On Fri, Dec 01, 2017 at 03:35:07PM -0700, Chandler wrote: > Hi, we had our filesystem crash the other day after getting 100% > full (although 53GB were still reported free). I had to reboot the > system and use xfs_repair. Yup, it tripped over an freespace tree corruption and shut down to prevent it from being propagatd. Could have been caused by anything - hardware, kernel memory corruption, a bug, a MD rebuild issue, etc. Did you save the output of xfs_repair so we can see what errors it fixed up? > It seem to me this shouldn't happen just > because it got full, so maybe there is some other issue? The > filesystem resides on an MD RAID-5 array with 4x 2TB disks that are > in good health, the array gets checked weekly by mdadm. The only > error messages in the system log were related to XFS (see below). > The OS is RHEL 6.9 with kernel 2.6.32-642.11.1.el6.x86_64. Not much we can do to diagnose the problem on old RHEL kernels on upstream lists - the codebase has diverged from upstream too far. Report the problem to your local RHEL support engineer if you need further diagnostic help. Cheers. Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
