On Tue, Aug 11, 2009 at 09:35:53AM -0700, Sascha wrote:
> Then creating a zpool:
> [b]zpool create -m /zones/huhctmp huhctmppool
> c6t6001438002A5435A00010000005A0000d0[/b]
>
> [b]zpool list[/b]
> NAME SIZE USED AVAIL CAP HEALTH ALTROOT
> huhctmppool 59.5G 103K 59.5G 0% ONLINE -
I recall your original question was about a larger disk (>1TB). My
assumption is that the zpool create has created an EFI label here, but
it would be nice to confirm with 'format' or 'prtvtoc' output.
[skipping ahead]
> format> type
>
> AVAILABLE DRIVE TYPES:
> 0. Auto configure
> 1. other
> Specify disk type (enter its number)[1]: 0
> c6t6001438002A5435A00010000005A0000d0: configured with capacity of 70.00GB
> <HP-HSV210-6200-70.00GB>
> selecting c6t6001438002A5435A00010000005A0000d0
> [disk formatted]
My fear is that with a small disk and not running 'format -e' it's
placed an SMI label on the disk. Again, confirming that would be nice.
The label in this section must match the label in the first section. If
they're both EFI, you should be good. If it put an SMI label on, the
data won't line up. If that's all that's wrong, you can repeat this
step on your lun and should still be good.
(use 'format -e' and when labeling it should prompt you for the label
type).
> And in the end trying to import:
> zpool import huhctmppool
Hmm, you've skipped the partitioning step (which should be done after
applying the new label). I would make sure that slice 0 encompasses the
full 70G. Basically, make the partitioning here look like it used to,
but with more data in the slice.
So
#1. Confirm you have EFI labels before and after running format
#2. Partition the disk after the label to look like it used to (but
with a larger slice)
--
Darren
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
