Re: [OpenIndiana-discuss] zpool vdev membership misreported

[George Wilson]

Justin,

More than likely c3d1 contain a label from an old pool. If you run 'zdb 
-l /dev/dsk/c3d1s0' you should be able to if one exists. If does contain 
information for an old pool then using the '-f' option when attaching 
will solve your problem and relabel the device with the new pool 
information.


You could also do a 'zpool import' to see if c3d1 shows up with 
information about an exported pool.


Thanks,
George

On 4/19/13 5:20 AM, Justin Warwick wrote:

jrw@valinor:~$ pfexec zpool attach media c2d1 c3d1
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c3d1s0 is part of active ZFS pool rpool. Please see zpool(1M).

Yet I do not see c3d1 in zpool status.  Initially I had 4 disks total, all
Seagate SATA drives, two separate plain two-disk mirrors. I added a couple
more disks, but havn't yet added them to a pool. I noticed that the device
identifiers changed (which I did not expect). I broke the mirror on the
media pool (i can't remember whey I did that). Since that time I have
been getting that message which seems to mean somehow the disk is halfway
stuck in the mirror. Should I just issue the -f override? Am I asking for
trouble if i do?


jrw@valinor:~$ zpool status
   pool: media
  state: ONLINE
   scan: scrub repaired 0 in 3h38m with 0 errors on Sun Feb 17 04:44:29 2013
config:

 NAMESTATE READ WRITE CKSUM
 media   ONLINE   0 0 0
   c2d1  ONLINE   0 0 0

errors: No known data errors

   pool: rpool
  state: ONLINE
   scan: scrub in progress since Fri Apr 19 01:47:19 2013
 27.1M scanned out of 75.9G at 3.87M/s, 5h34m to go
 0 repaired, 0.03% done
config:

 NAMESTATE READ WRITE CKSUM
 rpool   ONLINE   0 0 0
   mirror-0  ONLINE   0 0 0
 c2d0s0  ONLINE   0 0 0
 c3d0s0  ONLINE   0 0 0

errors: No known data errors
jrw@valinor:~$ echo | pfexec format
Searching for disks...done


AVAILABLE DISK SELECTIONS:
0. c2d0 Unknown-Unknown-0001 cyl 60797 alt 2 hd 255 sec 63
   /pci@0,0/pci-ide@11/ide@0/cmdk@0,0
1. c2d1 ST950056- 5YX1J9E-0001-465.76GB
   /pci@0,0/pci-ide@11/ide@0/cmdk@1,0
2. c3d0 ST950056- 5YX1R0Z-0001-465.76GB
   /pci@0,0/pci-ide@11/ide@1/cmdk@0,0
3. c3d1 Unknown-Unknown-0001 cyl 60797 alt 2 hd 255 sec 63
   /pci@0,0/pci-ide@11/ide@1/cmdk@1,0
4. c7d0 ST950056- 5YX1FJF-0001-465.76GB  Media3
   /pci@0,0/pci-ide@14,1/ide@0/cmdk@0,0
5. c7d1 ST950056- 5YX1Q39-0001-465.76GB  Media4
   /pci@0,0/pci-ide@14,1/ide@0/cmdk@1,0
Specify disk (enter its number): Specify disk (enter its number):

  -- Justin
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss



___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss

Re: [OpenIndiana-discuss] zpool vdev membership misreported

[Jim Klimov]

On 2013-04-19 11:20, Justin Warwick wrote:

I broke the mirror on the
media pool (i can't remember whey I did that). Since that time I have
been getting that message which seems to mean somehow the disk is halfway
stuck in the mirror.

Agreeing with George's answer, I'd like to inquire: how did you
break the mirror? The state you describe seems like physical
removal of one disk (c3d1) and then detachment of an absent
component from the remaining live mirror, turning that into
a single-disk pool, and then physical addition of the old disk
back into the system. Due to name and/or guid conflict, this
disk does not get imported as a pool. Maybe due to having the
same GUID as a live pool, it is considered part of one -
mistakenly in fact.

BTW, interesting corner case for our recent discussion of the
possible enhancements to detection and import of rpool (i.e.
for removable media, or to switch HDDs between SATA and IDE
legacy modes easily).

Speaking of which, your cXdY disks on pci-ide bus seem to be
in IDE legacy mode. Is this intentional (or are they really IDE)?
You know this is sub-optimal for SATA, right?.. though use of
this mode may be dictated by other causes (compatibilities with
dual-booted OSes, missing SATA drivers in illumos, etc.)

Cheers,
//Jim


___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@openindiana.org
http://openindiana.org/mailman/listinfo/openindiana-discuss