On Wed, Mar 17, 2010 at 1:27 PM, Geoff <geoffakerlund at gmail.com> wrote:
> Hi Giovanni, > > I think I see where you're going with this. I incorrectly assumed that > disk c8t0d0 was my rpool, because it's at the top of the list with the > "format" command. However "zpool status" shows that my rpool is actually > disk c8t5d0. But then why, when I try to format c8t0d0, does it say > "c8t0d0s0 is part of active ZFS pool rpool". Surely both disks can't be > part of my rpool, can they? > > IMHO, that's unlikely. At least not the same rpool that is active now. My theory is that OpenSolaris was installed on c8t0d0 at some point and then it was reinstalled on c8t5d0. I did a little experiment in a virtual machine to see if I could reproduce your situation. 1. Created a 'tank' pool on c9t0d0 2. Turned machine off and removed disk 3. Booted it up 4. Destroyed 'tank' pool (it was degraded and the disk was off) 5. Created a 'tank' pool on c9t1d0 6. Turned machine off and re-added disk c9t0d0 7. Booted it up 8. Tried to format c9t0d0 (didn't say anything about being part of an active pool) 8. Tried to attach c9t0d0 to c9t1d0 (failed) # zpool attach tank c9t1d0 c9t0d0 invalid vdev specification use '-f' to override the following errors: /dev/dsk/c9t0d0s0 is part of exported or potentially active ZFS pool tank. Please see zpool(1M). ... which slightly differs from your error. This is on build 111b and I was using whole disks. Also, ZFS on the rpool has some peculiarities with EFI labels that I don't know much about (compared to non-root pools). Perhaps someone can help here. After you figured out that your root device was c8t5d0 instead of c8t0d0, did you repeat the prtvtoc/fmthard step ? Not sure it would help though since it wouldn't touch c8t0d0. -- Giovanni -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20100317/46c984f3/attachment.html>
