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
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,
zfs should work fine with disks under the control of solaris mpxio.
i don't know about any of the other multipathing solutions.
if you're trying to use a device that's controlled by another
multipathing solution, you might want to try specifying the full
path to the device, ex:
zpool
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 IDFUNCTION:NAME
0 7233
So it does look like something's messed up here. Before we pin this
down as a driver bug, we should double check that we are indeed opening
what we think we're opening, and try to track down why ldi_get_size is
failing. Try this:
#!/usr/sbin/dtrace -s
ldi_open_by_name:entry
{
Eric,
Here is the output:
# ./dtrace2.dtr
dtrace: script './dtrace2.dtr' matched 4 probes
CPU IDFUNCTION:NAME
0 17816 ldi_open_by_name:entry /dev/dsk/vpath1c
0 16197 ldi_get_otyp:return 0
0 15546
On Wed, Jul 26, 2006 at 02:11:44PM -0600, David Curtis wrote:
Eric,
Here is the output:
# ./dtrace2.dtr
dtrace: script './dtrace2.dtr' matched 4 probes
CPU IDFUNCTION:NAME
0 17816 ldi_open_by_name:entry /dev/dsk/vpath1c
0 16197
Does format show these drives to be available and containing a non-zero
size?
Eric Schrock wrote:
On Wed, Jul 26, 2006 at 02:11:44PM -0600, David Curtis wrote:
Eric,
Here is the output:
# ./dtrace2.dtr
dtrace: script './dtrace2.dtr' matched 4 probes
CPU ID
zfs depends on ldi_get_size(), which depends on the device being
accessed exporting one of the properties below. i guess the
the devices generated by IBMsdd and/or EMCpower/or don't
generate these properties.
ed
On Wed, Jul 26, 2006 at 01:53:31PM -0700, Eric Schrock wrote:
On Wed, Jul 26,