Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: Re: sub-array kicked out of raid6 on each reboot.
Date: Fri, 28 Jan 2011 21:28:55 +0100	[thread overview]
Message-ID: <20110128212855.64339d06@atak.bl.pg.gda.pl> (raw)
In-Reply-To: <20110129012156.00a935ec@natsu>

Roman Mamedov said:     (by the date of Sat, 29 Jan 2011 01:21:56 +0500)

> On Fri, 28 Jan 2011 21:15:34 +0100
> Janek Kozicki <janek_listy@wp.pl> wrote:
> 
> > Is it possible that the order in which the arrays were created,
> > matters? Because when it worked I created the sub-array first, and
> > then I created the BIG array. And currently the sub-array is created
> > after the BIG one.
> 
> I believe the order in which they are listed in mdadm.conf matters here.
> And after changing that file, you may need to rebuild your initramfs
> (on current Debian, "update-initramfs -k all -u").

Hi,

backup:~# cat /etc/mdadm/mdadm.conf | grep -v "#"

DEVICE partitions
CREATE owner=root group=disk mode=0660 auto=yes
HOMEHOST <system>
MAILADDR root
ARRAY /dev/md/2  metadata=1.0 UUID=4fd340a6:c4db01d6:f71e03da:2dbdd574 name=backup:2
ARRAY /dev/md/6  metadata=1.1 UUID=78f253ba:5a19ff8a:6646aa2f:f5218d84 name=backup:6
ARRAY /dev/md/0  metadata=1.0 UUID=75b0f878:79539d6c:eef22092:f47a6e6f name=backup:0
ARRAY /dev/md/69 metadata=1.1 UUID=dd751cb0:63424a86:66b98082:4bd80dcb name=backup:69

The order, I think is correct, but I did not rebuild initramfs.
I will try that and let you know, thanks.

-- 
Janek Kozicki                               http://janek.kozicki.pl/  |

  reply	other threads:[~2011-01-28 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28 20:15 sub-array kicked out of raid6 on each reboot Janek Kozicki
2011-01-28 20:21 ` Roman Mamedov
2011-01-28 20:28   ` Janek Kozicki [this message]
2011-01-28 20:44   ` Janek Kozicki

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=20110128212855.64339d06@atak.bl.pg.gda.pl \
    --to=janek_listy@wp.pl \
    --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