Are hot spares implmented yet?

I got Solaris 2006 6/06 installed and setup a ZFS pool and ZFS filesystem.

# zpool status
  pool: data
 state: ONLINE
 scrub: none requested
config:

        NAME                                         STATE     READ WRITE CKSUM
        data                                         ONLINE       0     0     0
          mirror                                     ONLINE       0     0     0
            c4t60001FE1000DAD9000092110348000DAd0s2  ONLINE       0     0     0
            c4t60001FE1000DAD9000092110348000D7d0s2  ONLINE       0     0     0
          mirror                                     ONLINE       0     0     0
            c4t60001FE1000DAD9000092110348000E0d0s2  ONLINE       0     0     0
            c4t60001FE1000DAD9000092110348000C3d0s2  ONLINE       0     0     0
           ...etc...
     errors: No known data errors
       

 I assumed I was going to be able to add spares later, but when I tried to add 
a spare, it said:

   # zpool add data spare c4t60001FE1000DAD9000092110348000F5d0s2
   cannot open 'spare': no such device in /dev/dsk
   must be a full path or shorthand device name

I tried to add my spare(s) as art of the create subcommand and got the same 
message.
For some reason, it doesn't seem to be implemented.  My zpool man page says 
this:
    The  pool  names  "mirror",  "raidz",  and "spare"  are  reserved,  as are 
names
    beginning with the pattern "c[0-9]".

I look at the binary to see that it wouldn't understand "spare" as being 
special at all.

  # strings /usr/sbin/zpool | egrep 'spare|mirror|raidz'
  mirror
  raidz
  mirror
  raidz

So I suspect I don't have support for hot spares in Solaris 2006 6/06 (aka U2).

Is there a Nevada version which supports zpool spares?  My "uname -srv" says I 
have "SunOS 5.11 snv_40".  or is there an update I can get?

Thanks, ez
 
 
This message posted from opensolaris.org
_______________________________________________
zfs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to