On Sun, Jul 1, 2018 at 10:27 AM, Marc MERLIN <m...@merlins.org> wrote: > Howdy, > > I have a btrfs filesystem made out of 2 devices: > [ 75.141414] BTRFS: device label btrfs_space devid 1 transid 429220 > /dev/bcache3 > [ 75.164745] BTRFS: device label btrfs_space devid 2 transid 429220 > /dev/bcache2 > > One of the 2 devices had a hardware error (not btrfs' fault): > [201504.939659] BTRFS error (device bcache3): bdev /dev/bcache2 errs: wr 552, > rd 39, flush 1, corrupt 0, gen 0 > [201504.995967] BTRFS warning (device bcache3): bcache3 checksum verify > failed on 399998976 wanted F3019EEA found E6A97DC4 level 0 > [201505.032209] BTRFS error (device bcache3): bdev /dev/bcache2 errs: wr 552, > rd 40, flush 1, corrupt 0, gen 0 > [201505.062447] BTRFS error (device bcache3): parent transid verify failed on > 399998976 wanted 434763 found 434245 > [201600.262142] BTRFS error (device bcache3): bdev /dev/bcache2 errs: wr 552, > rd 41, flush 1, corrupt 0, gen 0 > > I unmounted it, and I'm trying to check the filesystem now.
Is it raid0 metadata? Because if it's raid1 metadata it should have passively recovered from a good copy and then fixed the bad copy. > > How is it supposed to work when you have multiple devices for a btrfs > filesystem? > > gargamel:~# btrfs check --repair -p /dev/bcache2 > enabling repair mode > ERROR: mount check: cannot open /dev/bcache2: No such device or address > ERROR: could not check mount status: No such device or address > gargamel:~# btrfs check --repair -p /dev/bcache3 > enabling repair mode > ERROR: cannot open device '/dev/bcache3': Device or resource busy > ERROR: cannot open file system > > [205248.299528] BTRFS info (device bcache3): disk space caching is enabled > [205248.320335] BTRFS error (device bcache3): Remounting read-write after > error is not allowed If it's successfully unmounted, I don't understand the error messages that it can't be opened. Is umount hung? Sounds to me like btrfs check thinks it's still mounted. -- Chris Murphy -- 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
