For the record and for those that are interested, it looks like the problem *was* kernel-level. I was running 2.4.18-6mdk, and the problem seems to have been fixed (see the package changes for the RPM regarding smbfs) in the 2.4.18-7mdk and later kernels (I grabbed the 2.4.18-8mdk one). The problem still appears to be there at first, but after I used the "umount -l" command, it took a few moments, but the unmountable mountpoint went away. Yay! Nevertheless, I still think this is an unacceptable way to handle such a problem, but at least I won't have to reboot anymore. Thanks to all who threw ideas my way.
ROB Rob Gillen wrote: > I've seen a problem for many different versions (latest 8.2) of > Mandrake with Samba before, and I may have even inquired about it > before. Whether it is a problem with Samba I have no idea, but I > suspect not. I'm trying to get some info/advice about what might be > potentially the problem before going to Samba mailing lists to query > them. > > Some of you might already be familiar with the strange way that Linux > will often disallow umount-ing or listing directory contents of a > mounted smb share, returning the error text, "Input/output error." I > believe this error happens when a smb share is mounted, then that > remote share is removed. This is a seriously annoying problem, > because restarting Samba does not solve the problem, nor does changing > runlevels. Which is why I think it may be a kernel-level problem. I > have tried changing the runlevel to [S]ingle level user, which is > running pretty much nothing save kernel processes and a simple shell. > At this level, a 'mount' command still shows the shares to be mounted, > and also at this level it is still impossible to umount them. The > only solution that I have found so far is rebooting, which I think is > an unacceptable way to handle such a problem. > <snip>
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
