FAQ SearchLogin
Tuxera Home
View unanswered posts | View active topics It is currently Thu May 13, 2021 00:49



Post new topic Reply to topic  [ 2 posts ] 
mount.ntfs-3g process stuck at 100% and unkillable 
Author Message

Joined: Thu Jan 27, 2011 16:48
Posts: 1
Post mount.ntfs-3g process stuck at 100% and unkillable
I'm trying to use ntfs-3g to perform file-level backups over Xen VMs.
I use lvm snapshot to take a snap of a VM's hd, mount it with ntfs-3g and copy files.
Mount options are force, debug.

All goes well, but on a particular file the system get stucked!

The file is
/System Volume Information/_restore{37FADD86-6CCA-4714-9C94-10AB32C64FD8}
/RP217/snapshot/Repository/FS/INDEX.BTR

When the backup comes on that file (I know that using the debug option, the log is at the end of this post), mount.ntfs-3g start using 100% cpu and the process become unkillable. The only solution to recover is a physical reboot, since also the reboot command doesn't work anymore.

From inside the VM (so using Windows to access the same filesystem), i have to problem in moving the cited file. And if i just remove it, all proceeds without more problems.


More informations on my ntfs-3g package:
Package: ntfs-3g
State: installed
Automatically installed: no
Version: 1:1.2531-1.1

System: Debian 5 Lenny

Here is the log:
Code:
LOOKUP /System Volume Information/_restore{37FADD86-6CCA-4714-9C94-10AB32C64FD8}
/RP217/snapshot/Repository/FS
   NODEID: 78039
   unique: 473679, error: 0 (Success), outsize: 136
unique: 473680, opcode: GETATTR (3), nodeid: 78039, insize: 56
   unique: 473680, error: 0 (Success), outsize: 112
unique: 473681, opcode: OPENDIR (27), nodeid: 78039, insize: 48
   unique: 473681, error: 0 (Success), outsize: 32
unique: 473682, opcode: GETATTR (3), nodeid: 78039, insize: 56
   unique: 473682, error: 0 (Success), outsize: 112
unique: 473683, opcode: READDIR (28), nodeid: 78039, insize: 80
   unique: 473683, error: 0 (Success), outsize: 360
unique: 473684, opcode: READDIR (28), nodeid: 78039, insize: 80
   unique: 473684, error: 0 (Success), outsize: 16
unique: 473685, opcode: RELEASEDIR (29), nodeid: 78039, insize: 64
   unique: 473685, error: 0 (Success), outsize: 16
unique: 473686, opcode: LOOKUP (1), nodeid: 78039, insize: 50
LOOKUP /System Volume Information/_restore{37FADD86-6CCA-4714-9C94-10AB32C64FD8}
/RP217/snapshot/Repository/FS/INDEX.BTR
   NODEID: 78040
unique: 473686, error: 0 (Success), outsize: 136
unique: 473687, opcode: GETATTR (3), nodeid: 78040, insize: 56
   unique: 473687, error: 0 (Success), outsize: 112
unique: 473688, opcode: OPEN (14), nodeid: 78040, insize: 48
   unique: 473688, error: 0 (Success), outsize: 32
OPEN[0] flags: 0x8000 /System Volume Information/_restore{37FADD86-6CCA-4714-9C94-10AB32C64FD8}/RP217/snapshot/Repository/FS/INDEX.BTR
unique: 473689, opcode: GETATTR (3), nodeid: 78040, insize: 56
   unique: 473689, error: 0 (Success), outsize: 112
unique: 473690, opcode: GETATTR (3), nodeid: 78040, insize: 56
   unique: 473690, error: 0 (Success), outsize: 112
unique: 473691, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 0
   READ[0] 131072 bytes
   unique: 473691, error: 0 (Success), outsize: 131088
unique: 473692, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 131072
   READ[0] 131072 bytes
   unique: 473692, error: 0 (Success), outsize: 131088
unique: 473693, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 262144
   READ[0] 131072 bytes
   unique: 473693, error: 0 (Success), outsize: 131088
unique: 473694, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 393216
   READ[0] 131072 bytes
   unique: 473694, error: 0 (Success), outsize: 131088
unique: 473695, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 524288
   READ[0] 131072 bytes
   unique: 473695, error: 0 (Success), outsize: 131088
unique: 473696, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 655360
   READ[0] 131072 bytes
   unique: 473696, error: 0 (Success), outsize: 131088
unique: 473697, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 786432
   READ[0] 131072 bytes
   unique: 473697, error: 0 (Success), outsize: 131088
unique: 473698, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 917504
   READ[0] 131072 bytes
   unique: 473698, error: 0 (Success), outsize: 131088
unique: 473699, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 1048576
   READ[0] 131072 bytes
unique: 473699, error: 0 (Success), outsize: 131088
unique: 473700, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 1179648
   READ[0] 131072 bytes
   unique: 473700, error: 0 (Success), outsize: 131088
unique: 473701, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 1310720
   READ[0] 131072 bytes
   unique: 473701, error: 0 (Success), outsize: 131088
unique: 473702, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 1441792
   READ[0] 131072 bytes
   unique: 473702, error: 0 (Success), outsize: 131088
unique: 473703, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 1572864
   READ[0] 131072 bytes
   unique: 473703, error: 0 (Success), outsize: 131088
unique: 473704, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 131072 bytes from 1703936
   READ[0] 131072 bytes
   unique: 473704, error: 0 (Success), outsize: 131088
unique: 473705, opcode: READ (15), nodeid: 78040, insize: 80
READ[0] 98304 bytes from 1835008


Any help is appreciated, thank you
best regards,
Roberto


Thu Jan 27, 2011 17:41
Profile
NTFS-3G Lead Developer

Joined: Tue Sep 04, 2007 17:22
Posts: 1286
Post Re: mount.ntfs-3g process stuck at 100% and unkillable
Hi,

Quote:
Version: 1:1.2531-1.1

This is an old version (two years), if you need a fix you must upgrade.

Quote:
The file is
/System Volume Information/_restore{37FADD86-6CCA-4714-9C94-10AB32C64FD8}
/RP217/snapshot/Repository/FS/INDEX.BTR

This is a compressed file (an easy way to check is to compare the results of "du -s <file>" and "du -s --apparent-size <file>"). A bug causing a loop when reading a corrupt compressed file or a compressed file located on a bad sector was fixed in ntfs-3g-2010.8.8. This fix detects the bad condition, and issues an error, but the bad condition remains unchanged.

I would suggest you first do a "chkdsk /f" on Windows. This will probably delete the file (which is only useful for reverting some Windows upgrading).

Anyway, upgrading to a recent ntfs-3g version would prevent you from getting into known bugs which have been fixed.

Regards

Jean-Pierre


Thu Jan 27, 2011 19:51
Profile
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 2 posts ] 


Who is online

Users browsing this forum: No registered users and 3 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:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Original forum style by Vjacheslav Trushkin.