fusesmb mount disappears - libsmbclient segfaults
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| samba (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: libsmbclient
In latest 8.10, I find that when using a filesystem mounted with fusesmb, the filesystem will suddenly disappear. This is very repeatable and does seem to be load related although more experimenting will be needed to find the exact cause.
Each time it happens, I get a line in my log:
Oct 29 10:02:57 gort kernel: [69797.713426] fusesmb[16090]: segfault at 4 ip b7c03590 sp b5514dc0 error 4 in libsmbclient.
Oct 29 11:00:01 gort kernel: [73221.338081] fusesmb[20089]: segfault at 4 ip b7cc9590 sp b55dadc0 error 4 in libsmbclient.
I've tried to get a backtrace with gdb, having installed fusesmb-dbgsym and libsmbclient-dbgsym but I can't seem to get it to attach properly. I'm a total noob with gdb, but I've tried "set follow-fork-mode child" and "set debug lin-lwp 1" but nothing seems to do the trick. I've asked around but to no avail, so if any deb could tell me how to supply a backtrace (or any other info you need) I'll be glad to oblige.
By the way, should apport pick this crash up, or not?
Note that I always found fusesmb very stable when used in exactly the same way on 8.04.
johncc@gort:~$ apt-cache policy libsmbclient
libsmbclient:
Installed: 2:3.2.3-1ubuntu3
Candidate: 2:3.2.3-1ubuntu3
Version table:
*** 2:3.2.3-1ubuntu3 0
500 http://
100 /var/lib/
johncc@gort:~$ apt-cache policy fusesmb
fusesmb:
Installed: 0.8.7-1
Candidate: 0.8.7-1
Version table:
*** 0.8.7-1 0
500 http://
100 /var/lib/
johncc@gort:~$
| description: | updated |
| John Carlyle-Clarke (jpcc) wrote | #1 |
| John Carlyle-Clarke (jpcc) wrote | #2 |
| Dr_Willis (dr-willis) wrote | #3 |
| Benny (benchik) wrote | #4 |
| Richard Corner (rcorner) wrote | #5 |
| Robert Moerland (veel-mail) wrote | #6 |
To add some more information, it doesn't always write something the logs when it fails. Sometimes the only way you know is because the directories suddenly appear empty and you start to get "Transport endpoint not connected" errors.
Secondly, the problem seems to occur always when you use Nautilus to view the fuse mounted files & directories. I find I can run bansee on fusesmb mounted music for long periods of time with no problem, but if I fire up fusesmb and then nautilus, I can make it fail instantly.