Bug 494356
| Summary: | NTFS-3g corrupted my filesystem | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jason Waggoner <waggoneer> |
| Component: | ntfs-3g | Assignee: | Tom "spot" Callaway <tcallawa> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | luke, szaka, tcallawa |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-05-11 21:36:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jason Waggoner
2009-04-06 14:37:04 UTC
There is a newer ntfs-3g update in rawhide (ntfs-3g-2009.4.4-1.fc11) that has some corruption fixes... try to update to that and see if you still get the same errors? I logged into my computer in single-user mode and commented out my ntfs drive to prevent any possible further corruption. I checked the version of ntfs-3g and it was ntfs-3g-2:2009.4.4-1.fc11 (x86_64). I am fairly certain that this version caused my problems. After I did the initial install of Fedora 11 Beta I did a full update before mounting my ntfs drives via fstab. Should I wait for the next ntfs-3g update before I start using it again? It seems you have only one problem: one segment of the NTFS superblock is invalid (uninitialized, empty disk space) between file numbers 33,000-42,000. There can be several reasons for this: 1. One lower layer is temporarily or permanently broken (device driver, disk). 2. If the relevant NTFS info is at the end of the NTFS superblock then the volume was not safely unmounted (i.e. the data was not written to the disk). 3. The issue could be also not NTFS but RAID related. Sometimes they are doing funny things. You should check your logs not only for NTFS but all kind of disk, I/O, RAID, USB errors in the past: http://ntfs-3g.org/support.html#ioerror The reason for the errors is something (apparently rawhide update?) unexpectedly unmounting the NTFS volume: http://forums.fedoraforum.org/showpost.php?p=1198150&postcount=14 gnome-keyring-daemon? doing an unmount of a volume? that looks very odd to me. gnome-keyring-daemon doesn't unmount volumes. It logged that the volume was unmounted/detached/removed/disconnected/etc by something else. Partial logs, like 'grep ntfs' are usually useless because those are symptoms, not reasons. Based on szaka's feedback, I don't think this is a fixable bug in the software. Closing out. |