From: Phil Turmel <philip@turmel.org>
To: Rory Jaffe <rsjaffe@gmail.com>
Cc: Mikael Abrahamsson <swmike@swm.pp.se>, linux-raid@vger.kernel.org
Subject: Re: RAID5 Shrinking array-size nearly killed the system
Date: Sun, 13 Mar 2011 09:33:45 -0400 [thread overview]
Message-ID: <4D7CC7B9.3010207@turmel.org> (raw)
In-Reply-To: <AANLkTi=ZtxFJDtYCP62BZDg5=QyM3873eNDXZqC2c_wu@mail.gmail.com>
Hi Rory,
On 03/13/2011 01:56 AM, Rory Jaffe wrote:
>> OK, so your new array size will be 5857612608 (1952537536 * 3) == 5586GB
>>
>> You can use an initial resize2fs to 5.4T to speed things up, as you don't really need to move items that are currently located between the 3.8T and 5.4T mark. Then use the exact "mdadm --grow /dev/md0 --array-size=5857612608" afterwards before you fsck it.
>>
>> If that passes, do the rest. The final resize2fs should be very quick.
>>
>> Phil
>>
>
> One more glitch? I ran the following command, trying several different
> locations for the backup file, all of which have plenty of space and
> are not on the array.
>
> sudo mdadm -G /dev/md/0_0 -n 4 --backup-file=/tmp/backmd
>
> mdadm gives the message "mdadm: Need to backup 960K of critical
> section.." and it immediately returns to the command prompt without
> shrinking the array.
Are you sure its not doing the reshape? "cat /proc/mdstat" will show whats happening in the background.
Also, check your dmesg to see if there are any explanatory messages.
Phil
next prev parent reply other threads:[~2011-03-13 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimrq904HRZfx6RpPrVNd0EJ5AkUZtytY7TqcFYv@mail.gmail.com>
2011-03-12 4:58 ` RAID5 Shrinking array-size nearly killed the system Rory Jaffe
2011-03-12 5:56 ` Mikael Abrahamsson
2011-03-12 14:40 ` Phil Turmel
[not found] ` <AANLkTik2qk2ep7fsQPjAesnjur-0AB-Xx7EeZ5YfeCSA@mail.gmail.com>
2011-03-12 17:47 ` [PATCH] Add more warnings to --grow documentation (was: RAID5 Shrinking array-size nearly killed the system) Phil Turmel
[not found] ` <AANLkTikRdqZ4nAdLcUuYz17KeWb54ES_sNYzzW-u1R0x@mail.gmail.com>
2011-03-12 17:58 ` RAID5 Shrinking array-size nearly killed the system Phil Turmel
2011-03-12 18:31 ` Rory Jaffe
[not found] ` <AANLkTim+OwO5-w5Hhjdchp+Nj8k0zTLqqvRKfAzFgkWz@mail.gmail.com>
2011-03-12 20:10 ` Phil Turmel
2011-03-13 6:56 ` Rory Jaffe
2011-03-13 13:33 ` Phil Turmel [this message]
2011-03-15 5:26 ` Rory Jaffe
2011-03-15 5:44 ` NeilBrown
2011-03-15 5:53 ` Rory Jaffe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7CC7B9.3010207@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rsjaffe@gmail.com \
--cc=swmike@swm.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.