On Mon, Apr 11, 2016 at 3:51 PM, lenovomi <lenovomi@xxxxxxxxx> wrote: > Hi, > > i didnt try mount -o ro, when i tried to mount it via esata i got > kernel panic immediately. Then i conntected enclosure with drives via > usb and tried to mount it : OK so try '-o ro,recovery' and report back what you get. > > https://bpaste.net/show/641ab9172539 > plugged via usb -> mount randomly one of the drive mount /dev/sda /mnt/brtfs > > I was told on irc channel that i should not run btrfs check and if so > i should run it as > btrfs check --repair --init-extent-tree > > > Also there was recommendation to run btrfs restore before repair. Did you use btrfs restore? https://btrfs.wiki.kernel.org/index.php/Restore And did you use --repair --init-extent-tree? I don't recommend it until you use restore as well. > Still not clear what should i do as next step. 1. mount with -o ro,recovery and get important date backed up. It sounds like you don't have a backup? 2. If that doesn't work, use btrfs restore. It's tedious but at least you can update your backup. 3. Next try btrfs check without repair. There's some nuance whether it's better to use init-extent-tree or try zeroing the log. But don't use repair until there's a current backup with 1 or 2. -- Chris Murphy -- 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
