Nick
asked on
smbmount - a bug ?
I have done a brief search here, and cannot find anything on this subject.
OK, have a network, and everything is hunky dory.
To mount a Win Drive on my Linux machine I have created 4 mount points for my 4 Windows machine drives thus:-
/home/winC /home/winD /home/winE /home/winF [cdrom]
Apply:-
submount //<Windows Machine>/C /home/winC
and then get presented with password (as expected), enter password, and they mount fine, and are browseable in Linux as required :-)
But... if I make a typo in the smbclient <machine> part, or enter an incorrect password I get a device not found/busy MS type of error message, and nothing happens except the mount point becomes a file [52KB] (created 1974) (?) and the permissions are set so nobody (including root) has access to do anything with it. I have done a page with 2 small screen dumps to aid you visualize the problem:-
http://www.nickw.co.uk/things/smb.htm
The only way I can remove these 'corrupted' folders is to re-boot!.
Is this a bug? Is there any other way to delete these corrupt 'folders/files' other than rebooting?
Cheers,
Nick
OK, have a network, and everything is hunky dory.
To mount a Win Drive on my Linux machine I have created 4 mount points for my 4 Windows machine drives thus:-
/home/winC /home/winD /home/winE /home/winF [cdrom]
Apply:-
submount //<Windows Machine>/C /home/winC
and then get presented with password (as expected), enter password, and they mount fine, and are browseable in Linux as required :-)
But... if I make a typo in the smbclient <machine> part, or enter an incorrect password I get a device not found/busy MS type of error message, and nothing happens except the mount point becomes a file [52KB] (created 1974) (?) and the permissions are set so nobody (including root) has access to do anything with it. I have done a page with 2 small screen dumps to aid you visualize the problem:-
http://www.nickw.co.uk/things/smb.htm
The only way I can remove these 'corrupted' folders is to re-boot!.
Is this a bug? Is there any other way to delete these corrupt 'folders/files' other than rebooting?
Cheers,
Nick
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
umount /home/winC
Yep, would work normally, but there is no directory/mount (after the 'failed' smbmount command) to unmount... it's recognised as a file ¿
I think this is a bug!
Nick
Yep, would work normally, but there is no directory/mount (after the 'failed' smbmount command) to unmount... it's recognised as a file ¿
I think this is a bug!
Nick
Umm, that does look like a bug in something, but I'm not sure what. When I provoke the same failure (RedHat 6.1, Samba 2.0.5a-12), it doesn't garbage the mount point. It does case the mount point to be unusable until I unmount it or re-boot, hence my proposed answer.
Which Linux and Samba are you using?
Which Linux and Samba are you using?
ASKER
Right, just done a deliberate incorrect password from console connecting to winD - the error message:-
tree connect failed: ERRSRV - ERRbadpw
smbmount: login failed
Could not umount /home/WinD: Device or resource busy
smbmount: exit
Then I get prompt back... jus tlooked, and got same 52 file created [winD]...
Specs:-
Linux 2.2.13-7mdk
KDE1.1.2
Samba 2.0.5a
Cheers,
Nick
tree connect failed: ERRSRV - ERRbadpw
smbmount: login failed
Could not umount /home/WinD: Device or resource busy
smbmount: exit
Then I get prompt back... jus tlooked, and got same 52 file created [winD]...
Specs:-
Linux 2.2.13-7mdk
KDE1.1.2
Samba 2.0.5a
Cheers,
Nick
ASKER
Bloody hell !!
I just re-read...
I was using smbumount /home...
not umount.
:-D
Nick
I just re-read...
I was using smbumount /home...
not umount.
:-D
Nick
Well that would do it...
ASKER
Yep, would work normally, but there is no directory/mount (after the 'failed' smbmount command) to unmount... it's recognised as a file ¿
I think this is a bug!
Nick