On Sat, May 23, 2020 at 8:38 AM Jiří Lisický <jiri_lisicky@xxxxxxxxx> wrote: > > [root@localhost-live tmp] # btrfs rescue super -v /dev/loop4 > All Devices: > Device: id = 1, name = /dev/loop4 > > Before Recovering: > [All good supers]: > device name = /dev/loop4 > superblock bytenr = 65536 > > device name = /dev/loop4 > superblock bytenr = 67108864 > > [All bad supers]: > > All supers are valid, no need to recover OK. So they're good. > > > > [root@localhost-live tmp]# mount -o ro,recovery /dev/loop4 ./mnt > mount: /home/jirka/tmp/mnt: can't read superblock on /dev/loop4. But it can't be read? This doesn't make sense. What kernel messages are reported at the time of the mount attempt? When using a newer kernel, the recovery command is deprecated but should still work. The new command is 'usebackuproot' What do you get for: # btrfs insp dump-s -fa /dev/ -- Chris Murphy
