Op 12-06-17 om 00:58 schreef Chris Murphy: [..]
> Also worth trying btrfs check --mode=lowmem. This doesn't repair but > is a whole new implementation so it might find the source of the > problem better than the current fsck. I ran it under 'catchsegv' to give more data where it segfaults, here's the log: https://dominion.thruhere.net/btrfsck-lowmem.txt.gz It's 688K compressed and 16MiB uncompressed. regards, Koen -- 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
