On 12/07/17 15:05, Andrei Borzenkov wrote:
On Wed, Jul 12, 2017 at 4:49 PM, Wols Lists <antlists@youngman.org.uk> wrote:
But I suspect that going back into 12.2, and shrinking the filesystem (MAKE SURE you shrink the md device, not the sd device)
Quite the opposite. Attempting to shrink filesystem that is already effectively corrupted is potentially dangerous. So the right thing here is to stop md, backup superblocks (in case they will be overwritten in the process), shrink filesystem on physical device (after fsck'ing it to fix metadata that may be located "under" md superblock) and then reassembling md again, possibly restoring superblock from backup.
There is no need to go back to 12.2 for that.
I'm thinking that the filesystem starts at the beginning of the md device, the superblock is at the end. So shrinking the filesystem would "release" the superblock and shouldn't write anything anywhere near it because it's in the space that's being freed. Remember - you can access a filesystem within a raid 1 mirror without needing the raid to be running ... But yes, my feeling would be to create a new array and copy the data across. It's safer. Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org