Bug 5808 - 3.2.4 (+3.3.0pre2) & FUSE filesystem directory dissapears after awhile.
3.2.4 (+3.3.0pre2) & FUSE filesystem directory dissapears after awhile.
Product: Samba 3.2
Classification: Unclassified
Component: File services
x86 Windows XP
: P3 critical
: ---
Assigned To: Jeremy Allison
Samba QA Contact
Depends on:
  Show dependency treegraph
Reported: 2008-10-03 18:33 UTC by hyakki
Modified: 2009-08-06 16:55 UTC (History)
0 users

See Also:

level10 log of samba.XPPRO (691.30 KB, application/octet-stream)
2008-10-07 00:31 UTC, hyakki
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description hyakki 2008-10-03 18:33:55 UTC
  Since upgrading to 3.2.4 samba has been breaking when it lists FUSE mounted directorys 

for example i have a directory for the fuse filesystem  /down/.cache/ (this is where the fuse filesystem stores data) then i mount that to /down/data/ now this is where the problem starts when samba is first started the directory shows up fine and i can even using it for awhile, then out of the blue samba makes mounted the directory dissapear any programs that were using the directory crash and it becomes impossible to re-access the directory (unless i restart samba, but then it happens again after awhile), i know this is a bug in the recent samba versions since i can still access the directorys fine on the local machine, and restarting samba makes the dir re-appear, also downgrading to an older samba version 3.2.3 or 3.3.0pre1 fixes the problem.

the fuse filesystems i am using are encfs 1.5.0, but this problem also happens on other fuse filesystems such as compfused, im sure it could happen on others also

i asked in #samba-technical but they told me to make a bug report. hopefully someone can fix this.

steps to reproduce make fuse filesystem such as encfs (maybe even other fuse filesystems like compfused..etc) use it for awhile and samba should break after some time, it should be easy to track down since it was a recent change that happened in the samba code.
Comment 1 Jeremy Allison 2008-10-06 18:51:45 UTC
Attach a debug level 10 log of this failing please.
Comment 2 hyakki 2008-10-06 23:37:26 UTC
(In reply to comment #1)
> Attach a debug level 10 log of this failing please.
> Jeremy.

thats kindof a problem for me since i only have 1 gig of space and a level 10 debug log can fill that space up fast, and since this bug happens random from 1-30~ minutes, but ill see what i can do maybe ill be lucky and catch it.
Comment 3 hyakki 2008-10-07 00:31:05 UTC
Created attachment 3662 [details]
level10 log of samba.XPPRO

here is the log, the real log was around 200 megs, so i just cut the last 10 megs around where the error happened and zipped it, 20 20 20 20 binary data is just a dummy file i was creating on the fuse file system 

the problem (fuse) dirs i was working with are /down/Storage/Programs/Backup
and /down/fuse/data
Comment 4 Karolin Seeger 2009-08-06 09:17:00 UTC
Jeremy, are there any news on this one?
Comment 5 hyakki 2009-08-06 16:07:20 UTC
(In reply to comment #4)
> Jeremy, are there any news on this one?

i found a fix for this, on the fuse file system you need to mount with the option allow_other i guess samba drops permissions after awhile 
Comment 6 Jeremy Allison 2009-08-06 16:55:23 UTC
Ah, this makes sense. Samba only stays as the logged in user credentials whilst there is activity going on, periodically Samba will revert back to root. Looks like the FUSE mount option "allow_other" is required for access via Samba. We might want to make a tech note of this somewhere.