Bug 1314911
| Summary: | XFS Corruption | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher Bachner <b.christopher.92> |
| Component: | kernel | Assignee: | Eric Sandeen <esandeen> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | b.christopher.92, esandeen, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab |
| 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: | 2016-03-07 20:10:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Christopher Bachner
2016-03-04 20:34:03 UTC
Hit some sort of btree corruption, I would follow the advice:
> Mar 04 09:12:49 fedora23 kernel: XFS (sda5): Please umount the filesystem and rectify the problem(s)
by the following steps:
* Unmount the filesystem
* Mount the filesystem again to replay the log if needed
* Unmount the filesystem again
* Run xfs_repair (first with the -n option to be sure it doesn't look too catastrophic)
* Save the output and attach it to this bug.
When I tried to mount the filesystem, I got a "structure needs cleaning." So I had to basically force an xfs_repair. After that I was able to mount it and copy off all my files. I decided to change to ext4 for now because I got two xfs corruptions in such a short time period. However, could this be due to bad ram? Maybe I should run some memtest? I did all of this when I filed the bug, so I was not able to save the output of xfs_repair. Thanks Sounds like log replay failed too; this could indicate a storage problem as well... but without more logs, or xfs_repair output, etc, it's hard to know what has happened. |