From: Robin Hill <robin@robinhill.me.uk>
To: Adam Ryczkowski <adam.ryczkowski@statystyka.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
Date: Tue, 18 Sep 2012 08:52:13 +0100 [thread overview]
Message-ID: <20120918075213.GA15342@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <50581A65.5050201@statystyka.net>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
On Tue Sep 18, 2012 at 08:53:25AM +0200, Adam Ryczkowski wrote:
> On 2012-09-17 19:49, Robin Hill wrote:
>
> > Your data offset is 272 sectors, which means you'll need to use an older
> > mdadm version to re-create the array. Newer versions use 2048 sectors,
> > but it looks like version 3.0 uses 272, so grab a copy of that if
> > possible.
> Does it mean, that with the current raid setup I need to stick to the
> mdadm 3.0, or is there way to convert the arrays to the new layout so I
> can use a recent mdadm? Re-creating the arrays from scratch would be a
> very long and complex enterprise.
>
You only need 3.0 to do the create. Once that's done, you can use any
newer version.
The only way I know of to update the offset location in an existing
array would be to fail the disks one at a time, zeroing the superblocks,
then adding them back into the array using a new mdadm. When it's added
back in, it'll use the new offset location. If you have a spare disk and
a new enough kernel version, you can use the pre-emptive replacement
option, which will prevent the need to run without full parity
available.
Cheers,
Robin
--
___
( ' } | Robin Hill <robin@robinhill.me.uk> |
/ / ) | Little Jim says .... |
// !! | "He fallen in de water !!" |
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-09-18 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 7:00 What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage? Adam Ryczkowski
2012-09-17 17:49 ` Robin Hill
2012-09-18 6:53 ` Adam Ryczkowski
2012-09-18 7:52 ` Robin Hill [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=20120918075213.GA15342@cthulhu.home.robinhill.me.uk \
--to=robin@robinhill.me.uk \
--cc=adam.ryczkowski@statystyka.net \
--cc=linux-raid@vger.kernel.org \
/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).