Re: [zfs-discuss] ZFS and IBM sdd (vpath)

2006-10-18 Thread Geoffroy Doucet
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 >>

Re: [zfs-discuss] ZFS and IBM sdd (vpath)

2006-10-18 Thread Torrey McMahon
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 exportin

Re: [zfs-discuss] ZFS and IBM sdd (vpath)

2006-10-18 Thread Eric Schrock
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 IDFUNCTION:NAME > 1 24930 ldi_get

Re: [zfs-discuss] ZFS and IBM sdd (vpath)

2006-10-18 Thread Geoffroy Doucet
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 IDFUNCTION:NAME 1 24930 ldi_get_size:return-1 With the command: # zpool create tank /dev/d

Re: [zfs-discuss] ZFS and IBM sdd (vpath)

2006-10-18 Thread Eric Schrock
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

[zfs-discuss] ZFS and IBM sdd (vpath)

2006-10-18 Thread Geoffroy Doucet
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 4