All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tomáš Dulík" <dulik@unart.cz>
To: st0ff@npl.de
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid10,f2 Add a Controller: Which drives to move?
Date: Mon, 12 Apr 2010 09:43:16 +0200	[thread overview]
Message-ID: <4BC2CF14.9000209@unart.cz> (raw)
In-Reply-To: <4BC2B887.6020403@stud.tu-ilmenau.de>

Stefan /*St0fF*/ Hübner napsal(a):
> I cannot quite understand your problem.  As every part of the array
> contains it's own metadata, it doesn't matter to md which /dev/sdX a
> drive is.  It might matter a bit for boot-time assembly, but actually
> that's what UUIDs are for.
>   
I know how UUIDs work.
My problem with device names is not a "critical", it's about "user 
friendliness" of the physical disk management.
If a disk fails and I receive email "A Fail event had been detected on 
md device /dev/md2. It could be related to component device /dev/sdd3", 
how will I know which disk should be replaced, if the device name is not 
fixed/persistent? Is it the disk in the first bay, or the second? Aside 
of the solution documented on the wiki page, I could also use try a 
simpler one based on the idea here:
http://www.outsidaz.org/blog/2009/11/05/identifying-failed-drives-via-udev-and-mdadm/

But for the disk management purposes, I prefer having the disk names 
fixed according the the disk bay position. So disk in bay nr. 1 is 
/dev/sda, bay nr. 2 is /dev/sdb, etc.

The wiki page I created is just about this. I haven't found any document 
like this anywhere else, so if it helps someone, I'll be glad.

Tom
--
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:[~2010-04-12  7:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 17:08 raid10,f2 Add a Controller: Which drives to move? Michael McCallister
2010-04-11 21:31 ` Michael Evans
2010-04-12  6:17   ` Michael McCallister
2010-04-12  3:41 ` Tomáš Dulík
2010-04-12  6:07   ` Stefan /*St0fF*/ Hübner
2010-04-12  7:43     ` Tomáš Dulík [this message]
2010-04-13  3:26       ` Simon Matthews
2010-04-13  9:23         ` Keld Simonsen
2010-04-13 13:09           ` Neil Brown
2010-04-12  6:07   ` Michael McCallister

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=4BC2CF14.9000209@unart.cz \
    --to=dulik@unart.cz \
    --cc=linux-raid@vger.kernel.org \
    --cc=st0ff@npl.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.