[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensolaris-storage-discuss
Subject:    Re: [storage-discuss] [zfs-discuss]  ZFS and fibre channel issues
From:       "James C. McPherson" <James.McPherson () Sun ! COM>
Date:       2008-05-16 0:13:51
Message-ID: 482CD1BF.6010209 () Sun ! COM
[Download RAW message or body]

Hi William,
comments below (after snipping)


William Yang wrote:
> No typo, which is why I think this is a bug somewhere.  d14 has never 
> been a member of nalgene.  d0 is an active disk in pool nalgene.
>  
> My best guess is that there is an incorrect assumption somewhere that 
> assumes the disk is always d0 (probably because it is more common to 
> have single-disk targets rather than multidisk targets?).  Even running 
> format gives a warning:
> hostname:~# format /dev/rdsk/c6t21800080E512C872d14s0
> selecting /dev/rdsk/c6t21800080E512C872d14s0
> [disk formatted]
> /dev/dsk/c6t21800080E512C872d0s0 is part of active ZFS pool nalgene. 
> Please see zpool(1M).
>  
> (The same warning occurs if I use s2 instead of s0.)

Yes, that does look like a bug, please file one on bugs.opensolaris.org

....
>>     William Yang wrote:
>>       
>>>     I am having issues creating a zpool using entire disks with a fibre 
>>>     channel array.  The array is a Dell PowerVault 660F.
>>>     When I run "zpool create bottlecap c6t21800080E512C872d14 
>>>     c6t21800080E512C872d15", I get the following error:
>>>     invalid vdev specification
>>>     use '-f' to override the following errors:
>>>     /dev/dsk/c6t21800080E512C872d0s0 is part of active ZFS pool nalgene. 


What you're seeing here is the interposition of libdiskmgmt,
which is what we use to figure out whether a device is in
use by a filesystem when you're trying to do a potentially
data-destructive operation on it.

Based on my limited investigation so far, it appears that
one layer is making an assumption about your disk based on
the devid:

         path='/dev/dsk/c6t21800080E512C872d14s0'
           devid='id1,ssd@x21000080e512c872/a'


I don't have a multi-lun per target system to check this,
so you'll have to do this - when you log your bug could
you please include the output from

prtconf -v

and

zdb -l /dev/dsk/.....  for each of the luns attached
to your targets on this controller.



James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp	http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
storage-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
[prev in list] [next in list] [prev in thread] [next in thread]