On 2018年07月04日 06:00, Marc MERLIN wrote: > On Tue, Jul 03, 2018 at 03:46:59PM -0600, Chris Murphy wrote: >> On Tue, Jul 3, 2018 at 2:50 AM, Qu Wenruo <quwenruo.btrfs@xxxxxxx> wrote: >>> >>> >>> There must be something wrong, however due to the size of the fs, and >>> the complexity of extent tree, I can't tell. >> >> Right, which is why I'm asking if any of the metadata integrity >> checker mask options might reveal what's going wrong? >> >> I guess the big issues are: >> a. compile kernel with CONFIG_BTRFS_FS_CHECK_INTEGRITY=y is necessary >> b. it can come with a high resource burden depending on the mask and >> where the log is being written (write system logs to a different file >> system for sure) >> c. the granularity offered in the integrity checker might not be enough. >> d. might take a while before corruptions are injected before >> corruption is noticed and flagged. > > Back to where I'm at right now. I'm going to delete this filesystem and > start over very soon. Tomorrow or the day after. > I'm happy to get more data off it if someone wants it for posterity, but > I indeed need to recover soon since being with a dead backup server is > not a good place to be in :) Feel free to recover asap, as the extent tree is really too large for human to analyse manually. Thanks, Qu > > Thanks, > Marc > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
