Re: 3dmd and kernel 2.4.17
> You create your file systems with a label, for example
> mke2fs -L data1 /dev/sdb1
> You can then mount /dev/sdb1 by using mount -L data1
> or LABEL=data1 in /etc/fstab.
Okay, I see what you are saying. We already put labels on our filesystems
(not for mounting, but for clarity so we know what each partition is
But what would happen if (for example) sda1, sdb5, and sdc3 all have the
If you do "mount -L boot", which would it load?
> Of course, this works only for filesystems, not raw
It would not be very useful if it referred to raw devices anyway.
> I am using this on our 160 file servers equipped with
> a total of 390 3ware boards and more than 2000 disks.
So you probably already have a proven way to get around the problem...
Or else you'd have a HUGE headache any time an array goes funny ;-)
> -----Original Message-----
> From: Jason Lim [mailto:email@example.com]
> Sent: Thursday, February 14, 2002 10:27 PM
> To: fabien; Peter L. Ashford
> Cc: Timothy Demarest; firstname.lastname@example.org
> Subject: Re: 3dmd and kernel 2.4.17
> > To overcome this "problem" you can mount your file
> > systems using labels instead of physical disks/volumes (aka /dev/sdX)
> > See mke2fs -L option, and mount -L option.
> Great advice... but is it really that useful?
> in man mount:
> -L label
> Mount the partition that has the specified label.
> in man mke2fs
> -L Set the volume label for the filesystem.
> That would suggest that if we gave it "/dev/sda" and told it to mount a
> partition called "boot", then it would load, for example, /dev/sda2.
> But that doesn't really solve the problem that /dev/sda may NOT be the
> actual disk/array you want loaded. We're not talking about the
> partitions... because that is one thing we can get right. Its the
> is sda becoming sdb if whatever is on port0 (the preceding port) fails
> becomes independent.
> the 3ware bios does not seem to have the intelligence or ability to set
> the "array order", so that a arrays will ALWAYS load up in a particular
> order, regardless of whatever changes are made, or what ports the
> are on ,etc.
> Does this make sense? Or is there already a way to do this?