Hi Roman, If you look at the 'show' command, the failing disk is sorta out of the fs, so maybe removing the 6TB disk again will divide the data already on the 6TB disk (which isn't more than 300something gigs) to the 2 well-functioning disks.
Still, as putting the dd-image of the 2TB disk on the temporary disk is only temporary, I do need one more 2TB+ disk attached to create a more permanent btrfs with the 6TB disk (which is what I eventually want). And for that I need some more harddisk power cables/splitters. And another disk. But that still seems to be the best option, so I will do that once I have those things sorted out. Thanks for your creative suggestion :) /klaus On Tue, Nov 14, 2017 at 4:44 PM, Roman Mamedov <r...@romanrm.net> wrote: > On Tue, 14 Nov 2017 15:09:52 +0100 > Klaus Agnoletti <kl...@agnoletti.dk> wrote: > >> Hi Roman >> >> I almost understand :-) - however, I need a bit more information: >> >> How do I copy the image file to the 6TB without screwing the existing >> btrfs up when the fs is not mounted? Should I remove it from the raid >> again? > > Oh, you already added it to your FS, that's so unfortunate. For my scenario I > assumed have a spare 6TB (or any 2TB+) disk you can use as temporary space. > > You could try removing it, but with one of the existing member drives > malfunctioning, I wonder if trying any operation on that FS will cause further > damage. For example if you remove the 6TB one, how do you prevent Btrfs from > using the bad 2TB drive as destination to relocate data from the 6TB drive. Or > use it for one of the metadata mirrors, which will fail to write properly, > leading into transid failures later, etc. > > -- > With respect, > Roman -- Klaus Agnoletti -- 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
