On Wed, Oct 18, 2006 at 02:15:42PM -0400, Geoffroy Doucet wrote:
> Here is the ouput of your DTrace script:
>
> # dtrace -n ldi_get_size:return'{trace(arg1)}'
> dtrace: description 'ldi_get_size:return' matched 1 probe
> CPU ID FUNCTION:NAME
> 1 24930 ldi_get_size:return -1
>
> With the command:
> # zpool create tank /dev/dsk/vpath1c
> warning: device in use checking failed: No such device
> internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c
Yep. This is a bug in the IBM driver code. There are a number of ddi
properties ("NBlocks", "nblocks", "Size", and "size") that a driver can
export we can calculate the size. Looks like the IBM driver is
exporting none of these, so we have no (generic) way of knowing how big
the underlying device is. I would escalate this with IBM, and point to
the ldi_get_size() source on opensolaris.org for information on what we
expect. Chances are they have already heard of this bug, as I seem to
remember it coming up before.
- Eric
--
Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
