Hi Michelle,
Your previous mail about the disk label reverting to EFI makes me wonder
whether you used the format -e option to relabel the disk, but your disk
label below looks fine.
This also might be a known bug (6419310), whose workaround is to use the
-f option to zpool attach.
An interim test would be to create a test pool with c19d0s0, like this:
# zpool create test c19d0s0
If that works, then destroy the test pool and try to attach it to the
root pool. If it complains again, then use the -f option.
Thanks,
Cindy
On 01/28/10 15:29, Michelle Knight wrote:
A bit more information... this is what I've used the all free hog to
generate....
Part Tag Flag Cylinders Size Blocks
0 unassigned wm 3 - 9725 74.48GB (9723/0/0) 156199995
1 unassigned wm 0 0 (0/0/0) 0
2 backup wu 0 - 9725 74.50GB (9726/0/0) 156248190
3 unassigned wm 0 0 (0/0/0) 0
4 unassigned wm 0 0 (0/0/0) 0
5 unassigned wm 0 0 (0/0/0) 0
6 unassigned wm 0 0 (0/0/0) 0
7 unassigned wm 0 0 (0/0/0) 0
8 boot wu 0 - 0 7.84MB (1/0/0) 16065
9 alternates wm 1 - 2 15.69MB (2/0/0) 32130
...and when I attempt to add c19d0s0 to the pool, I get...
m...@cougar:~# zpool attach rpool c7d0s0 c19d0s0
invalid vdev specification
use '-f' to override the following errors:
/dev/dsk/c19d0s0 overlaps with /dev/dsk/c19d0s2
Is it OK for me to use the -f or have I got something critically wrong here?
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
