From: "John Stoffel" <john@stoffel.org>
To: Dexter Filmore <Dexter.Filmore@gmx.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: second controller: what will my discs be called, and does it matter?
Date: Thu, 6 Jul 2006 18:05:17 -0400 [thread overview]
Message-ID: <17581.35101.128252.9505@stoffel.org> (raw)
In-Reply-To: <200607062012.14684.Dexter.Filmore@gmx.de>
Dexter> Currently I have 4 discs on a 4 channel sata controller which
Dexter> does its job quite well for 20 bucks. Now, if I wanted to
Dexter> grow the array I'd probably go for another one of these.
So, which SATA controller are you using? I'm thinking my next box
will go SATA, but I'm still deciding....
Dexter> How can I tell if the discs on the new controller will become
Dexter> sd[e-h] or if they'll be the new a-d and push the existing
Dexter> ones back?
Dexter> Next question: assembling by UUID, does that matter at all?
Dexter> (And while talking UUID - can I safely migrate to a
Dexter> udev-kernel? Someone on this list recently ran into trouble
Dexter> because of such an issue.)
I'm using udev and it's not a problem, but I admit I'm also
auto-assembling my arrays using the kernel detection stuff. All I
have in my mdadm.conf file is
MAILADDR john
PARTITIONS
and it just works for me. But using the UUID is the way to go.
Though I admit my system may not be setup like you think. I have a
pair of 120gb drives which are mirrored. On top of them I have LVM
configured and a pair of partitions setup, so I can grow/move/shrink
them at some point. Hasn't happened too often yet.
So I'm not using ext3 -> MD -> disks, I'm adding in the LVM layer.
John
next prev parent reply other threads:[~2006-07-06 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 18:12 second controller: what will my discs be called, and does it matter? Dexter Filmore
2006-07-06 22:05 ` John Stoffel [this message]
2006-07-06 22:20 ` Neil Brown
2006-07-07 13:15 ` Gabor Gombas
2006-07-17 18:28 ` Bill Davidsen
2006-07-17 21:45 ` Dexter Filmore
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=17581.35101.128252.9505@stoffel.org \
--to=john@stoffel.org \
--cc=Dexter.Filmore@gmx.de \
--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;
as well as URLs for NNTP newsgroup(s).