linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Scobie <richard@sauce.co.nz>
To: "Tor Arne Vestbø" <torarnv@gmail.com>
Cc: Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: Linux RAID autodetect partitions go missing from /dev, but fdisk can see them
Date: Sun, 01 Feb 2009 07:50:09 +1300	[thread overview]
Message-ID: <49849D61.5040602@sauce.co.nz> (raw)
In-Reply-To: <49844FD9.2090705@gmail.com>

Tor Arne Vestbø wrote:

> Changed the DEVICE line in my mdadm.conf from:
> 
>   DEVICE partitions
> 
> to
> 
>   DEVICE /dev/sd[bcdef]1
> 
> Now the array is assembled correctly at boot.

A safer way of acheiving this is to list the array in mdadm.conf by 
UUID, which will guarantee all the correct devices are used - sd devices 
can move around under some conditions.

eg.

ARRAY /dev/md1 level=raid1 num-devices=2 
UUID=f6bd7495:52288189:40f44282:1c220686
ARRAY /dev/md0 level=raid1 num-devices=2 
UUID=f7d720fe:a5d0724c:c9bd10fa:a496ed51

Note each ARRAY entry and UUID are entered as a single line.

Regards,

Richard
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-01-31 18:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 20:56 Linux RAID autodetect partitions go missing from /dev, but fdisk can see them Tor Arne Vestbø
2008-12-16  3:27 ` Neil Brown
2008-12-18 22:03   ` Tor Arne Vestbø
2008-12-18 22:19     ` Tor Arne Vestbø
     [not found]     ` <18762.53424.819087.495066@notabene.brown>
2009-01-18 17:51       ` Tor Arne Vestbø
2009-01-19 16:18         ` Tor Arne Vestbø
2009-01-31 13:19         ` Tor Arne Vestbø
2009-01-31 18:50           ` Richard Scobie [this message]
2008-12-18 22:22   ` Tor Arne Vestbø
  -- strict thread matches above, loose matches on Subject: below --
2008-12-11  6:41 Tor Arne Vestbø

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=49849D61.5040602@sauce.co.nz \
    --to=richard@sauce.co.nz \
    --cc=linux-raid@vger.kernel.org \
    --cc=torarnv@gmail.com \
    /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).