On Sun, Jan 12, 2014 at 07:47:29PM -0800, Zachary Kotlarek wrote: > > On Jan 12, 2014, at 7:19 PM, Dave Chinner <david@xxxxxxxxxxxxx> > wrote: > > > IOWs, xfs-repair wrote new contents to those blocks, and now the > > kernel cannot read them from disk. > > > Sure, but I don’t understand why it would have re-written them > in the first place. I know corruption happens, but this seems > awfully pattern-tastic to be random errors. Neither do I, but I'm trying to find out. > > Try using xfs_db to read and parse the blocks that the > > fielsystem is choking on. If it can't read them from xfs_db, > > then there's something gone wrong below XFS. If you can read > > them, use xfs_db to parse the block as a directory block and see > > what the raw directory entries are the block contains.... Based on the xfs-db output, these warnings are not related to the problem you are seeing. It's likely just a result of readahead being cancelled due to load, and the error set by the DM layer not being handled properly. So, you need to find the inode number of a directory with a corrupt entry, and dump the inode and any data fork blocks that it belongs to with xfs_db similar to what you have just done. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
