Answering myself because I've gotten things to work, but it's a mystery as
to why they're working (I have a Sun case number if anyone at Sun.com is
interested).
Steps:
1. Try to create a pool on a pseudo-device:
# zpool create mypool emcpower0a
This receives an I/O error (see previous message).
2. Create a pool on the LUN using the traditional device name:
# zpool create mypool c1tFOO...
3. Destroy the pool:
# zpool destroy mypool
4. Go back to the EMC PowerPath pseudo-device and create the pool:
# zpool create mypool emcpower0a
This now works.
The only difference I can see is that before the emcpower0a device had
slices that were numbered 0-7 according to format(1M). Now it has slices
0-6, and a slice numbered 8 that is "reserved":
AVAILABLE DISK SELECTIONS:
0. c0t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED]/[EMAIL PROTECTED],0
1. c0t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED]/[EMAIL PROTECTED],0
2. c1t5006016030602568d0 <DGC-RAID 5-0219-100.00GB>
/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],0
3. c1t5006016830602568d0 <DGC-RAID 5-0219-100.00GB>
/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL
PROTECTED],0
4. emcpower0a <DGC-RAID 5-0219-100.00GB>
/pseudo/[EMAIL PROTECTED]
Specify disk (enter its number): 4
selecting emcpower0a
[disk formatted]
FORMAT MENU:
[...]
format> p
PARTITION MENU:
[...]
partition> p
Current partition table (original):
Total disk sectors available: 209698782 + 16384 (reserved sectors)
Part Tag Flag First Sector Size Last Sector
0 usr wm 34 99.99GB 209698782
1 unassigned wm 0 0 0
2 unassigned wm 0 0 0
3 unassigned wm 0 0 0
4 unassigned wm 0 0 0
5 unassigned wm 0 0 0
6 unassigned wm 0 0 0
8 reserved wm 209698783 8.00MB 209715166
Also, if I select disks 2 or 3 in the format(1M) menu I get a warning that
the device is part of a ZFS pool and that I should see zpool(1M).
>From the "ZFS Administrators Guide", partition 8 seems to indicate that an
EFI label is now being used on the LUN. Furthermore the Admin Guide says:
> To use whole disks, the disks must be named using the standard Solaris
> convention, such as /dev/dsk/cXtXdXsX. Some third-party drivers use a
> different naming convention or place disks in a location other than the
> /dev/dsk directory. To use these disks, you must manually label the disk
> and provide a slice to ZFS.
I'm not manually labeling the disk, but things are now working on the
pseudo-device.
Is this expected behaviour? Is there a reason why ZFS cannot access the
pseudo-device in a "raw" manner, even though /dev/dsk/emcpower0a exists
(see truss(1) output in previous message)?
The Sun support guys deal more in the break-fix aspect of this, and not as
much as the "why?" part, but I asked them to follow up internally if they
can. I figured I'd post publicly in case a greater audience may find some
of this useful (and it'll be in the archives for anyone doing future
searches).
Thanks for any info.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
