linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Piotr Klimek <piotr@klimek.net.pl>, linux-raid@vger.kernel.org
Subject: Re: RAID6 reshape integer problem
Date: Fri, 03 Jan 2014 12:07:21 -0500	[thread overview]
Message-ID: <52C6EE49.2000907@turmel.org> (raw)
In-Reply-To: <CAM8eUy0=YbC68vesaLPSp0RhL_2c8byVyROMGv2DdQ2_JSjYrg@mail.gmail.com>

On 01/03/2014 08:34 AM, Piotr Klimek wrote:
> 2014/1/3 Phil Turmel <philip@turmel.org>
> 
>>
>>> After couple of days reshape stalled on 2147483648 block. I have found
>> that
>>> this is a bug in mdadm. 2147483648 is max integer on 32 bit system. For
>> now
>>> situation looks like this:
>>
>> You'll certainly have to take production down long enough to let a newer
>> kernel finish the reshape.  Or you could be brave and replace the kernel
>> and let production continue through the balance of the reshape.
>>
> 
> Is it safe to reboot during reshape and boot up with new kernel? I can
> easly upgrade kernel to 3.2.0.
> 

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

  parent reply	other threads:[~2014-01-03 17:07 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 [this message]
2014-01-08 11:19       ` Piotr Klimek
2014-01-08 16:32         ` joystick

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=52C6EE49.2000907@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).