Can anyone explain why this is, or needs to be?

In some systems, disks are named c0t0d0 etc

In some systems, they're named like this: c0t5000C5003424396Bd0

 

Worse yet... 

In my present system, 

foo=5000C5003424396B

bar=600C0FF000000000092C4D22A708D800

when I run format, I see c0t${foo}d0

If I ls /dev/rdsk/c0t${foo}* I see all the usual suspects... p0 to p4, and
s0 to s15 ... But I don't see any "d0" without any "p" or "s"

If I ls /dev/rdsk/*d0 then I see $bar

 

Here's why I care:

I installed s11e to a partition of a 2T drive.  Now I want to mirror it, so
I want to replicate the fdisk partitions & partition slices onto the 2nd
disk... Nothing I do inside of "format" seems to make them identical, so I
considered using a low-level dd copy of the raw disk, but the device name
for the raw disk doesn't exist (nothing /dev/rdsk/*d0 matching the name of
the disk in my zpool), unless it's one of those other $bar things...  In
which case I don't know which one is which.  I have a 50/50 chance of doing
it right, or destroying the original.  That's all assuming it's even valid
to attempt doing such a thing.

 

Right now, the only technique I can think of that will work is ... I'll
ignore the partition&slice tables on the original disk, and create a new
fdisk partition & partition slice scheme on the 2nd disk as I wish.  Then
I'll zfs send the rpool onto the 2nd disk, install grub etc, and wipe out
the first disk.  Boot from the 2nd disk.  Then re-partition the first disk
the same as the 2nd disk and start mirroring.  This sounds like a pointless
hassle that must be avoidable SOME how.

 

;-)   Thanks for any answers/info/suggestions.

_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to