>>>>> "Eli" == Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx> writes: Eli> On 09/29/2017 03:33 PM, John Stoffel wrote: >>>>>>> "Eli" == Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx> writes: >> Eli> On 09/29/2017 08:38 AM, John Stoffel wrote: >>>>>>>>> "Eli" == Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx> writes: >>>> Eli> I need to add another disk to my array (/dev/md128) when I accidentally Eli> did an array resize to 9 with the following command: >>>> Eli> First I add the disk to the array with the following: >>>> Eli> mdadm --manage /dev/md128 --add /dev/sdl >>>> Eli> This was a RAID6 with 8 devices. Instead of using --grow with Eli> --raid-devices set to 9, I did the following: >>>> Eli> mdadm --grow /dev/md128 --size 9 >>>> Eli> This happily returned without any errors so I went to go look at Eli> /proc/mdstat and did not see a resize operation going. So I shook my Eli> head and read the output of --grow --help and did the right thing which is: >>>> Eli> mdadm --grow /dev/md128 --raid-devices=9 >>>> Eli> Right after that everything hit the fan. dmesg reported a lot of Eli> filesystem errors. I quickly stopped all processes that were using this Eli> device and unmounted the filesystems. I then, stupidly, decided to Eli> reboot before looking around. >>>> >>>> >>>> I think you *might* be able to fix this with just a simple: >>>> >>>> mdadm --grow /dev/md128 --size max >>>> >>>> And then try to scan for your LVM configuration, then fsck your volume >>>> on there. I hope you had backups. >>>> >>>> And maybe there should be a warning when re-sizing raid array elements >>>> without a --force option if going smaller than the current size? >> Eli> I just tried that and got the following error: >> Eli> mdadm: Cannot set device size in this type of array >> Eli> Trying to go further down this path, I also tried to set the size Eli> explicitly with: >> Eli> mdadm --grow /dev/md150 --size 1953383512 >> Eli> but got: >> Eli> mdadm: Cannot set device size in this type of array >> Eli> I am curious if my data is actually still there on disk. >> Eli> What does the --size with --grow actually do? >> >> It changes the size of each member of the array. The man page >> explains it, though not ... obviously. >> >> Are you still running with the overlays? That would explain why it >> can't resize them bigger. But I'm also behind on email today... Eli> I was still using the overlay. I just tried the grow without the overlay Eli> and got the same error. Hmm.. what do the partitions on the disk look like now? You might need to do more digging. But I would say that using --grow and having it *shrink* without any warnings is a bad idea for the mdadm tools. It should scream loudly and only run when forced to like that. Aw crap... you used the whole disk. I don't like doing this because A) if I get a disk slightly *smaller* than what I currently have, it will be painful, B) it's easy to use a small partition starting 4mb from the start and a few hundred Mb (or even a Gb) from the end. In your case, can you try to do the 'mdadm --grow /dev/md### --size max' but with a version of mdadm compiled with debugging info, or at least using the latest version of the code if at all possible. Grab it from https://github.com/neilbrown/mdadm and when you configure it, make sure you enable debugging. Or grab it from https://www.kernel.org/pub/linux/utils/raid/mdadm/ and try the same thing. Can you show the output of: cat /proc/partitions as well? Maybe you need to do: mdadm --grow <dev> --size ######## which is the smallest of the max size of all your disks. Might work... -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
