From: "Andris Berzins" <pkix@inbox.lv>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: linux-raid@vger.kernel.org
Subject: Re: failed raid re-create changed dev size
Date: Tue, 11 Dec 2012 11:01:35 +0200 [thread overview]
Message-ID: <1355216495.50c6f66f123b1@mail.inbox.lv> (raw)
In-Reply-To: <alpine.DEB.2.00.1212110912470.17599@uplift.swm.pp.se>
Quoting "Mikael Abrahamsson" <swmike@swm.pp.se>:
> On Tue, 11 Dec 2012, Andris Berzins wrote:
>
>> I found on internet that this can be fixed if I re-create raid with the same
>> configuration, but with dead drive set as 'missing'.
>
> This is extremely dangerous. You would have been better off by first
> trying --assemble --force.
>
>> However, I can not mount md1 and looks like it contains random data. The
>> order is correct. However, I noticed that new raid device size is
>> different from old one.
>
> Your data offset is different, most likely you're not using the same mdadm
> version as was initially used to create the raid. Mdadm defaults have
> changed over time regarding chink size, data offset and others.
Thank you!
I did not notice that.
Looks that I will have to try downgrade kernel:
http://serverfault.com/questions/427683/what-parameters-to-mdadm-to-re-create-md-device-with-payload-starting-at-
0x2200
>
> I don't know off the top of my head how to change the mdadm data offset
> unfortunately.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2012-12-11 9:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 23:37 failed raid re-create changed dev size Andris Berzins
2012-12-11 8:15 ` Mikael Abrahamsson
2012-12-11 9:01 ` Andris Berzins [this message]
2012-12-11 9:27 ` Robin Hill
2012-12-11 14:35 ` Andris Berzins
2012-12-11 14:49 ` Robin Hill
2012-12-12 16:10 ` Andris Berzins
2012-12-13 9:30 ` Robin Hill
2012-12-13 16:13 ` Andris Berzins
2012-12-12 1:04 ` Brad Campbell
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=1355216495.50c6f66f123b1@mail.inbox.lv \
--to=pkix@inbox.lv \
--cc=linux-raid@vger.kernel.org \
--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 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).