|
From: Jean-Pierre A. <jea...@wa...> - 2012-10-19 11:50:19
|
Hi again, Christoph LANGE wrote: > Hi Jean-Pierre, > > thanks for your reply! > > 2012-10-19 12:32 Jean-Pierre André: >> You did not give details, > > How would I be able to obtain such details in future? Is there a > generic logging facility for fuse filesystems? Or do I have to rely > on whatever the specific fuse filesystem provides? (I see from "man > ntfs-3g" that this filesystem has the options "debug" and "no_detach", > which I should probably have used.) I just meant that I did not get a clue to confirm the fix I mentioned was related to the issue you reported. In most situation, the initial clue is logged into the system log (whose location depends on the distribution), and ntfs-3g and fuse try to log unusual conditions which are met. The fix I suggested is related to having "fuse internal error: node NNN not found" in the system log file. Do you have this or something else logged ? Using the debug option may be useful in complex situations when there is no other clue. >> but a frequent cause for >> this on fuse 2.9.0 and 2.9.1 is covered by the fix described >> in >> http://fuse.git.sourceforge.net/git/gitweb.cgi?p=fuse/fuse;a=commit;h=1061a0a2d90148bd2e7f32e1e694399db2dbe087 >> > > Thanks for letting me know! > >> Or upgrade to the latest fuse version with all the bug fixes. > > With regard to this I have reported the problem back to Gentoo, my > Linux distributor (where fuse-2.9.1-r1 is the latest version so far); > see https://bugs.gentoo.org/show_bug.cgi?id=437568#c11 The "-r1" suffix may mean some fix has been applied to the base fuse-2.9.1, so I cannot really tell whether the one I mentioned has been applied. Get the corresponding source code, and check. Regards Jean-Pierre |