Bug 805610

Summary: umount message "mount disagrees with the fstab" is too vague
Product: [Fedora] Fedora Reporter: stef <stephane.tranchemer>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: jonathan, kzak, mluscon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-10-29 15:31:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description stef 2012-03-21 16:54:18 UTC 
Description of problem:

When issuing a umount command you can get the following message "mount disagrees with the fstab".

This message doesn't give any usefull information about what really happens.

Here's what was the trigger of it in my install and how I fixed it :

I had this line in my fstab file

* server:/share	/share	nfs	noauto,user,defaults        0 0

but then umount gave me the not very helpfull message...

I found this doing a 'cat /etc/mtab | grep share'

server:/share/ /share nfs rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.0.1,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=192.168.0.1 0 0

I finally understood that the PRECISE value in mtab and fstab syntaxicaly didn't match, then I changed my fstab line to this :


* server:/share/	/share	nfs	noauto,user,defaults        0 0

This time no more problem.

The error messages needs to be more verbose and explicative about what the problem is, or the mount/umount executables needs to be modified to be more aware about a simple "/" difference.

The Libc logic "strcmp(str1, str2)≠0 means different" is a bit overkill in this context and needs a better approach.

Version-Release number of selected component (if applicable):


How reproducible:

always

Steps to Reproduce:
1.do not include a / at the end of a nfs mount source in fstab
2.mount
3.umount
  
Actual results:

says that the umount is not possible because "mount disagrees with the fstab"

Expected results:

understands that /share/ and /share means the same and do the umount

Additional info:
Comment 1 Karel Zak 2012-03-21 18:07:28 UTC 
This is known (and fixed) issue in F17... well, it seems that we have to backport the umount part of the upstream commit b106d052383083b80c0dc41f1555d2661db00374 to F16.
Comment 2 Karel Zak 2012-10-29 15:31:40 UTC 
It's not so fatal problem to backport the patch to Fedora16. Closing.
Comment 3 stef 2012-10-29 16:13:34 UTC 
just for the record, I disagree totally your point-of-view on this matter.

The devil is in the details and lots of those "minor" concerns spoils every Fedora distribution I worked on since many years.

Having a "killer feature" does not make a release the better ever, it's about being bug, regression and issue free.