netfs allows multiple identical mounts (was: smb/mount
Quoted 6 lines · Urban Widmark
Quoted 2 lines · Dan Podeanu
This should be self explanatory. My guess is, its probably the smb filesystem reporting as mounting again a share after network failure.
A very simple way to reproduce this (on 2.4.7):
Quoted 8 lines
$ mount -t smbfs -o username=puw //srv/share /mnt/smb $ mount -t smbfs -o username=puw //srv/share /mnt/smb $ cat /proc/mounts | grep smbfs //srv/share /mnt/smb smbfs rw 0 0 //srv/share /mnt/smb smbfs rw 0 0This is probably something that smbmount could check before mounting. But I'm not sure if that is the best fix.
For sure it is, as doing
mount -t smbfs -o username=a //srv/share /mnt/smb
mount -t smbfs -o username=b //srv/share /mnt/smb
looks quite legal to me, as both //srv/share can display completely different set of files, and nobody except smbfs knows that username=a/ username=b matters, but fmode=700/fmode=755 does not...
Quoted 2 lines
It could compare the server string ("//srv/share") but what if that server listens to more than one name?
ncpfs (mount.ncp) will warn you if //srv/share is listed anywhere in /etc/mtab and it is mounted by you. If you'll use '-o multiple', then it is assumed that you know what you are doing, and nothing prevents you from mounting same thing on same place 255 times.
Best regards,
Petr Vandrovec [email protected]
Quoted 11 lines · Petr Vandrovec
Quoted 2 lines
This is probably something that smbmount could check before mounting. But I'm not sure if that is the best fix.
For sure it is, as doing
mount -t smbfs -o username=a //srv/share
/mnt/smb
mount -t smbfs -o username=b //srv/share/mnt/smblooks quite legal to me, as both //srv/share can display completely different set of files, and nobody except smbfs knows that username=a/ username=b matters, but fmode=700/fmode=755 does not...
If this was a local block device it would not allow the mount, because the device is the same. Even if the options differ in a way that makes it access the files differently (hypothetical ntfs that allows you to specify the NT-GUID to use for access control? some funky iso9660 option that force it to read dirs from some alternative list?)
Doing this in smbmount isn't a problem, but I thought this was inconsistent between local and remote fs and that it could perhaps be (sort of) solved for all fs at once by doing something clever. Perhaps not.
Quoted 4 lines
ncpfs (mount.ncp) will warn you if //srv/share is listed anywhere in
/etc/mtaband it is mounted by you. If you'll use '-o multiple', then it is assumed that you know what you are doing, and nothing prevents you from mounting same thing on same place 255 times.
Most people have other "nodev" fs' so you can't actually mount 255 times (unless you hack get_unnamed_dev to give you more :)
And yes, I know someone that wanted to.
/Urban