On Fri, Jul 22, 2011 at 1:15 AM, Edward Ned Harvey
<opensolarisisdeadlongliveopensola...@nedharvey.com> wrote:
> 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
That's multipathing, usually by the name of MPXIO (or sometimes the
old unbundled STMS - which is where the name of the stmsboot command
comes from).
The c0t0d0 names tend to refer to physical locations; the longer ones
use the WWN or serial number of the device. Do an ls -l on the long
one and it'll probably point to a device node with scsi_vhci in the name.
Try:
mpathadm show LU /dev/rdsk/c0t5000C5003424396Bd0s2
and you'll get more information.
Note for the future: many current systems come with multipathing on
from the start. For example, the X4170 and T3 systems I'm currently
building come up with c0t5000C500397689DBd0 style names by default.
Mapping those back to physical slots is fun. Doesn't really matter on the
T3 which, being sparc, can boot sanely off any device. A bit more work
on the X4170 matching up the boot order in the BIOS with the devices
you can see from Solaris. (Hint: install the Hardware Management Pack
and then you can get everything from the Storage tab in the ilom web
interface.) That's just an aside, though.
> 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
That often happens. It shouldn't matter. If the d0 node doesn't exist, then
telling zfs to use it as a vdev will usually force it to be created.
However, if this is a root pool then you should be using slices rather
than the whole disk anyway. (And SMI labels rather than EFI labels
if I remember correctly.)
> 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,
format, or fdisk? You need to get the fdisk identical first. And if they're
different drives, then good luck...
> 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.
The device names should match up the world wide number on the
drive. Or serial. Whatever, everything $foo refers to one drive, everything
$bar to the other one.
As I said, if this is an rpool then don't use d0 anyway. Which may well be
why d0 doesn't exist. If it's not, then give zfs the d0 name and it should
create it.
> 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
>
--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
