> I'm not sure what you mean by isolate, or what's meant by recover all > data. To recover all data on all four disks suggests replicating all > of it to another file system - i.e. backup, rsync, snapshot(s) + > send/receive.
I mean, dd the disk to a file and copy the data, before replacing the broken disk. > Are there any kernel messages reporting btrfs problems with this file > system? That should be resolved as a priority before anything else. No, the fs is fine and i stopped using it when the disk port broke. > Also, DUP metadata for multiple device btrfs is suboptimal. It's a > single point of failure. I suggest converting to raid1 metadata so the > file system can correct for drive specific problems/bugs by getting a > good copy from another drive. If it's the case DUP metadata is on the > drive with the bad sata cable, that could easily result in loss or > corruption of both copies of metadata and the whole file system can > implode. I'll try to convert the whole fs as soon as I get a new disk for replacement. Em sáb., 23 de jan. de 2021 às 03:29, Chris Murphy <[email protected]> escreveu: > > On Mon, Jan 18, 2021 at 5:02 PM Hérikz Nawarro <[email protected]> > wrote: > > > > Hello everyone, > > > > I got an array of 4 disks with btrfs configured with data single and > > metadata dup, one disk of this array was plugged with a bad sata cable > > that broke the plastic part of the data port (the pins still intact), > > i still can read the disk with an adapter, but there's a way to > > "isolate" this disk, recover all data and later replace the fault disk > > in the array with a new one? > > I'm not sure what you mean by isolate, or what's meant by recover all > data. To recover all data on all four disks suggests replicating all > of it to another file system - i.e. backup, rsync, snapshot(s) + > send/receive. > > Are there any kernel messages reporting btrfs problems with this file > system? That should be resolved as a priority before anything else. > > Also, DUP metadata for multiple device btrfs is suboptimal. It's a > single point of failure. I suggest converting to raid1 metadata so the > file system can correct for drive specific problems/bugs by getting a > good copy from another drive. If it's the case DUP metadata is on the > drive with the bad sata cable, that could easily result in loss or > corruption of both copies of metadata and the whole file system can > implode. > > -- > Chris Murphy
