All of lore.kernel.org
 help / color / mirror / Atom feed
From: joystick <joystick@shiftmail.org>
To: Piotr Klimek <piotr@klimek.net.pl>
Cc: Phil Turmel <philip@turmel.org>, linux-raid@vger.kernel.org
Subject: Re: RAID6 reshape integer problem
Date: Wed, 08 Jan 2014 17:32:36 +0100	[thread overview]
Message-ID: <52CD7DA4.4080608@shiftmail.org> (raw)
In-Reply-To: <CAM8eUy180ShDn74JDqqrK8n7tLHqd_VgAaN+3UdqqU50mA+akA@mail.gmail.com>

Had I seen this thread earlier... I would probably have responded that 
no, AFAIR it is not safe to reboot while reshaping (!)

In fact i seem to recall that there was a very serious known problem 
during pivot_root , which is at the end of initramfs. A reshape in 
progress through that point would cause data loss. So the array could 
only be assembled after that point, so you had to modify initrd or use a 
livecd so to be sure that it wouldn't find/assemble the array at the 
early stages of boot. This is what I seem to remember.

However by looking for details on such problem everywhere, I am not 
anymore able to find any reference.
Does anybody recall this problem?

Thanks
J.


On 08/01/2014 12:19, Piotr Klimek wrote:
> Hi,
> Everything works fine right now, all I have to do after reboot was
> assemble array using backup file and set MDADM_GROW_ALLOW_OLD=1
> enviroment variable.
>
> Thanks for your help.
>
> 2014/1/3 Phil Turmel <philip@turmel.org>:
>> It is supposed to be safe. With a clean shutdown, the superblock will
>> have a record of the reshape progress and will be able to continue after
>> re-assembly.
>>
>> But you'll probably have to assembly manually to specify the location of
>> the critical section backup file.  If your root FS is in this array,
>> you'll have to intervene in the initramfs.
>>
>> HTH,
>>
>> Phil
>
>


      reply	other threads:[~2014-01-08 16:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  9:30 RAID6 reshape integer problem Piotr Klimek
2014-01-03 12:56 ` Phil Turmel
2014-01-03 13:43   ` Piotr Klimek
     [not found]   ` <CAM8eUy0=YbC68vesaLPSp0RhL_2c8byVyROMGv2DdQ2_JSjYrg@mail.gmail.com>
2014-01-03 17:07     ` Phil Turmel
2014-01-08 11:19       ` Piotr Klimek
2014-01-08 16:32         ` joystick [this message]

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=52CD7DA4.4080608@shiftmail.org \
    --to=joystick@shiftmail.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    --cc=piotr@klimek.net.pl \
    /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.