ntfs-3g crashed while copying files to an external USB drive (in ntfs_mft_record_alloc)

[lozioric]

Binary package hint: ntfs-3g

While copying files from my EXT-3 home partition to an external, NTFS-formatted USB hard disk drive, ntfs-3g crashed.
I restarted my Ubuntu box; meanwhile, I ran CHKDSK on the USB drive from a Windows PC (it found quite a lot of "lost" files, as I was kind of expecting).
When I tried again to copy the same files, ntfs-3g crashed again, though the copy operation proceeded further than the first time. This second crash is the one I included information about.
I am using Ubuntu 7.10 with up-to-date packages, on a Toshiba Satellite A100 notebook.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Tue Mar 18 12:45:18 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /bin/ntfs-3g
NonfreeKernelModules: fglrx
Package: ntfs-3g 1:1.913-2ubuntu1
PackageArchitecture: i386
ProcCmdline: /sbin/mount.ntfs-3g /dev/sdb1 /media/Archivio -o rw,nosuid,nodev,locale=it_IT.UTF-8
ProcCwd: /
ProcEnviron:

Signal: 11
SourcePackage: ntfs-3g
StacktraceTop:
 ntfs_mft_record_alloc () from /lib/libntfs-3g.so.12
 ?? () from /lib/libntfs-3g.so.12
 ?? ()
 ?? ()
 ?? ()
Title: ntfs-3g crashed with SIGSEGV in ntfs_mft_record_alloc()
Uname: Linux Claudine 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
UserGroups:

Stacktrace:
#0 0xb7fbe78f in ntfs_mft_record_alloc (vol=0x805a4a8, base_ni=0x80a9228)
#1 0xb7fab0e1 in ntfs_resident_attr_resize (na=0x80a9dc8, newsize=768)
#2 0xb7fab896 in ntfs_attr_truncate (na=0x80a9dc8, newsize=768)
#3 0xb7fb4d93 in ntfs_ir_truncate (icx=0x80a9bf8, data_size=752)
#4 0xb7fb549e in ntfs_ir_make_space (icx=0x80a9bf8, data_size=134914992)
#5 0xb7fb64c1 in ntfs_ie_add (icx=0x80a9bf8, ie=0x80a9b78) at index.c:1470
  1465:
  1466: ntfs_log_trace("index block sizes: allocated: %d needed: %d\n",
  1467: allocated_size, new_size);
  1468:
  1469: if (icx->is_in_root) {
  1470: if (ntfs_ir_make_space(icx, new_size) == STATUS_ERROR)
  1471: goto err_out;
  1472: } else {
  1473: if (ntfs_ib_split(icx, icx->ib) == STATUS_ERROR)
  1474: goto err_out;
  1475: }
#6 0xb7fb6e5d in ntfs_index_add_filename (ni=0x80a9228, fn=0x80a9b10,
#7 0xb7fb1ffa in __ntfs_create (dir_ni=0x80a9228, name=0x80a84e8,
#8 0xb7fb242b in ntfs_create (dir_ni=0x80a9228, name=0x80a84e8,
#9 0x0804ac7c in ntfs_fuse_create (org_path=<value optimized out>,
#10 0x0804dc75 in ntfs_fuse_mknod (
#11 0xb7f8bab0 in fuse_fs_mknod (fs=0x805da80,
#12 0xb7f90732 in fuse_lib_mknod (req=0x80a7250, parent=3487,
#13 0xb7f94a1e in do_mknod (req=0x80a7250, nodeid=3487, inarg=0x80aa3b0)
#14 0xb7f956e3 in fuse_ll_process (data=0x805e598, buf=0xb7cb2008 "B", len=66,
#15 0xb7f96ef6 in fuse_session_process (se=0x805a488, buf=0xb7cb2008 "B",
#16 0xb7f92f85 in fuse_session_loop (se=0x805a488) at fuse_loop.c:33
  [Error: fuse_loop.c was not found in source tree]
#17 0xb7f8edd8 in fuse_loop (f=0x80aa3b0) at fuse.c:2808
  [Error: fuse.c was not found in source tree]
#18 0x0804c696 in main (argc=) at ntfs-3g.c:2299
  2294: ctx->vol->vol_name, ctx->vol->major_ver,
  2295: ctx->vol->minor_ver);
  2296: ntfs_log_info("Cmdline options: %s\n", opts.options);
  2297: ntfs_log_info("Mount options: %s\n", parsed_options);
  2298:
  2299: fuse_loop(fh);
  2300:
  2301: fuse_unmount(opts.mnt_point, fc);
  2302: fuse_destroy(fh);
  2303: err = 0;
  2304: err_out:
#19 0xb7e2c050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#20 0x08049971 in _start ()

SegvAnalysis:
 Segfault happened at: 0xb7fbe78f <ntfs_mft_record_alloc+3455>: movzwl (%eax,%edx,1),%eax
 PC (0xb7fbe78f) ok
 source "(%eax,%edx,1)" (0x080b93eb) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA

[Apport retracing service (apport)]

StacktraceTop:ntfs_mft_record_alloc (vol=0x805a4a8, base_ni=0x80a9228)
ntfs_resident_attr_resize (na=0x80a9dc8, newsize=768)
ntfs_attr_truncate (na=0x80a9dc8, newsize=768)
ntfs_ir_truncate (icx=0x80a9bf8, data_size=752)
ntfs_ir_make_space (icx=0x80a9bf8, data_size=134914992)

[Szabolcs Szakacsits (szaka)]

Thanks for the bug report.

What Windows version (XP, Vista, Service Packs, etc) do you use?

Did you use a 3rd party NTFS driver (Partition Magic, Ghost, security software, etc)?

Could you please send to <email address hidden> the extracted NTFS information according to http://www.linux-ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata and the compressed /var/log/daemon.log file for debugging?

Thanks, Szaka

[lozioric (lozioric)]

> What Windows version (XP, Vista, Service Packs, etc) do you use?

XP Pro SP2, Italian, with up-to-date security updates.

> Did you use a 3rd party NTFS driver (Partition Magic, Ghost, security
> software, etc)?

I had used Acronis TrueImage once on the affected disk, but I had run
Chkdsk on it a couple of times since, so it hardly matters IMHO.

> Could you please send to <email address hidden> the extracted NTFS
> information according to http://www.linux-
> ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata and the
> compressed /var/log/daemon.log file for debugging?

Unfortunately I don't have the disk with me, nor will I for some days.
In the meantime it is being used with other Windows boxes (all XP SP2,
same as above). Will the info still be useful if I send them in a week
or so?

Thanks for your efforts, keep up the good work
Ric

[Szabolcs Szakacsits (szaka)]

On Mon, 31 Mar 2008, lozioric wrote:
> > What Windows version (XP, Vista, Service Packs, etc) do you use?
>
> XP Pro SP2, Italian, with up-to-date security updates.
>
> > Did you use a 3rd party NTFS driver (Partition Magic, Ghost, security
> > software, etc)?
>
> I had used Acronis TrueImage once on the affected disk, but I had run

Ok, Acronis is known to have problem with NTFS.

> Chkdsk on it a couple of times since, so it hardly matters IMHO.

Chkdsk is not reliable. It also has several known problems.

> Unfortunately I don't have the disk with me, nor will I for some days.
> In the meantime it is being used with other Windows boxes (all XP SP2,
> same as above). Will the info still be useful if I send them in a week
> or so?

Yes, it would be useful if you can still reproduce the problem (what you
should). No problem when you can do it since I'm fairly sure the problem
is Acronis related which is not used by many people. Your problem is unique.

Thanks.

[lozioric (lozioric)]

Sorry for the late answer, I've been away and I'm catching up with a
ton of unread mail.

> Ok, Acronis is known to have problem with NTFS.

Not what I'd call good news, considering that I use Acronis quite
extensively; nice to know, nevertheless.

> Chkdsk is not reliable. It also has several known problems.

Is there anything you may suggest to check a NTFS partition reliably?
Other than see if ntfs-3g crashes on it, I mean... :-) In other words,
what could I do between using Acronis and accessing the same disk with
ntfs-3g to be sure that the file system is not messed up?

Thanks for your patience
Ric

[Szabolcs Szakacsits (szaka)]

If ntfs-3g crashes then please send to <email address hidden> the NTFS information according to http://www.linux-ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata
and the compressed /var/log/daemon.log file.

Otherwise we can't help. Nobody else is having this problem, so you're the only one who can provide us the needed debug information for investigation.

Regards, Szaka

==
NTFS-3G Lead Developer: http://ntfs-3g.org