On 09/29/2017 08:55 AM, Roman Mamedov wrote:
On Fri, 29 Sep 2017 00:23:28 -0400
Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx> wrote:
This was a RAID6 with 8 devices. Instead of using --grow with
--raid-devices set to 9, I did the following:
mdadm --grow /dev/md128 --size 9
This happily returned without any errors so I went to go look at
/proc/mdstat and did not see a resize operation going. So I shook my
head and read the output of --grow --help and did the right thing which is:
mdadm --grow /dev/md128 --raid-devices=9
The output of the first command is:
# mdadm --grow /dev/md0 --size 9
mdadm: component size of /dev/md0 has been set to 9K
unfreeze
It didn't occur to you that you FIRST need to restore the "component size" back
to what it was previously?...
I am not sure that I actually got any response at all from setting
--size. I am running version:
mdadm - v3.4 - 28th January 2016
If I did get output, I totally missed it. I get that this is my fault
for using the wrong commmand and any data loss is totally due to my
stupidity. I am just hoping that there might be a way that I can get the
data back.
And yes as John says there should be a confirmation request on reducing the
array size. In fact I couldn't believe there isn't one already, that's why I
went checking. But nope, there are no warnings or confirmation requests
neither for reducing --size, nor --array-size. I might be remembering that
there were some, from LVM, not MD.
--
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
