On Tue, Jul 3, 2018 at 2:50 AM, Qu Wenruo <[email protected]> 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. So it might be pointless, no idea. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
