On Thu, Jun 01, 2017 at 11:26:26PM +0300, Ivan Sizov wrote: > 2017-06-01 20:35 GMT+03:00 Liu Bo <bo.li....@oracle.com>: > > After I went through the output of leaf's content, most parts of the > > leaf is sane except the two corrupted items, it's still not clear to > > me what caused the corruption, there could be some corner cases that > > I'm not aware of. > > > > If fsck doesn't work for you, then a recovery from backup may be the > > best option. > > I don't need to run any repair procedures because system is working > normally. Most likely that corrupted extents belong to files located > somewhere in /home. > Do you mean I should run fsck in order to determine which files are > corrupted? What are proper options to run fsck with?
I see. Scrub has found that there are some corrupted metadata, if you want to fix that corrupted thing, fsck may be helpful. Due to my test, 'btrfs check /your_disk' fixed my corruption. With this patch set, at least you won't get a crash when accessing the corrupted extent inline ref. -liubo -- 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
