Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like powerpath, MPXIO or VxDMP. Here is the error message when I try to create my pool: bash-3.00# zpool create tank /dev/dsk/vpath1a warning: device in use checking failed: No such device internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c bash-3.00# zpool create tank /dev/dsk/vpath1c cannot open ''/dev/dsk/vpath1c'': I/O error bash-3.00# zpool create tank vpath1 cannot open ''vpath1'': no such device in /dev/dsk must be a full path or shorthand device name bash-3.00# zpool create tank vpath1c cannot open ''/dev/dsk/vpath1c'': I/O error bash-3.00# zpool create tank vpath1a warning: device in use checking failed: No such device internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c Is there anyone else that use ZFS with IBM sdd? This message posted from opensolaris.org
On Wed, Oct 18, 2006 at 06:57:21AM -0700, Geoffroy Doucet wrote:> Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like powerpath, MPXIO or VxDMP. > > Here is the error message when I try to create my pool: > bash-3.00# zpool create tank /dev/dsk/vpath1a > warning: device in use checking failed: No such device > internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.c > bash-3.00# zpool create tank /dev/dsk/vpath1c > cannot open ''/dev/dsk/vpath1c'': I/O error > bash-3.00# zpool create tank vpath1 > cannot open ''vpath1'': no such device in /dev/dsk > must be a full path or shorthand device name > bash-3.00# zpool create tank vpath1c > cannot open ''/dev/dsk/vpath1c'': I/O error > bash-3.00# zpool create tank vpath1a > warning: device in use checking failed: No such device > internal error: unexpected error 22 at line 446 of ../common/libzfs_pool.cMy guess for the first case (vpath1a) is that the IBM driver is not correctly implementing the necessary DDI properties for ZFS to determine the configuration of the device. What bits are you using? Off the top of my head, this should catch the most likely candidate: # dtrace -n ldi_get_size:return''{trace(arg1)}'' I''d also check to see if there are any updates from IBM. From the looks of it, ''vpath1c'' cannot even be opened from userland, so something else seems misconfigured in that case. - Eric -- Eric Schrock, Solaris Kernel Development http://blogs.sun.com/eschrock
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
> On Wed, Oct 18, 2006 at 06:57:21AM -0700, Geoffroy Doucet wrote:
>> Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like
>> powerpath, MPXIO or VxDMP.
>>
>> Here is the error message when I try to create my pool:
>> bash-3.00# zpool create tank /dev/dsk/vpath1a
>> warning: device in use checking failed: No such device
>> internal error: unexpected error 22 at line 446 of
>> ../common/libzfs_pool.c
>> bash-3.00# zpool create tank /dev/dsk/vpath1c
>> cannot open ''/dev/dsk/vpath1c'': I/O error
>> bash-3.00# zpool create tank vpath1
>> cannot open ''vpath1'': no such device in /dev/dsk
>> must be a full path or shorthand device name
>> bash-3.00# zpool create tank vpath1c
>> cannot open ''/dev/dsk/vpath1c'': I/O error
>> bash-3.00# zpool create tank vpath1a
>> warning: device in use checking failed: No such device
>> internal error: unexpected error 22 at line 446 of
>> ../common/libzfs_pool.c
>
> My guess for the first case (vpath1a) is that the IBM driver is not
> correctly implementing the necessary DDI properties for ZFS to determine
> the configuration of the device. What bits are you using? Off the top
> of my head, this should catch the most likely candidate:
>
> # dtrace -n ldi_get_size:return''{trace(arg1)}''
>
> I''d also check to see if there are any updates from IBM. From the
looks
> of it, ''vpath1c'' cannot even be opened from userland, so
something else
> seems misconfigured in that case.
>
> - Eric
>
> --
> Eric Schrock, Solaris Kernel Development
> http://blogs.sun.com/eschrock
>
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.cYep. 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
Eric Schrock wrote:> Chances are they have already heard of this bug, as I seem to > remember it coming up before. >Comes up all the time on the storage lists. Especially, when people try to get mpxio to work with the underlying arrays instead of sdd(vpath). Last I recall they aren''t exporting the LUNs with the proper IEEE Registered Extended bits....but that was awhile ago.
You are right I am not the first one, with a little bit a research I found this tread: http://mail.opensolaris.org/pipermail/zfs-discuss/2006-July/003937.html> On Wed, Oct 18, 2006 at 06:57:21AM -0700, Geoffroy Doucet wrote: >> Hello, I am trying to configure ZFS with IBM sdd. IBM sdd is like >> powerpath, MPXIO or VxDMP. >> >> Here is the error message when I try to create my pool: >> bash-3.00# zpool create tank /dev/dsk/vpath1a >> warning: device in use checking failed: No such device >> internal error: unexpected error 22 at line 446 of >> ../common/libzfs_pool.c >> bash-3.00# zpool create tank /dev/dsk/vpath1c >> cannot open ''/dev/dsk/vpath1c'': I/O error >> bash-3.00# zpool create tank vpath1 >> cannot open ''vpath1'': no such device in /dev/dsk >> must be a full path or shorthand device name >> bash-3.00# zpool create tank vpath1c >> cannot open ''/dev/dsk/vpath1c'': I/O error >> bash-3.00# zpool create tank vpath1a >> warning: device in use checking failed: No such device >> internal error: unexpected error 22 at line 446 of >> ../common/libzfs_pool.c > > My guess for the first case (vpath1a) is that the IBM driver is not > correctly implementing the necessary DDI properties for ZFS to determine > the configuration of the device. What bits are you using? Off the top > of my head, this should catch the most likely candidate: > > # dtrace -n ldi_get_size:return''{trace(arg1)}'' > > I''d also check to see if there are any updates from IBM. From the looks > of it, ''vpath1c'' cannot even be opened from userland, so something else > seems misconfigured in that case. > > - Eric > > -- > Eric Schrock, Solaris Kernel Development > http://blogs.sun.com/eschrock >