Messages in this thread | | | Subject | dying samba mounts | From | Hannu Koivisto <> | Date | 10 Nov 1998 11:38:54 +0200 |
| |
Greetings,
The last time I tested samba mounts (I was probably using .76, .96 or .101 back then), they used to work just fine for few hours but usually after night they were dead. I didn't have guts to experiment them because I couldn't unmount them with smbumount ("Could not open /mnt/xyz: Input/output error") and that was a server machine so I didn't want to pollute it.
Now, with 2.1.125/x86 and smbfsx 1.9.18p10 (from Debian), the problem is still there. I realized I can unmount the samba mounts with plain umount, so I experimented a bit more. The machine I mount shares from is an NT 4.0SP3 box and it's still the same story: I can use those mounts fine for some time, but then the smbmount that was left on background says it got a signal, tries to get a new socket and then tries to ask password (sometimes I manage to give it, but usually the tty is pretty messed up).
I don't know whether this is a problem with smbmount or the kernel, but I guess kernel has something to do with this because at the time of death I get this to kernel log: """ kernel: smb_retry: signal failed, error=-3 last message repeated 3 times """ I have gotten some other messages too like "smb_trans2_request: result=-32, setting invalid", but they don't correlate with those death cases.
If you have ideas what could cause this or how to investigate the problem, I'd like to hear. It would be nice to get rid of that kind of behaviour before 2.2...
TIA, //Hannu
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |