Bug#725387: Re : wheezy's shipped ntfs-3g causes strange fs corruptions
Hi, Hi, It's a windows 7 fresh install, the system was not hibernated when I had these problems, ntfscheck/info said about some unsupported flags Do you remember which flags ? Could be dirty meaning a partition previously improperly unmounted (for power failure, etc.) It's an hard disk not an SSD. I meant a computer using a SSD to cache data normally stored on a hard disk, for faster reboots. They are not compatible with both Linux and Windows. It's very strange no one noticed the problem because I think there is nothing uncommon in my configuration. I agree, the more as 2013.1.13AR.1 is a year an a half old, and the only similar reports were related to using Windows 8 (which is compatible with newer ntfs-3g). I have my thunderbird profile shared between linux and windows, and it becames corrupted after opening thunderbird on windows The cause does not appear to be Thunderbird (or any other application) related. If you used different incompatible Thunderbird versions on Linux and Windows, you would get application-level errors, not cluster allocation errors. Please tell me if I can provide more informations Do you remember having made some configuration change at the same period ? It is probably not worth switching back to the old version, but if you get something similar again, please report, and I will try to track the cause again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725387: Re : wheezy's shipped ntfs-3g causes strange fs corruptions
Hi, The errors exhibited by chkdsk are typical of what happens when two OS access a partition with one of them not being aware of the changes done by the other one. A typical situation for this to happen is updating on Linux a partition mounted on Windows while the latter is hibernated. On Windows 7 this situation can only be detected when the Windows system partition is mounted. There were no changes related to such detection between the versions you mentioned. I would rather suspect you were updating through Windows 8. This system brought a new mode with half-hibernation which can be detected on all partitions. This new mode was taken into account between the versions you mentioned, and mounting on Linux is now prohibited during such hibernation. Please understand that ntfs-3g 2012.1.15AR.5 (released on Apr 13, 2012) could not take into account what Microsoft released at a later date. Similar errors may also happen in some special architectures, such as different cacheing on a SSD. If this is your situation, please bring details. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725387: Re : wheezy's shipped ntfs-3g causes strange fs corruptions
On 10/08/13 10:47, Jean-Pierre André wrote: Hi, The errors exhibited by chkdsk are typical of what happens when two OS access a partition with one of them not being aware of the changes done by the other one. A typical situation for this to happen is updating on Linux a partition mounted on Windows while the latter is hibernated. On Windows 7 this situation can only be detected when the Windows system partition is mounted. There were no changes related to such detection between the versions you mentioned. I would rather suspect you were updating through Windows 8. This system brought a new mode with half-hibernation which can be detected on all partitions. This new mode was taken into account between the versions you mentioned, and mounting on Linux is now prohibited during such hibernation. Please understand that ntfs-3g 2012.1.15AR.5 (released on Apr 13, 2012) could not take into account what Microsoft released at a later date. Similar errors may also happen in some special architectures, such as different cacheing on a SSD. If this is your situation, please bring details. Hi, It's a windows 7 fresh install, the system was not hibernated when I had these problems, ntfscheck/info said about some unsupported flags With updated 1:2013.1.13AR.1-2 version I never had any problems while 2012.1.15AR.5 caused a lot of troubles It's an hard disk not an SSD. It's very strange no one noticed the problem because I think there is nothing uncommon in my configuration. I have another box in a similar configuration but I never had problem because it's a sid so it has new version Please tell me if I can provide more informations Regards -- Gianluigi Tiesi sher...@netfarm.it EDP Project Leader Netfarm S.r.l. - http://www.netfarm.it/ Free Software: http://oss.netfarm.it/ Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725387: Re : wheezy's shipped ntfs-3g causes strange fs corruptions
Hi, problematic version: 1:2012.1.15AR.5-2.1 backported working version: 1:2013.1.13AR.1-2 Can you please confirm which one is the version with suspected bad behavior ? If you fixed the file system by using chkdsk, can you please post its log, which you can find in mountpoint/'System Volume Information'/Chkdsk/Chkdsk*.log Replace mountpoint by your actual mount point. The '*' in the name Chkdsk*.log stands for the date and time you started chkdsk. The file is encoded in utf16, a simple way to get an ascii variant is to cat it to screen and copy/paste the output. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725387: Re : wheezy's shipped ntfs-3g causes strange fs corruptions
On 10/07/13 22:34, Jean-Pierre André wrote: Hi, problematic version: 1:2012.1.15AR.5-2.1 backported working version: 1:2013.1.13AR.1-2 Can you please confirm which one is the version with suspected bad behavior ? the version in wheezy is 1:2012.1.15AR.5-2.1, I had corruption every time I was writing to the disk. I've backported 1:2013.1.13AR.1-2 from sid and corruption problems are gone. If you fixed the file system by using chkdsk, can you please post its log, which you can find in I'm attaching some chkdsk logs, I've already cleaned and converted utf-8 unfortunately they are in Italian language, but I don't think it's a big problem Regards -- Gianluigi Tiesi sher...@netfarm.it EDP Project Leader Netfarm S.r.l. - http://www.netfarm.it/ Free Software: http://oss.netfarm.it/ Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon? Chkdsk.tar.bz2 Description: application/bzip
