FAQ SearchLogin
Tuxera Home
View unanswered posts | View active topics It is currently Sat May 15, 2021 04:06



Post new topic Reply to topic  [ 16 posts ] 
ntfs-3g corrupts volume? 
Author Message

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post ntfs-3g corrupts volume?
Hello,

first of all, many thanks for providing ntfs-3g. If it wasn't for this problem, which I am not entirely sure to be actually caused by ntfs-3g, it'd be just perfect.

Anyway, I use Arch Linux x64, i. e. have all the latest software updates :). The very same problem however already occurred in a previous Ubuntu 9.10 installation:

Virtually always when I boot into Windows 7 x64 after having used Arch, which is configured to allow rw access for (only) my user to my ntfs partitions (three, one on another hdd) I get messages of "filesystem corrupted", but always exclusively for the partition Windows is installed on. My Windows user tmp directory appears particularly affected, for whatever reason, which causes applications to malfunction. It is to be noted that I myself very seldom write on the two other partitions - the one affected however does hold the profile folders for Firefox & Thunderbird, which I use extensively, and are shared between the two OS.

The chkdsk /F report is always the same:

Code:
C:\>chkdsk /F
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is System.

CHKDSK is verifying files (stage 1 of 3)...
4 percent complete. (57447 of 143616 file records processed)
Deleted corrupt attribute list entry
with type code 128 in file 70766.
Deleting corrupt attribute record (128, "")
from file record segment 119468.
9 percent complete. (129255 of 143616 file records processed)
Deleting corrupt attribute record (128, "")
from file record segment 142314.
Deleting corrupt attribute record (128, "")
from file record segment 142331.
Deleting corrupt attribute record (128, "")
from file record segment 142345.
Deleting corrupt attribute record (128, "")
from file record segment 142399.
Deleting corrupt attribute record (128, "")
from file record segment 142400.
Deleting corrupt attribute record (128, "")
from file record segment 142474.
Deleting corrupt attribute record (128, "")
from file record segment 142478.
Deleting corrupt attribute record (128, "")
from file record segment 142732.
  143616 file records processed.
File verification completed.
  590 large file records processed.
  0 bad file records processed.
  2 EA records processed.
  44 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
46 percent complete. (146713 of 192132 index entries processed)
Deleting index entry TM04D0~1 in index $I30 of file 3679.
Deleting index entry TM05E9~2 in index $I30 of file 3679.
Deleting index entry TM0D21~1 in index $I30 of file 3679.
Deleting index entry TM198D~1 in index $I30 of file 3679.
Deleting index entry TM1AF1~1 in index $I30 of file 3679.
Deleting index entry TM237A~1 in index $I30 of file 3679.
Deleting index entry TM2956~1 in index $I30 of file 3679.
Deleting index entry TM317E~1 in index $I30 of file 3679.
Deleting index entry TM37A7~1 in index $I30 of file 3679.
Deleting index entry TM4073~1 in index $I30 of file 3679.
Deleting index entry TM43C4~1 in index $I30 of file 3679.
Deleting index entry TM449E~1 in index $I30 of file 3679.
Deleting index entry TM46A6~1 in index $I30 of file 3679.
Deleting index entry TM5294~1 in index $I30 of file 3679.
Deleting index entry TM53FC~1 in index $I30 of file 3679.
Deleting index entry TM5BFA~1 in index $I30 of file 3679.
Deleting index entry TM678E~1 in index $I30 of file 3679.
Deleting index entry TM6798~1 in index $I30 of file 3679.
Deleting index entry TM6978~1 in index $I30 of file 3679.
Deleting index entry TM8484~1 in index $I30 of file 3679.
Deleting index entry TM92C4~1 in index $I30 of file 3679.
Deleting index entry TM977F~1 in index $I30 of file 3679.
Deleting index entry TM98FA~1 in index $I30 of file 3679.
Deleting index entry TM9AFE~1 in index $I30 of file 3679.
Deleting index entry TMB78D~1 in index $I30 of file 3679.
Deleting index entry TMBF3C~1 in index $I30 of file 3679.
Deleting index entry TMC337~1 in index $I30 of file 3679.
Deleting index entry TMC51F~1 in index $I30 of file 3679.
Deleting index entry TMC6E8~1 in index $I30 of file 3679.
Deleting index entry TMC747~1 in index $I30 of file 3679.
Deleting index entry TMCAFC~1 in index $I30 of file 3679.
Deleting index entry TMCB1F~1 in index $I30 of file 3679.
Deleting index entry TMCFF6~1 in index $I30 of file 3679.
Deleting index entry TMD7DE~1 in index $I30 of file 3679.
Deleting index entry TME251~1 in index $I30 of file 3679.
Deleting index entry TME468~1 in index $I30 of file 3679.
Deleting index entry TMEC0F~1 in index $I30 of file 3679.
Deleting index entry TMEFB4~1 in index $I30 of file 3679.
Deleting index entry TMEFB4~2 in index $I30 of file 3679.
Deleting index entry TMF9EA~1 in index $I30 of file 3679.
Deleting index entry TMFAB3~1 in index $I30 of file 3679.
Deleting index entry TMFBA6~1 in index $I30 of file 3679.
Deleting index entry TMFFDF~1 in index $I30 of file 3679.
Deleting index entry TMP000000129DE26BA894FB89B8 in index $I30 of file 3679.
Deleting index entry TMP00000013071A3C6584152644 in index $I30 of file 3679.
Deleting index entry TMP00000014B7676651109456CF in index $I30 of file 3679.
Deleting index entry TMP00000015794D46D55D839A4B in index $I30 of file 3679.
Deleting index entry TMP00000016C195754A49379401 in index $I30 of file 3679.
Deleting index entry TMP000000173E9717F5094E59EC in index $I30 of file 3679.
Deleting index entry TMP0000001875CD78A3D38307FF in index $I30 of file 3679.
Deleting index entry TMP00000019F128CEA5AB5353FE in index $I30 of file 3679.
Deleting index entry TMP0000001C60601F3AF3F043C8 in index $I30 of file 3679.
Deleting index entry TMP0000001E74965B92E1907580 in index $I30 of file 3679.
Deleting index entry TMP0000001FBD9BBA66DB814CFE in index $I30 of file 3679.
Deleting index entry TMP00000020C72B39B98FD78EE9 in index $I30 of file 3679.
Deleting index entry TMP000000210D1BDD5A28DF3DD9 in index $I30 of file 3679.
Deleting index entry TMP000000223A554328BCF03CBD in index $I30 of file 3679.
Deleting index entry TMP00000023063CF3324CCF71DF in index $I30 of file 3679.
Deleting index entry TMP0000002CB01887574720814F in index $I30 of file 3679.
Deleting index entry TMP0000002D8EBBF7358E0A02B3 in index $I30 of file 3679.
Deleting index entry TMP0000002E54A561EC867675F9 in index $I30 of file 3679.
Deleting index entry TMP0000002F525EF802A99AA7E3 in index $I30 of file 3679.
Deleting index entry TMP000000326165A2B4FA530F2C in index $I30 of file 3679.
Deleting index entry TMP000000339C3F328B1C5899B1 in index $I30 of file 3679.
Deleting index entry TMP0000003852F3703BD826C8C1 in index $I30 of file 3679.
Deleting index entry TMP00000039B1971D3247C05DD0 in index $I30 of file 3679.
Deleting index entry TMP0000003B9733AE3CC8BD2FC2 in index $I30 of file 3679.
Deleting index entry TMP0000003C34B2971873AF9FAA in index $I30 of file 3679.
Deleting index entry TMP0000003FD5A8E02EE03B8DA8 in index $I30 of file 3679.
Deleting index entry TMP000000404E906C2B9F7D6CFD in index $I30 of file 3679.
Deleting index entry TMP00000045254D20C759E8AAB4 in index $I30 of file 3679.
Deleting index entry TMP00000046ECB565ECD3309A42 in index $I30 of file 3679.
Deleting index entry TMP00000047617CA59008858C16 in index $I30 of file 3679.
Deleting index entry TMP00000048CD07AACC70EE5D3B in index $I30 of file 3679.
Deleting index entry TMP000000495A16F9D25E2146F5 in index $I30 of file 3679.
Deleting index entry TMP0000004A5FC23F484C76AFDA in index $I30 of file 3679.
Deleting index entry TMP0000004BD406CDCEF55CB968 in index $I30 of file 3679.
Deleting index entry TMP0000004C1829A6BBFB13633A in index $I30 of file 3679.
Deleting index entry TMP0000004D89FCD0788398E055 in index $I30 of file 3679.
Deleting index entry TMP0000004E55AB8D006A757CE1 in index $I30 of file 3679.
Deleting index entry TMP0000004FB0BFF4903A2E3AC3 in index $I30 of file 3679.
Deleting index entry TMP00000050675C89EE86156B73 in index $I30 of file 3679.
Deleting index entry TMP0000005142EC0183F18DE0E7 in index $I30 of file 3679.
Deleting index entry TMP000000524E196BBD0644CB1C in index $I30 of file 3679.
Deleting index entry TMP000000553004291A5181653D in index $I30 of file 3679.
Deleting index entry TMP00000056BA9B25AC0388B74A in index $I30 of file 3679.
49 percent complete. (158875 of 192132 index entries processed)
Deleting index entry ini156d5zmi.tmp in index $I30 of file 69334.
Deleting index entry INI156~1.TMP in index $I30 of file 69334.
Deleting index entry ini15pgbgqt.tmp in index $I30 of file 69334.
Deleting index entry INI15P~1.TMP in index $I30 of file 69334.
Deleting index entry ini16xcfzp6.tmp in index $I30 of file 69334.
Deleting index entry INI16X~1.TMP in index $I30 of file 69334.
Deleting index entry ini17h0sebq.tmp in index $I30 of file 69334.
Deleting index entry INI17H~1.TMP in index $I30 of file 69334.
Deleting index entry ini180xs4b1.tmp in index $I30 of file 69334.
Deleting index entry INI180~1.TMP in index $I30 of file 69334.
Deleting index entry ini1c18m0dn.tmp in index $I30 of file 69334.
Deleting index entry INI1C1~1.TMP in index $I30 of file 69334.
Deleting index entry ini1huov5yd.tmp in index $I30 of file 69334.
Deleting index entry INI1HU~1.TMP in index $I30 of file 69334.
Deleting index entry ini1imn8dtn.tmp in index $I30 of file 69334.
Deleting index entry INI1IM~1.TMP in index $I30 of file 69334.
Deleting index entry ini1iy5mdih.tmp in index $I30 of file 69334.
Deleting index entry INI1IY~1.TMP in index $I30 of file 69334.
Deleting index entry ini1njg4lxp.tmp in index $I30 of file 69334.
Deleting index entry INI1NJ~1.TMP in index $I30 of file 69334.
Deleting index entry ini1ppi3nhk.tmp in index $I30 of file 69334.
Deleting index entry INI1PP~1.TMP in index $I30 of file 69334.
Deleting index entry ini297kbw1t.tmp in index $I30 of file 69334.
Deleting index entry INI297~1.TMP in index $I30 of file 69334.
Deleting index entry ini2arhrk7v.tmp in index $I30 of file 69334.
Deleting index entry INI2AR~1.TMP in index $I30 of file 69334.
Deleting index entry ini2d4gk9u2.tmp in index $I30 of file 69334.
Deleting index entry INI2D4~1.TMP in index $I30 of file 69334.
Deleting index entry ini2imnkj8b.tmp in index $I30 of file 69334.
Deleting index entry INI2IM~1.TMP in index $I30 of file 69334.
Deleting index entry ini2jot005z.tmp in index $I30 of file 69334.
Deleting index entry INI2JO~1.TMP in index $I30 of file 69334.
Deleting index entry ini2kwy2ua2.tmp in index $I30 of file 69334.
Deleting index entry INI2KW~1.TMP in index $I30 of file 69334.
Deleting index entry ini2l955or4.tmp in index $I30 of file 69334.
Deleting index entry INI2L9~1.TMP in index $I30 of file 69334.
Deleting index entry ini2mm0fblc.tmp in index $I30 of file 69334.
Deleting index entry INI2MM~1.TMP in index $I30 of file 69334.
Deleting index entry ini2ouzix3o.tmp in index $I30 of file 69334.
Deleting index entry INI2OU~1.TMP in index $I30 of file 69334.
Deleting index entry ini3a2ps1o.tmp in index $I30 of file 69334.
Deleting index entry INI3A2~1.TMP in index $I30 of file 69334.
Deleting index entry ini3pv4ct0.tmp in index $I30 of file 69334.
Deleting index entry INI3PV~1.TMP in index $I30 of file 69334.
Deleting index entry ini53vpkop.tmp in index $I30 of file 69334.
Deleting index entry INI53V~1.TMP in index $I30 of file 69334.
Deleting index entry ini5j7czt5.tmp in index $I30 of file 69334.
Deleting index entry INI5J7~1.TMP in index $I30 of file 69334.
Deleting index entry inibworhi3.tmp in index $I30 of file 69334.
Deleting index entry INIBWO~1.TMP in index $I30 of file 69334.
Deleting index entry ininqvdarz.tmp in index $I30 of file 69334.
Deleting index entry ININQV~1.TMP in index $I30 of file 69334.
Deleting index entry iniqmtpoha.tmp in index $I30 of file 69334.
Deleting index entry INIQMT~1.TMP in index $I30 of file 69334.
Deleting index entry inivs3lz9i.tmp in index $I30 of file 69334.
Deleting index entry INIVS3~1.TMP in index $I30 of file 69334.
49 percent complete. (161423 of 192132 index entries processed)
Deleting index entry ini10swku9y.tmp in index $I30 of file 91653.
Deleting index entry INI10S~1.TMP in index $I30 of file 91653.
Deleting index entry ini117evu97.tmp in index $I30 of file 91653.
Deleting index entry INI117~1.TMP in index $I30 of file 91653.
Deleting index entry ini18f663zy.tmp in index $I30 of file 91653.
Deleting index entry INI18F~1.TMP in index $I30 of file 91653.
Deleting index entry ini1dtq022r.tmp in index $I30 of file 91653.
Deleting index entry INI1DT~1.TMP in index $I30 of file 91653.
Deleting index entry ini1h0q7a5x.tmp in index $I30 of file 91653.
Deleting index entry INI1H0~1.TMP in index $I30 of file 91653.
Deleting index entry ini1lex7nx9.tmp in index $I30 of file 91653.
Deleting index entry INI1LE~1.TMP in index $I30 of file 91653.
Deleting index entry ini1nkm0l8r.tmp in index $I30 of file 91653.
Deleting index entry INI1NK~1.TMP in index $I30 of file 91653.
Deleting index entry ini1tadya08.tmp in index $I30 of file 91653.
Deleting index entry INI1TA~1.TMP in index $I30 of file 91653.
Deleting index entry ini1tp3l1vp.tmp in index $I30 of file 91653.
Deleting index entry INI1TP~1.TMP in index $I30 of file 91653.
Deleting index entry ini1ufpkzcz.tmp in index $I30 of file 91653.
Deleting index entry INI1UF~1.TMP in index $I30 of file 91653.
Deleting index entry ini26itneze.tmp in index $I30 of file 91653.
Deleting index entry INI26I~1.TMP in index $I30 of file 91653.
Deleting index entry ini2j3odcq6.tmp in index $I30 of file 91653.
Deleting index entry INI2J3~1.TMP in index $I30 of file 91653.
Deleting index entry ini2sd55zt7.tmp in index $I30 of file 91653.
Deleting index entry INI2SD~1.TMP in index $I30 of file 91653.
Deleting index entry ini2su552t0.tmp in index $I30 of file 91653.
Deleting index entry INI2SU~1.TMP in index $I30 of file 91653.
Deleting index entry ini8osrjkg.tmp in index $I30 of file 91653.
Deleting index entry INI8OS~1.TMP in index $I30 of file 91653.
Deleting index entry ini8p8ns1y.tmp in index $I30 of file 91653.
Deleting index entry INI8P8~1.TMP in index $I30 of file 91653.
Deleting index entry inibn4qrbc.tmp in index $I30 of file 91653.
Deleting index entry INIBN4~1.TMP in index $I30 of file 91653.
Deleting index entry inire8u37l.tmp in index $I30 of file 91653.
Deleting index entry INIRE8~1.TMP in index $I30 of file 91653.
Deleting index entry inirhvwf87.tmp in index $I30 of file 91653.
Deleting index entry INIRHV~1.TMP in index $I30 of file 91653.
Deleting index entry iniwo7vpxm.tmp in index $I30 of file 91653.
Deleting index entry INIWO7~1.TMP in index $I30 of file 91653.
Deleting index entry inixaz85ev.tmp in index $I30 of file 91653.
Deleting index entry INIXAZ~1.TMP in index $I30 of file 91653.
Deleting index entry iniyva4u0o.tmp in index $I30 of file 91653.
Deleting index entry INIYVA~1.TMP in index $I30 of file 91653.
  192132 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  143616 file SDs/SIDs processed.
Security descriptor verification completed.
Inserting data attribute into file 70766.
69 percent complete. (1 of 24268 data files processed)
Inserting data attribute into file 142314.
Inserting data attribute into file 142331.
Inserting data attribute into file 142345.
Inserting data attribute into file 142399.
Inserting data attribute into file 142400.
Inserting data attribute into file 142474.
Inserting data attribute into file 142478.
Inserting data attribute into file 142732.
  24268 data files processed.
CHKDSK is verifying Usn Journal...
  35694544 USN bytes processed.
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

  31455238 KB total disk space.
  25472960 KB in 117390 files.
     65496 KB in 24260 indexes.
         0 KB in bad sectors.
    246446 KB in use by the system.
     65536 KB occupied by the log file.
   5670336 KB available on disk.

      4096 bytes in each allocation unit.
   7863809 total allocation units on disk.
   1417584 allocation units available on disk.


Fri Mar 26, 2010 21:30
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfs-3g corrupts volume?
Hi,

Quote:
Anyway, I use Arch Linux x64, i. e. have all the latest software updates :). The very same problem however already occurred in a previous Ubuntu 9.10 installation:

Which ntfs-3g version are you using ? (type "ntfs-3g --help")
Quote:
Virtually always when I boot into Windows 7 x64 after having used Arch, which is configured to allow rw access for (only) my user to my ntfs partitions (three, one on another hdd) I get messages of "filesystem corrupted", but always exclusively for the partition Windows is installed on.

There are apparently two problems.
The first one is about "attribute 128", which is a data attribute, possibly a "Linux extended attribute". I suspect this is about some character which chkdsk for Windows 7 does not allow in files and attributes names. There were about 10 such files (inodes 142314, 142331 etc.). Can you first post the fixed inode data for these files :
Code:
# as root
ntfsinfo -vi <number> <umounted device>

This will at least show the file name and confirm the presence of an extended attribute, but it would be better if you do the same on the unfixed node (recreate the error and do a chkdsk without /f to just get the inode number).

Now, there is another error reported in directories 3679 and 69334. In both situations these are about temporary files (firefox cache ?) which were obviously not created by ntfs-3g, though possibly reused. I would suspect some directory being named with different character case in the Windows and Linux versions of firefox, leading to two names (eg Tmp and tmp) which Windows is not able to distinguish.
Can you also post the current state - or better a corrupt state - of these directories (same as above).

Please gzip the results and attach file, instead of posting them in-line.

*edit*

Do you use the same firefox version on both systems ?

Can you also post the full list of files in the shared firefox directory, with their inodes, after some Linux firefox navigation :
Code:
ls -lRi <shareddirectory>


Regards

Jean-Pierre


Sat Mar 27, 2010 10:20
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
Quote:
Which ntfs-3g version are you using ? (type "ntfs-3g --help")

ntfs-3g 2010.1.16 external FUSE 28

Quote:
which were obviously not created by ntfs-3g

My (uneducated) guess would be that they originate in attempts by Windows applications (e. g. Winamp) to use the Temp directory. Note that unless chkdsk /F is run, I cannot access said folder (via Windows Explorer), but get an error message upon trying to do so.

Quote:
Code:
# as root
ntfsinfo -vi <number> <umounted device>


Can you also post the current state - or better a corrupt state - of these directories (same as above).

Can you also post the full list of files in the shared firefox directory, with their inodes, after some Linux firefox navigation :
Code:
ls -lRi <shareddirectory>

Attached are a copy of my fstab, the results of ntfsinfo and ls after the posted chkdsk /F was executed in "previous" and in "new" are the logs of chkdsk, ntfsinfo and ls after browsing a bit and running Thunderbird on Arch, then booting Windows and there starting Firefox and Winamp. Inodes reports missing are the result of files no longer existing.

Quote:
Do you use the same firefox version on both systems ?

Until the day before I had FF 3.6.3pre nightly installed on Windows, which now replaced by the official 3.6.2 (same version as on Arch, if it wasn't for x86), because I grew tired of the constant extension compatibility checks.

It also occurred to me that esp. after a seemingly unrelated application on Arch (qutIM, to be precise) reports "An I/O error occurred" Firefox starts using ~90 % CPU for about a minute and much of the system acts strange (cursors rapidly blinking; text not properly selectable and keyboard entries only after repeated attempts; windows being properly selectable and displayed, but not resizeable and active...).

Something else:

Every time I boot after having run Windows I get this kind of messages (quoted from my memory):
"unclean file system (0,x)
wasn't safely closed on Windows, fixing
unclean file system (0,x)
wasn't safely closed on Windows, fixing
unclean file system (0,x)
wasn't safely closed on Windows, fixing"

The "x" stands for 0 or 1; they appear seemingly without fixed frequency, though there are always three such messages at most. There are two ntfs partitions on my system drive; the other one is on a hdd connected via eSata. Now I don't know if this is related or of other any interest, but it makes me wonder as it appears to stem from normal Windows behaviour. (Btw, all partitions were formatted by Windows 7.)


Attachments:
File comment: logs of chkdsk, ls, ntfsinfo
ntfs-3g.tar.gz [92.61 KiB]
Downloaded 910 times
Sat Mar 27, 2010 14:40
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
Quote:
ntfs-3g 2010.1.16 external FUSE 28


It just occurred to me that this is not the current stable version. However, unfortunately it is the only one currently available form the official Arch repositories and AUR.


Sat Mar 27, 2010 14:47
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
Shoot, I forgot to include the new chkdsk log.


Attachments:
chkdsk.tar.gz [511 Bytes]
Downloaded 842 times
Sat Mar 27, 2010 15:35
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfs-3g corrupts volume?
Hi,

Your data designates problems in two directories, but so far I could not pinpoint what exact problems they are.

First the directory 69334 (cFosSpeed) containing at least file 142474 (ini1wjqoom8.tmp). This directory contains both the software, installation files and temporary files. All these files were created on Windows. I doubt ntfs-3g has messed with them. 64-bit Windows is said to have problems with sparse files which are commonly used by torrent-type downloads, but there were no sparse file among the descriptions you sent. Have you used cFosSpeed at times related to corrupting the volume ?

Second the directory 3679 (Temp) containing TMP00000* files. This directory was created on Linux and contains files created on Linux and files created on Windows with the same pattern, so this must be a shared file. It also contains files with .sqm suffix, possibly related to msn. Do you know in what circumstances Linux interferes with Temp (you said you cannot enter this directory in Windows until you make a chkdsk) ?

Endly in the chkdsk log, an attribute 128 error is mentioned in file 91653 (ini28pui31r.tmp), but I do not see anything bad in the description you sent. This file was created today at 12:50 UTC. Can you find what software you were using (on Windows) ?

None of these files are part of the firefox profile you sent, and their names are not similar to the ones firefox uses, so I am encline to not charge on firefox.

Quote:
Every time I boot after having run Windows I get this kind of messages (quoted from my memory):
"unclean file system (0,x)
wasn't safely closed on Windows, fixing

That may well be the cause, if Windows leaves the system partition in an inconsistent state. If this is really the case (this would have been reported earlier, but are you using some fast shutdown process ?), separate system and shared data on different partitions, and mount the Windows system partition read-only.

To go further, can you try to identify the software which causes problems, but starting one at a time and starting chkdsk in-between ?

Also would you accept making a metadata image of your partition (with errors present), so that I can analyze what is wrong (but possible unclean shutdowns should be checked first) :
Code:
ntfsclone --metadata -o <imagefile> <unmountedpartition>

The result is likely to be too big (even gzipped) for a mail, so you would have to put it on a public server for me to download.

Regards

Jean-Pierre


Sat Mar 27, 2010 17:34
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
cFosSpeed is a network traffic shaper which constantly runs in the background that I installed along with Windows 7 - months before Ubuntu, Arch and the problems. It surprises me that it would even create temp files - then again, I have never monitored its directories.

Concerning torrent, I seldom use that. Not within the last two weeks, at least. I also use no other way of shutdown than the standard one.

I have no idea when or why Linux would access the Windows temp directories - I merely configured Firefox and Thunderbird to use the same profile, nothing else. The sqm files are to my knowledge somehow related to (user) feedback by Microsoft applications, in my case not MSN (the Messenger is uninstalled) but likely Windows Security Essentials.

Concerning that file 91653, other than the normal background processes I can only recall to have explicitly started Foxit Reader, Firefox, Thunderbird and Winamp. Besides of them I can only think of the ordinary Microsoft services (incl. WSE), hardware programs (Realtek Audio, Intel Rapid Storage, Acer Fingerprint) and Miranda, WideCap and TrueCrypt.

Quote:
can you try to identify the software which causes problems, but starting one at a time and starting chkdsk in-between ?

To tell the truth, I do not really know where to start here. Both installations are (for their respective standards) minimal; I did not have any problems with Windows software and under Arch no other than said two (ought to) make use of the partition.

Quote:
would you accept making a metadata image of your partition

I manually installed the 2010.3.6 release of ntfs-3g today and had to use --force for the program to proceed as it gave a "scheduled for a check" warning. The output on the console was:
Code:
"ntfsclone v2.0.0 (libntfs 10:0:0)
NTFS volume version: 3.1
Cluster size       : 4096 bytes
Current volume size: 32210161664 bytes (32211 MB)
Current device size: 32210164224 bytes (32211 MB)
Scanning volume ...
ERROR: Cluster 4156031 referenced twice!
You didn't shutdown your Windowsproperly?"


I don't get any errors or the likes when I shutdown Windows, though.

The link to the compressed dump is in the PM I sent you.

I suppose my next steps will be to move the FF & TB profile to a fat32 partition, mount the Windows one as ro and see if the bug persists, in which case I would think of it to originate within Windows itself.


Sun Mar 28, 2010 21:34
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfs-3g corrupts volume?
Hi,

Quote:
I manually installed the 2010.3.6 release of ntfs-3g today

I do not expect this to solve your problem.
Quote:
The link to the compressed dump is in the PM I sent you.

I got it, and checked its integrity. I will analyze later.
Quote:
I suppose my next steps will be to move the FF & TB profile to a fat32 partition, mount the Windows one as ro and see if the bug persists

This would be a safe configuration, and this will surely hide the problem... but not much useful to locate the source of the problem.

I am convinced there is something wrong when Windows is shut down. Have you installed the latest Windows updates ? Are you using a special storage hardware or software (RAID or whatever ?)

I also notice your problems seem to be related to temp directories. It would be interesting to redirect them to a directory on FAT.

(continued, later)

Regards

Jean-Pierre


Sun Mar 28, 2010 23:12
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfs-3g corrupts volume?
Hi,

I have begun to analyze you image file, and I notice that nearly all orphaned files detected by chkdsk are parts of file 139844, which is a sparse file related to firefox (could be some Microsoft data collection on crashes). Its full name is :
Users/Andreas/AppData/Local/Microsoft/Windows/WER/ReportQueue/AppCrash_firefox.exe_78e59a9fb969d3e5ccbaad9054d16f712d7972f8_cab_0decb3f5/WERA2F6.tmp.hdmp
As I said earlier, Windows 64bits is known to have problems with sparse files, but this does not explain the relation with Linux being used.
So, if you have not yet moved you shared profile to fat, can you :
- use firefox on Windows,
- switch to Linux, without mounting and dump inode 139844
- mount as rw on Linux, use firefox, unmount and dump again
- also check whether file named above is still in inode 139844
- switch to Windows, and do a chkdsk
- dump inode again
Code:
ntfsinfo -vi 139844 --force <device>


Most of other errors are associated to cFosSpeed or to some other software writing into directory Windows/Temp. These files are apparently not sparse, but there could be inteference with sparse files being used at the same time.

Regards

Jean-Pierre


Mon Mar 29, 2010 11:04
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
I booted Windows today (which ran chkdsk /F at startup), did some Firefox surfing etc. Then I ran chkdsk, which reported that C: was fine.

Did a normal shutdown, booted into Arch, dismounted the Windows (C:) partition (without having started FF or TB).

Since I got the "corrupt file system hd(0,0) // wasn't safely closed" message thrifold, I figured to reboot Windows and run chkdsk (chkdsk1) again - which reported errors.

1. So I started Arch again (without having ran chkdsk /F; yet again the three alerts)
2. unmounted and dumped the ntfsinfo of the three reported files & the directory
3. then did what you wrote in your last message (output in "before")
4. had chkdsk /F run at boot (which then rebooted, i. e. w/o further starting Windows)
5. had Arch give me the three messages again
6. redid your last message (output in "after") - except for booting into Arch after the chkdsk (chkdsk3)
7. I rebooted Windows, running another chkdsk (chkdsk4).

However, it does not appear to me that there is a file at 139844 any more.

Nonetheless, after 4. to 6. - i. e. without the Windows further touching its partition, while having Arch use it - chkdsk (chkdsk3) reported no issues with the partition. Then at 7. - i. e. without involvement of Arch - chkdsk (chkdsk4) reported an "Attribute record (128, "") error.

It hence appears to me that Linux resp. ntfs-3g are not to blame.


Attachments:
reports.7z [28.43 KiB]
Downloaded 871 times
Mon Mar 29, 2010 17:52
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
I forgot to add: The Windows installation and its software is up-to-date; there is no RAID whatsoever.


Mon Mar 29, 2010 18:52
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfs-3g corrupts volume?
Hi,

Your problem will be hard to locate. I suggest you take safety measures before it turns into a nightmare. You should save a full partition image, relocate your shared directory and mount the Windows partition readonly, to exclude any possibility of ntfs-3g as a source cause.

In the three samples you sent, there were files related to cFosSpeed, and I suspect this software to trigger a bug somewhere (the "4156031 referenced twice!" message is about two overlapping files, both from cFosSpeed). You should uninstall it temporarily unless it is important for you.

I also want to correct my diagnosis for WERA2F6.tmp.hdmp (now deleted) : it is not sparse, but compressed, and this is because the directory ReportQueue is marked for compression. You should delete this compression mark (in Windows Explorer select its properties and uncheck compression for all subdirectories and files, and the names should switch from blue to black). Set it again later if this has no impact on the behavior.
*edit* Reports by WER can be turned off in the “Problem Reports and Solutions” applet in Control Panel : this may be easier.*end edit*
Quote:
It hence appears to me that Linux resp. ntfs-3g are not to blame.

I hope you are right...

I am not asking for more tests now, try to get to a safe situation and please report again when something new turns out.

Regards

Jean-Pierre


Mon Mar 29, 2010 19:32
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
Alright, I will do as you advise and update should more information become available. Thanks for the help so far, and again, thanks for ntfs-3g in general! :)


Mon Mar 29, 2010 19:40
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
Darn, I really should have updated this sooner. But better late than never.

Anyway, while I can't say that there was not some sort of interplay between ntfs-3g and Windows, a new installation of the latter resolved the problem. So far I only have chkdsk lament if Linux has crashed.

Which brings me to a different issue, though. Almost always CPU usage spikes and sometimes even the system completely freezes if I try any file operation that involves a large amount of data (regardless of file count) (apparently only) from a ntfs volume to another arbitrary partition (other physical disks with ext4 and btrfs included). These ntfs partitions are clean, the data in question was written by ntfs-3g and it appears as if the problem is considerably more likely to arise if the volume is relatively full (e. g. 15 GiB free of 200 GiB). I always use Nautilus.


Mon Jan 03, 2011 14:37
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: ntfs-3g corrupts volume?
Hi,

Quote:
Almost always CPU usage spikes and sometimes even the system completely freezes if I try any file operation that involves a large amount of data (regardless of file count) (apparently only) from a ntfs volume to another arbitrary partition (other physical disks with ext4 and btrfs included).

Do you have a lot of files in the same directory ? This could be caused by Nautilus opening all the files to identify their contents and display an appropriate icon.

To identify precisely the cause, maybe you can mount with a debug version of ntfs-3g. This will capture execution details and tell where time is spent. I have put such a debug version into http://b.andre.pagesperso-orange.fr/deb ... -3g.tar.gz Unpack and mount with it :
Code:
# mount, as root
./debug-ntfs-3g [-o options] <device> <mountpoint>
# to unmount :
umount <device>

After unmounting, details are written into the file ntfs.log which you can compress and post as an attachment.
Note : this debug version is much slower than the normal version.

Regards

Jean-Pierre


Wed Jan 05, 2011 11:55
Profile

Joined: Fri Mar 26, 2010 21:16
Posts: 10
Post Re: ntfs-3g corrupts volume?
jpa wrote:
Do you have a lot of files in the same directory ? This could be caused by Nautilus opening all the files to identify their contents and display an appropriate icon.


Iirc this has happened both when trying to copy a folder with 2000+ files in subfolders and when attempting to copy (another folder with) one file of ~ the same size as the former (10 GiB+).

jpa wrote:
To identify precisely the cause, maybe you can mount with a debug version of ntfs-3g. This will capture execution details and tell where time is spent.


Thanks, I will do that the next time when such operation is necessary. That could take a couple of weeks, though.


Thu Jan 06, 2011 19:17
Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 16 posts ] 


Who is online

Users browsing this forum: Google [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.