On Tue, Jul 30, 2019 at 5:13 PM Graham Cobb <g.btrfs@xxxxxxxxxxx> wrote: > > On 30/07/2019 23:44, Swâmi Petaramesh wrote: > > Still, losing a given FS with subvols, snapshots etc, may be very > > annoying and very time consuming rebuilding. > > I believe that in one of the earlier mails, Qu said that you can > probably mount the corrupted fs readonly and read everything. > > If that is the case then, if I were in your position, I would probably > buy another disk, create a a new fs, and then use one of the subvol > preserving btrfs clone utilities to clone the readonly disk onto the new > disk. > > Not cheap, and would still take some time, but at least it could be > automated. btrfstune might allow the seeding flag to be changed on this volume; I'm not sure what kind of checks are done to see if it's viable; but also the seed feature is somewhere between tricky and unsupported in multiple device contexts. But yeah if it's readonly mountable, it should be possible to script `btrfs send-receive` based replication for the ro snapshots anyway, to preserve shared extents. -- Chris Murphy
