This bug has been fixed in ntfs-3g-2014.2.15AR.1
Upgrading (or applying the patch in Message #30) is recommended
Jean-Pierre
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
So, with a random chunk order, a factor of 2 was expected,
which your figures confirm. The difference between the two
patch variants should be much smaller.
Well i think with the former I did a little more downloading.
So I can't make any conclusions from that.
Then I have to do a more con
Niek Green wrote:
Hi,
I have attached a different variant of the patch, which
I prefer because it should have less overhead.
Can you try it also ?
Yep that one works too.
Great ! So that will be the one which I will promote upon
further testing.
Too bad, this is probably what I wanted, b
Hi,
I have attached a different variant of the patch, which
I prefer because it should have less overhead.
Can you try it also ?
Yep that one works too.
Too bad, this is probably what I wanted, but your download
does not lead to measurable times. Good news for ntfs-3g
performance anyway. So
Hi again,
Niek Green wrote:
Hoi,
Thank you for testing. It confirms what I have found in the
meantime, and I have even found the cause.
I do not need the logs I asked, you can drop them.
Can you please try the attached patch over the latest
version 2013.1.13AR.4 ?
Done, no errors anymore.
Hoi,
Thank you for testing. It confirms what I have found in the
meantime, and I have even found the cause.
I do not need the logs I asked, you can drop them.
Can you please try the attached patch over the latest
version 2013.1.13AR.4 ?
Done, no errors anymore.
And I would also like to kn
Hi,
deb...@niek.gr wrote:
Hello,
What do you mean ? Is the issue un-repeatable, or did you switch
to an earlier version ?
I meant downgrading to the earlier version that is still in testing
(1:2013.1.13AR.1-2)
I haven't seen this problem with that version but when upgrading to
AR.4-2, the er
Hello,
What do you mean ? Is the issue un-repeatable, or did you switch
to an earlier version ?
I meant downgrading to the earlier version that is still in testing
(1:2013.1.13AR.1-2)
I haven't seen this problem with that version but when upgrading to
AR.4-2, the errors pop-up again.
2) Can
Hi,
ntfs-3g spitting out a lot of errors, rtorrent crashing with a SIGBUS
exception,
and the NTFS partition being corrupted.
Hmm. Probably bug introduced in 2013.1.13AR.4 through
either
http://sourceforge.net/p/ntfs-3g/ntfs-3g/ci/d2c7d40a2b494f9bf355c8bbe78c24fa16925f86/
or the subsequent
http
Package: ntfs-3g
Version: 1:2013.1.13AR.4-2
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
* What led up to the situation?
Upgrading from version 1:2013.1.13AR.1-2 to 1:2013.1.13AR.4-2.
* What exactly did you do (or not do) that was effective (or
ineffe
10 matches
Mail list logo
