Re: second controller: what will my discs be called, and does it matter?

2006-07-17 Thread Bill Davidsen

Dexter Filmore wrote:

Currently I have 4 discs on a 4 channel sata controller which does its job 
quite well for 20 bucks. 
Now, if I wanted to grow the array I'd probably go for another one of these.


How can I tell if the discs on the new controller will become sd[e-h] or if 
they'll be the new a-d and push the existing ones back?
 


For software RAID you shouldn't care, for other things you might.


Next question: assembling by UUID, does that matter at all?
 


No. There's the beauty of it.

(And while talking UUID - can I safely migrate to a udev-kernel? Someone on 
this list recently ran into trouble because of such an issue.)


You shouldn't lose data unless you panic at the first learning 
experience and do something without thinking of the results. I would 
convert to UUID first, obviously.


--
bill davidsen [EMAIL PROTECTED]
 CTO TMR Associates, Inc
 Doing interesting things with small computers since 1979

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


Re: second controller: what will my discs be called, and does it matter?

2006-07-17 Thread Dexter Filmore
Am Montag, 17. Juli 2006 20:28 schrieb Bill Davidsen:
 Next question: assembling by UUID, does that matter at all?

 No. There's the beauty of it.

That's what I needed to hear.


 (And while talking UUID - can I safely migrate to a udev-kernel? Someone
  on this list recently ran into trouble because of such an issue.)

 You shouldn't lose data unless you panic at the first learning
 experience and do something without thinking of the results. I would
 convert to UUID first, obviously.

Already happened. Biggest problem so far is coming up with a sane backup 
solution for 500gigs of data :P

-- 
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GCS d--(+)@ s-:+ a- C UL++ P+++ L+++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@ 
b++(+++) DI+++ D- G++ e* h++ r* y?
--END GEEK CODE BLOCK--

http://www.stop1984.com
http://www.againsttcpa.com
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: second controller: what will my discs be called, and does it matter?

2006-07-07 Thread Gabor Gombas
On Thu, Jul 06, 2006 at 08:12:14PM +0200, Dexter Filmore wrote:

 How can I tell if the discs on the new controller will become sd[e-h] or if 
 they'll be the new a-d and push the existing ones back?

If they are the same type (or more precisely, if they use the same
driver), then their order on the PCI bus will decide. Otherwise, if you
are using modules, then the order you load the drivers will decide. If
the drivers are built into the kernel, then their link order will
decide.

Gabor

-- 
 -
 MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
 -
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: second controller: what will my discs be called, and does it matter?

2006-07-06 Thread John Stoffel

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
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: second controller: what will my discs be called, and does it matter?

2006-07-06 Thread Neil Brown
On Thursday July 6, [EMAIL PROTECTED] wrote:
 Currently I have 4 discs on a 4 channel sata controller which does its job 
 quite well for 20 bucks. 
 Now, if I wanted to grow the array I'd probably go for another one of these.
 
 How can I tell if the discs on the new controller will become sd[e-h] or if 
 they'll be the new a-d and push the existing ones back?

No idea.  Probably depends on where you plug it in, but also on the
phase of the moon :-)

 
 Next question: assembling by UUID, does that matter at all?

No.

 (And while talking UUID - can I safely migrate to a udev-kernel? Someone on 
 this list recently ran into trouble because of such an issue.)

Depends on what you mean by 'safely'.

If you mean can I change something that fundamental and expect
everything will just work perfectly without me having to think , then
no. 

If you mean should it be fairly easy to fix anything that breaks, and
can I be confident that my data will be safe even if something does
break, then yes.

NeilBrown
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html