> > > > 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. >
While the arrays were powered off in both cases, it was well after the original problem was observed, so I would have expected the array to flush the cache by then. In any event, the biggest issue is that I'm left with a totally unrecoverable filesystem. On these filesystems I can live with "something strange happened and you lost some files", but in this case it's "something strange happened you lost 1TB". -- Bill -- 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
