I continue to have the same problems in Samba 2.0.6 with smbfs that I was seeing in 2.0.5: (1) After a mount (mount -t smbfs etc.), the volume is often not yet fully mounted. For instance, if I write a Perl script like: system('mount -t smbfs -o password=pwd //MACHINE/SHARE /mnt/machine_share'); system('find /mnt/machine_share > find.out'); the 'find' may not find any files beyond /mnt/machine_share (yet not return any errors), because the thing is not really there yet. Right now, I'm putting a two-second sleep in between the mount and the find to avoid this problem. (2) The mount always returns success, since it doesn't even wait for the mount to complete properly. (3) After some period of time, the mount seems to "go away", such that 'df' shows a "Input/output error". This is all using Samba 2.0.6 on Linux 2.2.10, Debian Potato. Are these recognized as problems, will they be solved sometime, or is there a better way to handle scripting involving smbfs? Perhaps no one else is seeing this because they don't do a lot of mounting on the fly? I should also mention that I saw none of this behavior with the old (non-Samba) smbfs.
On Thu, 30 Dec 1999, Keith G. Murphy wrote:> I continue to have the same problems in Samba 2.0.6 with smbfs that I > was seeing in 2.0.5: > > (1) After a mount (mount -t smbfs etc.), the volume is often not yet > fully mounted. For instance, if I write a Perl script like: >[snip]> > (2) The mount always returns success, since it doesn't even wait for the > mount to complete properly.I believe this is a known mount problem. Try getting a new mount from the util-linux package: ftp://ftp.win.tue.nl/pub/linux/utils/util-linux Where you getting this with 2.0.5 too? That's strange since 2.0.5 didn't use mount -t, or do you have some magic script as mount.smbfs ?> (3) After some period of time, the mount seems to "go away", such that > 'df' shows a "Input/output error".Before 2.0.6 there was a lot of discussion about mounts that where dying but I thought this was fixed in 2.0.6 ... (smbmount died and when the smbfs wanted to talk to smbmount it was gone -> Input/output error). Does your mount (mount.smbfs?) process stay around? If it doesn't then all that needs to be done is figure out why it dies :) You are sure that it is smbmount from 2.0.6 that is used and not some left-over from 2.0.5? (sorry, just checking) /Urban
On Thu, 30 Dec 1999 03:30:24 +1100, hai scritto:>(1) After a mount (mount -t smbfs etc.), the volume is often not yet >fully mounted. For instance, if I write a Perl script like: >(2) The mount always returns success, since it doesn't even wait for the >mount to complete properly.These are "mount" bugs, solved in the latest util-linux release. -- giulioo@pobox.com