LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Patrick Ale" <patrick.ale@gmail.com>
To: "Bill Davidsen" <davidsen@tmr.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] Can't start MD devices by using /dev/disk/by-id
Date: Wed, 14 Feb 2007 08:28:25 +0100	[thread overview]
Message-ID: <8d158e1f0702132328u104c89d4r3154b87c2b5f6e5c@mail.gmail.com> (raw)
In-Reply-To: <45D259DD.7040505@tmr.com>

> >
> Just out of curiosity, why did you do this in such a manual way instead
> of just using the UUID? I would think every time you replace a failed
> drive you would have to go edit the files all over again.

Oh, there is a very simple reason for that.
These md arrays exist for a year of three allready, from the time I
used raidtool instead of mdadm.

So when I switched to to mdadm, I just got the /etc/raidtab file and
migrated it to /etc/mdadm.conf, since /etc/raidtab worked with
blockdevices and not UIDs (correct me if I am wrong and overlooked
this featute), the mdadm.conf ended up with these devices too.

Next to that, there is a, for me at least, practicle reason. I keep
adding harddisks, and when I use the block devices rather than UIDS,
and I get problems like yesterday, I have the blockdevice or serial
number of the disk, which makes it easier to look in my case where the
potential problem might be. If I work with UIDs and something goes
wrong when doing an mdadm --assemble, then I'll first have to look up
which disks belong to which UID, which costs time.

OR! which is also very possible, maybe there is a way easier way to
pinpoint which drives belong to which array before starting the array,
which I don't know about yet. So please, if you have suggestions, let
me know :)


Take care!

Patrick

      reply	other threads:[~2007-02-14  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 21:51 Patrick Ale
2007-02-14  0:37 ` Bill Davidsen
2007-02-14  7:28   ` Patrick Ale [this message]

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=8d158e1f0702132328u104c89d4r3154b87c2b5f6e5c@mail.gmail.com \
    --to=patrick.ale@gmail.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PROBLEM] Can'\''t start MD devices by using /dev/disk/by-id' \
    /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

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).