From: Jeff Wiegley <jeffw@csun.edu>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Why would a recreation cause a different number of blocks??
Date: Fri, 25 Apr 2014 00:05:26 -0700 [thread overview]
Message-ID: <535A0936.9060207@csun.edu> (raw)
In-Reply-To: <alpine.DEB.2.02.1404250800190.19744@uplift.swm.pp.se>
Here's something about my closer call...
In the original the mdstat lists:
md3 : active raid6 sda1[0] sdc1[2] sde1[4] sdb1[1] sdd1[6]
1073735680 blocks super 1.2 level 6, 512k chunk, algorithm 2
[6/5] [UUUUU_]
What do the numbers after the drives mean? It appears to match
the number in the Device Role in an examine.
When I recreated the array with 3.1.4 I used:
/mdadm --create --assume-clean --level=6 --raid-devices=6 /dev/md0
/dev/sdd1 /dev/sdb1 /dev/sde1 /dev/sdc1 /dev/sda1 missing
now mdadm (which luks is happy with) reports:
Personalities : [raid6] [raid5] [raid4]
md0 : active raid6 sdd1[0] sda1[4] sdc1[3] sde1[2] sdb1[1]
1073735680 blocks super 1.2 level 6, 512k chunk, algorithm 2
[6/5] [UUUUU_]
which are not the same numbers. Now I figure I can reorder my
command line arguments but (due to prior drive failures) I think
the mapping (from the original) should be:
0: /dev/sda1
1: /dev/sdb1
2: /dev/sdc1
3: ????
4: /dev/sde1
5: ?????
6: /dev/sdd1
7: /dev/sdf1 (this is my current dead drive that I have to leave out
and bring the array degraded because this drive is
probably very out of sync)
Though I know to substitute "missing" for /dev/sdf1 to leave it
out, my question is: What do I do about the active devices 3 and 5
on the command line? Also put missing for those?? I don't think
that will work because wouldn't it think I have 3 drives dead and
refuse to start the array?
But it does seem like I'm getting closer... and if I can get
this partition up then I have high probability of recovering
the larger important array that is in /dev/sd[a-o]2
Thanks again,
- Jeff
On 4/24/2014 11:01 PM, Mikael Abrahamsson wrote:
> On Thu, 24 Apr 2014, Jeff Wiegley wrote:
>
>> If it's mdadm then could I just grab old copies of mdadm sources and
>> compile them one version after the other and try each one?
>
> As far as I know, it's mdadm version specific. If you look in the archives
> I'm sure you'll be able to find the old offsets and you can use the latest
> mdadm with those offsets and hopefully things will work.
>
next prev parent reply other threads:[~2014-04-25 7:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 5:05 Corrupted ext4 filesystem after mdadm manipulation error L.M.J
2014-04-24 17:48 ` L.M.J
[not found] ` <CAK_KU4a+Ep7=F=NSbb-hqN6Rvayx4QPWm-M2403OHn5-LVaNZw@mail.gmail.com>
2014-04-24 18:35 ` L.M.J
[not found] ` <CAK_KU4Zh-azXEEzW4f1m=boCZDKevqaSHxW0XoAgRdrCbm2PkA@mail.gmail.com>
2014-04-24 19:53 ` L.M.J
[not found] ` <CAK_KU4aDDaUSGgcGBwCeO+yE0Qa_pUmMdAHMu7pqO7dqEEC71g@mail.gmail.com>
2014-04-24 19:56 ` L.M.J
2014-04-24 20:31 ` Scott D'Vileskis
2014-04-24 22:25 ` Why would a recreation cause a different number of blocks?? Jeff Wiegley
2014-04-25 3:34 ` Mikael Abrahamsson
2014-04-25 5:02 ` Jeff Wiegley
2014-04-25 6:01 ` Mikael Abrahamsson
2014-04-25 6:45 ` Jeff Wiegley
2014-04-25 7:25 ` Mikael Abrahamsson
2014-04-25 7:05 ` Jeff Wiegley [this message]
[not found] ` <CAK_KU4YUejncX9yQk4HM5HE=1-qPPxOibuRauFheo3jaBc8SaQ@mail.gmail.com>
2014-04-25 5:13 ` Corrupted ext4 filesystem after mdadm manipulation error L.M.J
2014-04-25 6:04 ` Mikael Abrahamsson
2014-04-25 11:43 ` L. M. J
2014-04-25 13:36 ` Scott D'Vileskis
2014-04-25 14:43 ` L.M.J
2014-04-25 18:37 ` Is disk order relative or are the numbers absolute? Jeff Wiegley
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=535A0936.9060207@csun.edu \
--to=jeffw@csun.edu \
--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).