ntfs-3g crashed with SIGSEGV in ntfs_attr_lookup()

[pdaemon]

Binary package hint: ntfs-3g

Description: Ubuntu jaunty (development branch)
Release: 9.04

Recieved report the ntfs-3g unexpectely closed and I couldn't mount my NTFS disks...

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /bin/ntfs-3g
NonfreeKernelModules: nvidia
Package: ntfs-3g 1:2009.1.1-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /sbin/mount.ntfs-3g /dev/sdd2 /media/Backup_DataStore -o rw,nosuid,nodev,uhelper=hal,locale=en_AU.UTF-8
ProcEnviron:

Signal: 11
SourcePackage: ntfs-3g
StacktraceTop:
 ntfs_attr_lookup () from /lib/libntfs-3g.so.48
 ntfs_inode_lookup_by_name ()
 ntfs_pathname_to_inode () from /lib/libntfs-3g.so.48
 ?? ()
 ?? () from /lib/libfuse.so.2
Title: ntfs-3g crashed with SIGSEGV in ntfs_attr_lookup()
Uname: Linux 2.6.28-7-generic x86_64
UserGroups:

[pdaemon (philipp-burath)]

After a few minutes ntfs-3g must reload and the disk comes back online...

[pdaemon (philipp-burath)]

OK, this seems to be related to a hardware problem with my disk. Sorry about that! Could this bug please be closed.

[Apport retracing service (apport)]

StacktraceTop:ntfs_attr_lookup (type=AT_INDEX_ROOT,
ntfs_inode_lookup_by_name (dir_ni=0x21f6420,
ntfs_pathname_to_inode (vol=0x21f1b60, parent=0x0,
ntfs_fuse_getattr (org_path=<value optimized out>,
lookup_path (f=0x21f5130, nodeid=8,

[Hew (hew)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please update Jaunty to include ntfs-3g 1:2009.2.1-0ubuntu1, and test if the problem still occurs? I have removed the sensitive data from the stacktrace. Thanks in advance.

[Szabolcs Szakacsits (szaka)]

NTFS-3G 2009.2.1 did fix a crash in ntfs_attr_lookup if a file or directory (this is the case here) was highly fragmented and there was an NTFS corruption or hardware problem: http://ntfs-3g.org/releases.html

[Szabolcs Szakacsits (szaka)]

The crash happens exactly at the same place which was fixed in NTFS-3G 2009.2.1.

However the stack trace doesn't look correct. There are some problems with it. Like apparently using debug symbols from the NTFS-3G 2009.2.1 release and manual edition of vital parameters to corrupt values which should never happen.

[Hew (hew)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!