From: Matthias Urlichs <matthias@urlichs.de>
To: "Majed B." <majedb@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID1 assembled broken array
Date: Tue, 15 Sep 2009 19:33:19 +0000 [thread overview]
Message-ID: <1253043199.7774.179.camel@kiste> (raw)
In-Reply-To: <70ed7c3e0909151224s75cd6c60kc65c2f4e9076e649@mail.gmail.com>
On Tue, 2009-09-15 at 22:24 +0300, Majed B. wrote:
> Specifying partition names may cause problems if the disk names
> changed. Specify the UUID instead.
>
What I was trying to say is "use a pattern that matches all of your
partitions and none of your actual disks". That should be safe from
changing disk file names.
Besides, specifying UUIDs does not work because it runs into the exact
problem we're trying to solve in the first place. Behold the "blkid"
output from the server in question:
/dev/sdb2: UUID="1583e643-7004-a86e-4eff-81c58ea53278" TYPE="mdraid"
/dev/sdb: UUID="1583e643-7004-a86e-4eff-81c58ea53278" TYPE="mdraid"
Interestingly, for some reason it doesn't do that with /dev/sda -- most
probably because the disks in question use different head/sector values
and thus have slightly different partition layout.
next prev parent reply other threads:[~2009-09-15 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 19:22 RAID1 assembled broken array Matthias Urlichs
2009-09-15 19:24 ` Majed B.
2009-09-15 19:33 ` Matthias Urlichs [this message]
2009-09-15 19:43 ` Majed B.
2009-09-15 20:04 ` Doug Ledford
2009-09-15 20:00 ` Doug Ledford
2009-09-15 20:27 ` Matthias Urlichs
2009-09-15 21:01 ` NeilBrown
2009-09-16 4:50 ` Matthias Urlichs
2009-09-17 16:44 ` Doug Ledford
2009-09-17 17:09 ` Matthias Urlichs
2009-09-17 17:12 ` Majed B.
2009-09-25 8:07 ` Neil Brown
2009-09-17 8:25 ` Andre Noll
2009-09-25 8:12 ` Neil Brown
2009-09-25 10:42 ` Chris Webb
2009-09-26 9:58 ` Andre Noll
2009-09-26 13:01 ` John Robinson
2009-09-26 19:21 ` Clinton Lee Taylor
2009-09-28 16:12 ` Andre Noll
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=1253043199.7774.179.camel@kiste \
--to=matthias@urlichs.de \
--cc=linux-raid@vger.kernel.org \
--cc=majedb@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).