Re: [fuse-devel] Fwd: ntfs3g (or whatever) crashes are not fixed

[Jean-Pierre A. <jea...@wa...>]

Hi Matteo,

Matteo Sisti Sette wrote:
>
>> Matteo Sisti Sette wrote:
>>> On 08/30/2013 02:00 PM, Miklos Szeredi wrote:
>>>
>>>> Ntfs-3g uses it's own internal version of fuse, so the fuse package's
>>>> version is irrelevant for this bug.
>>>>
>>>> Please check the ntfs-3g version instead.
>>>
>>> Then that means that the "workaround" described in comment #29 at
>>> https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1072270/comments/29
>>> is completely useless?
>>
>> Which workaround are you pointing at ?
>
> Sorry, wrong link:
> https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1072270/comments/26
>
> The supposed workaround (or probably the right word is "fix") is to 
> install libfuse/fuse version 2.9.2-2 or above. Which I did in Ubuntu 
> 12.10, and seemed to work (never observed a ntfs-3g crash again) until 
> it crashed again recently after upgrading to Ubuntu 13.04. I don't 
> know whether it is a coincidence or something has "regressed" in 
> Ubuntu 13.04, but the version of fuse and libfuse which I had 
> installed (2.9.2-4) is still there.
>
>
>> I do not see any precise data about your own issue. Nobody can be
>> sure you hit the same bug as the one reported as #1072270 without
>> some extra detail. Getting a message "Transport endpoint is not
>> connected" is not enough to qualify for being the same bug. You
>> may have hit another bug in fuse, ntfs-3g or whatever.
>
> Maybe. Besides the message "Transport endpoint..." there is the ubuntu 
> popup window indicating that nfts-3g has crashed (iirc, it says that 
> "some system program" has crashed, then the "Show Details" button 
> shows it's ntfs-3g or ntfs-3g-something.
>
>
> > Reminder :  Ubuntu does not use the fuse library shipped by nfs-3g.
>
> I have no idea what that implies. The discussion in the Ubuntu bug 
> report seems to indicate that replacing libfuse and fuse with the most 
> recent version is supposed to fix the ntfs3g crashes; somebody in this 
> list said that those packages are irrelevant because ntfs-3g uses its 
> own version, so installing whatever version of libfuse/fuse on Ubuntu 
> should have no impact; now I don't understand which of the two thesis 
> this reminder  supports.

Well, the bug reported as #1072270 relates to
libfuse (AFAIK versions 2.9.0 and 2.9.1). The fuse
library shipped by ntfs-3g is not used by Ubuntu,
so the bug #1072270 is specific to versions which
are discussed on this list. I was mainly objecting
to Miklos' remark quoted above.

So, even though we do not know whether your bug
is the same as #1072270, they cannot be caused
by the fuse library shipped by ntfs-3g.

>> Can you post the syslog messages and backchain triggered by the
>> bug (Sorry, I do not know the procedure to collect them from
>> Ubuntu)
>
> Sorry, I don't either.
>
>> If this were to be an ntfs-3g
>> bug,
>
> I'm not implying this is a ntfs-3g bug. Everybody seems to agree it's 
> a fuse/libfuse bug, and I'm not questioning it. This mailing list is 
> about fuse development, not about ntfs-3g development, right?

Ok, I am getting out of this thread.

>> please start chkdsk from Windows before reporting.
>
> I shouldn't ever need Windows to use a ntfs partition in Linux, or to 
> report a bug against a Linux program.

I agree. However nobody has released an open-source
ntfs checker for Linux, so this is just a wish.

> Do you mean that if the crash is triggered by some error in the ntfs 
> partition (which Window's chkdsk could detect and/or fix) then it's 
> not a bug?
>
> Or do you mean that chkdisk would provide additional information?

I mainly mean that if ntfs-3g has really crashed, your
data might be left in an inconsistent state, and you
will save energy by putting things right first.

Now, the bug reported as #1072270 occurs between
transitions and should not affect your data.

Jean-Pierr