Description of problem: [pasha@vbox smolrg]$ mount /mnt/net/y [pasha@vbox smolrg]$ [pasha@vbox mnt]$ umount /mnt/net/y umount: /mnt/net/y mount disagrees with the fstab /etc/fstab related record: //192.168.100.199/updater /mnt/net/y cifs users,noauto,guest,uid=500,gid=500,file_mode=0666,dir_mode=0777,iocharset=utf8 0 0 I think it is known problem with available patch. Please look at: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/99437 Version-Release number of selected component (if applicable): $ rpm -qf `which mount` util-linux-2.19-4.fc15.i686 How reproducible: Always.
The problem is that fstab does not match with mtab, right? For example: fstab: //foo.com/path mtab (/proc/mounts): //foo.com/path/ The umount(8) command (for non-root users) requires that the first field in fstab matches with the first field from mtab (or /proc/mounts). The mount.cifs should not add the extra '/' to the end of the source path or cifs docs should be updated and the '/' should be required in all fstabs.
Yep, this was actually fixed in "mainline" cifs-utils a couple of weeks ago by just having it pass the "device" string from userspace to the kernel directly (instead of trying to reconstruct it).
cifs-utils-4.9-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/cifs-utils-4.9-2.fc15
Could you please post update for Fedora 14 too?
(In reply to comment #4) > Could you please post update for Fedora 14 too? Could you open a bug for this against f14?
Package cifs-utils-4.9-2.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing cifs-utils-4.9-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/cifs-utils-4.9-2.fc15 then log in and leave karma (feedback).
cifs-utils-4.9-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.