Eric,
Here is what the customer gets trying to create the pool using the
software alias: (I added all the ldi_open's to the script)
# zpool create -f extdisk vpath1c
# ./dtrace.script
dtrace: script './dtrace.script' matched 6 probes
CPU ID FUNCTION:NAME
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 15801 ldi_open_by_dev:return 0
0 7233 ldi_open_by_vp:return 0
0 17817 ldi_open_by_name:return 0
0 16191 ldi_get_size:return -1
0 44942 vdev_disk_open:return 22
Thanks,
David
Eric Schrock wrote On 07/26/06 10:03 AM,:
> This suggests that there is some kind of bug in the layered storage
> software. ZFS doesn't do anything special to the underlying storage
> device; it merely relies on a few ldi_*() routines. I would try running
> the following dtrace script:
>
> #!/usr/sbin/dtrace -s
>
> vdev_disk_open:return,
> ldi_open_by_name:return,
> ldi_open_by_path:return,
> ldi_get_size:return
> {
> trace(arg1);
> }
>
> And then re-run your 'zpool create' command. That will at at least get
> us pointed in the right direction.
>
> - Eric
>
> On Wed, Jul 26, 2006 at 09:47:03AM -0600, David Curtis wrote:
>
>>Please reply to [EMAIL PROTECTED]
>>
>>******** Background / configuration **************
>>
>>zpool will not create a storage pool on fibre channel storage. I'm
>>attached to an IBM SVC using the IBMsdd driver. I have no problem using
>>SVM metadevices and UFS on these devices.
>>
>> List steps to reproduce the problem(if applicable):
>>Build Solaris 10 Update 2 server
>>Attach to an external storage array via IBM SVC
>>Load lpfc driver (6.02h)
>>Load IBMsdd software (1.6.1.0-2)
>>Attempt to use zpool create to make a storage pool:
>># zpool create -f extdisk vpath1c
>>internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c
>>
>>********* reply to customer ********************
>>
>>It looks like you have an additional unwanted software layer between
>>Solaris and the disk hardware. Currently ZFS needs to access the
>>physical device to work correctly. Something like:
>>
>># zpool create -f extdisk c5t0d0 c5t1d0 ......
>>
>>Let me know if this works for you.
>>
>>************* follow-up question from customer ************
>>
>>Yes, using the c#t#d# disks work, but anyone using fibre-channel storage
>>on somethink like IBM Shark or EMC Clariion will want multiple paths to
>>disk using either IBMsdd, EMCpower or Solaris native MPIO. Does ZFS
>>work with any of these fibre channel multipathing drivers?
>>
>>
>>Thanks for any assistance you can provide.
>>--
>>
>>David Curtis - TSE Sun Microsystems
>>303-272-6628 Enterprise Services
>>[EMAIL PROTECTED] OS / Installation Support
>>Monday to Friday 9:00 AM to 6:00 PM Mountain
>>
>>_______________________________________________
>>zfs-discuss mailing list
>>[email protected]
>>http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
>
>
> --
> Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
--
David Curtis - TSE Sun Microsystems
303-272-6628 Enterprise Services
[EMAIL PROTECTED] OS / Installation Support
Monday to Friday 9:00 AM to 6:00 PM Mountain
_______________________________________________
zfs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
