> From: Cindy Swearingen [mailto:cindy.swearin...@oracle.com] > Sent: Monday, July 25, 2011 10:59 AM > > The p* devices represent the fdisk partition. > > The disk naming is very confusing so let's summarize: > > c*t*d*p* - represents the larger fdisk partition. Do no use these > for your storage pools. > > c*t*d* - represents the whole disk. Use these for your pools > except when creating a root pool for booting. Do not use s2, a > slice that represented the whole disk on the VTOC label for > anything. > > c*t*d*s* - represents a disk slice. Only use this for a > root pool.
Thank you - But I already knew all that. Here's what's weird, and where the confusion is coming from: First, fdisk only supports 4 partitions. So the existence of p0, p1, p2, p3, p4 is weird. Cuz that's five. Second, there is no d0 device. There is only p0-p4, and s0-s15 Third, the goal is to replicate the fdisk partitions from one disk to another. I therefore expected I would need something broader than the p0-p4 devices... I thought I would need d0. But then somebody here told me to simply use p0 in place of d0, and it worked. Which was rather mind blowing. I thought p0 might be synonymous with d0, but on some device where p0 and d0 both exist, I checked... They're not the same. If you simply reference the d0 in zpool create... Then it will create the d0 device. By looking at the major,minor numbers, it seems to be synonymous with another random thing, like s5 or something... But not p0, not s2, and not s0. So the logic of all of this evades me... _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org