Version-Release number of selected component: ntfsprogs-2013.1.13-1.fc18.1 Additional info: backtrace_rating: 4 cmdline: fsck.ntfs /dev/sdb1 core_backtrace: 46867bbfd8387b8ed0fc56bc992381ac2fe38903 0x188d main /usr/bin/ntfsck 0d88cc737605126aa713262561d8e775390514b1 crash_function: check_file_record executable: /usr/bin/ntfsck kernel: 3.8.6-203.fc18.x86_64 uid: 0 ureports_counter: 2 Truncated backtrace: Thread no. 1 (3 frames) #0 check_file_record at ntfsck.c:624 #1 verify_mft_record at ntfsck.c:696 #2 check_volume at ntfsck.c:778
Created attachment 734779 [details] File: backtrace
Created attachment 734780 [details] File: cgroup
Created attachment 734781 [details] File: dso_list
Created attachment 734782 [details] File: environ
Created attachment 734783 [details] File: limits
Created attachment 734784 [details] File: maps
Created attachment 734785 [details] File: open_fds
Created attachment 734786 [details] File: proc_pid_status
Created attachment 734787 [details] File: var_log_messages
Created attachment 735251 [details] Proposed patch for using ntfsck on 4K-sector disks This is apparently caused by using ntfsck for a 4K-sector disk... Can you try the attached patch ?
Jean-Pierre, I'm not sure if this user will come back to test or not (this crash report was filed automatically by the Fedora ABRT system). I don't have a 4K-sector disk handy to test this on, but I applied the patch to a test package: http://kojipkgs.fedoraproject.org//work/tasks/3423/5253423/ntfsprogs-2013.1.13-2.fc18.1.x86_64.rpm Full Koji Scratch Build is here: http://koji.fedoraproject.org/koji/taskinfo?taskID=5253422
> I'm not sure if this user will come back to test or not Well, anybody having a similar problem might check whether it had already been notified, with a possible fix available. > I don't have a 4K-sector disk handy For testing purposes, you can use a traditional disk and format it with mkntfs and option "-s4096" to get a 4K sector layout.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.