i've got a little zpool with a naughty raidz vdev that won't take a
replacement that as far as i can tell should be adequate.
a history: this could well be some bizarro edge case, as the pool doesn't
have the cleanest lineage. initial creation happened on NexentaCP inside
vmware in linux. i had given the virtual machine raw device access to 4
500gb drives and 1 ~200gb drive, with which I made my raidz vdev, knowing
that i could replace the 200 with a 500gb when i got another. unfortunately,
the device names that vmware was pointed to proved not to be quite stable,
and one of the drives in the pool got swapped with the drive containing my
linux root. whoops! seemed like a good time to install SXCE.
so here i am, i've got the pool imported into the new setup. one of the
drives is showing as degraded (the one that got pointed at the linux root).
i attempted to replace this drive with a 300GB drive that was going to be
used for something else, but no luck- replace said the device wasn't large
enough. fair enough- everything else in there is 500gb (despite the pool
size still showing as 800G), so i just assumed zpool wasn't allowing the
replacement because everything else was a 500gb drive. fair enough.
so i get a 500gb drive- the exact same drive, in fact, as the other drives
in the pool. i install it, attempt to replace it, but get the same error-
the device is too small. this seems wrong.
as far as i can tell, there's no way to get the zpool command to tell you
what it thinks the smallest drive appropriate for replacement is, so i'm
left wondering why this won't work.
ideas, anyone? have i run into a bug or just done something daft? possibly
both?
below are some hopefully useful command outputs:
[EMAIL PROTECTED]:~$ zpool list data
NAME SIZE USED AVAIL CAP HEALTH ALTROOT
data 931G 803G 128G 86% DEGRADED -
[EMAIL PROTECTED]:~$ zpool status data
pool: data
state: DEGRADED
status: One or more devices could not be opened. Sufficient replicas exist
for
the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
see: http://www.sun.com/msg/ZFS-8000-2Q
scrub: resilver completed with 0 errors on Sat Oct 13 20:42:18 2007
config:
NAME STATE READ WRITE CKSUM
data DEGRADED 0 0 0
raidz1 DEGRADED 0 0 0
c4d0 ONLINE 0 0 0
c5d0 ONLINE 0 0 0
c4d1 ONLINE 0 0 0
c5d1 ONLINE 0 0 0
c2t4d0 UNAVAIL 0 0 0 cannot open
errors: No known data errors
[EMAIL PROTECTED]:~$ sudo format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c0d0 <DEFAULT cyl 24318 alt 2 hd 255 sec 63>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED],0
1. c0d1 <ST320082- 4LJ0QEG-0001-186.31GB>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED],0
2. c1d0 <ST320082- 3LJ3CD0-0001-186.31GB>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED],0
3. c2d0 <ST320082- 5LJ03Y4-0001-186.31GB>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED],0
4. c3d0 <ST350063- 9QG3TVD-0001-465.76GB>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL
PROTECTED],0
5. c4d0 <ST350063- 6QG0AEC-0001-465.76GB>
/[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/[EMAIL
PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
6. c4d1 <ST350063- 6QG0949-0001-465.76GB>
/[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/[EMAIL
PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
7. c5d0 <ST350063- 6QG0B8A-0001-465.76GB>
/[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/[EMAIL
PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
8. c5d1 <ST350063- 6QG0A9N-0001-465.76GB>
/[EMAIL PROTECTED],0/pci10de,[EMAIL PROTECTED]/[EMAIL
PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
Specify disk (enter its number): ^C
[EMAIL PROTECTED]:~$ sudo zpool replace data c2t4d0 c3d0
cannot replace c2t4d0 with c3d0: device is too small
[EMAIL PROTECTED]:~$ iostat -En
c0d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3200822A Revision: Serial No: 4LJ Size:
200.05GB<200047067136 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c0d1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3200822A Revision: Serial No: 4LJ Size:
200.05GB<200047067136 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c4d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3500630AS Revision: Serial No: 6QG Size:
500.10GB<500101152768 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c4d1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3500630AS Revision: Serial No: 6QG Size:
500.10GB<500101152768 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c5d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3500630AS Revision: Serial No: 6QG Size:
500.10GB<500101152768 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c5d1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3500630AS Revision: Serial No: 6QG Size:
500.10GB<500101152768 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c2d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3200822AS Revision: Serial No: 5LJ Size:
200.05GB<200047067136 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c3d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3500630AS Revision: Serial No: 9QG Size:
500.10GB<500101152768 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
c1d0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Model: ST3200822A Revision: Serial No: 3LJ Size:
200.05GB<200047067136 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 0
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
