On Fri, Feb 26, 2010 at 01:11:57PM -0500, Bill Pemberton wrote: > > > > Does the array have any kind of writeback cache? > > > > Yes, the array has a writeback cache.
Ok, this would be my top suspect then, especially if it had to be powered off to reset it. The errors you sent look like some IO just didn't happen, which the btrfs code goes to great length to detect and complain about. Going back to the errors: parent transid verify failed on 20971520 wanted 206856 found 214247 parent transid verify failed on 20971520 wanted 206856 found 214247 parent transid verify failed on 20971520 wanted 206856 found 214247 btrfsck: disk-io.c:723: open_ctree_fd: Assertion `!(!chunk_root->node)' failed. Aborted (core dumped) You're actually hitting this very early in the mount. We read in the super block and then we read all the tree roots it points to. Each pointer includes the generation number it expects to find. The generation number is similar to a version counter. Each transaction that updates that block increments the generation number. So, the super block says: go read block number 20971520, and it is supposed to be generation 206856. Instead we find: 214247, which is much newer. The most likely cause of this is that a write to either the super block or block 20971520 went to the writeback cache but never made it to the drive. My would be the super block, it is updated more often and so more likely to get stuck in the array's cache. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
