On Wed, Apr 09, 2008 at 05:09:05PM -0400, Damon L. Chesser wrote: > SNIP >> >> I am on amd64 lenny (with some sid), 2.6.24 >> I don't normally use UUID's i have been using labels >> >> mdadm --detail /dev/md1 | grep UUID >> UUID : ba8c4627:6e74a6c4:1a2e6c15:22feafcf >> tune2fs -l /dev/md1 | grep UUID >> Filesystem UUID: ec3e3537-4e36-443e-8132-5b0f03dd0978 >> >> As you can see the UUID ids are different between md1, I don't have a >> /dev/disk/by-uuid (i remember having it before) >> >> here is the output of blkid (which i believe is used to make up the links >> in /dev/disk/by-uuid) >> blkid | grep md1 >> /dev/md1: LABEL="/" UUID="ec3e3537-4e36-443e-8132-5b0f03dd0978" >> SEC_TYPE="ext2" TYPE="ext3" >> >> so if i wanted to mount my / partition (/dev/md0 is /boot), then I could >> put >> UUID=ec3e3537-4e36-443e-8132-5b0f03dd0978 / auto ...... in my fstab file >> >> Alex >> >> > Alex, > > I think you have it, though I can't explain the different UUIDs from > tune2fs and mdadm --detail. I would rather put in the fs type rather well tune2fs is looking at the fs which is ontop of the raid1
I also have a md2 which is a lvm pv, I can do a mdadm --detail on it and
get a uuid, but the filesystems on there are managed by lvm.
I would guess why it loads when you use the UUID of the raid1, is
because it would be the same as specifying /dev/sda1 (a partition)
alex
> then auto, but that is a matter of style. What is the result?
>
> [EMAIL PROTECTED]
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a
> subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
>
--
"Oftentimes, we live in a processed world -- you know, people focus on the
process and not results."
- George W. Bush
05/29/2003
Washington, DC
signature.asc
Description: Digital signature
