> > Disk /dev/zvol/rdsk/pool/dcpool: 4295GB
> > Sector size (logical/physical): 512B/512B
>
>
> Just to check, did you already try:
>
> zpool import -d /dev/zvol/rdsk/pool/ poolname
>
Thanks for the sugestion. As a matter of fact, I did not try that.
But it hasn't helped (possibly tue to parti
Disk /dev/zvol/rdsk/pool/dcpool: 4295GB
Sector size (logical/physical): 512B/512B
Just to check, did you already try:
zpool import -d /dev/zvol/rdsk/pool/ poolname
?
thanks Andy.
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://m
> The volume is exported as whole disk. When given whole disk, zpool
> creates GPT partition table by default. You need to pass the partition
> (not the disk) to zdb.
Yes, that is what seems to be the problem.
However, for the zfs volumes (/dev/zvol/rdsk/pool/dcpool) there seems
to be no concept o
On Tue, May 31, 2011 at 5:47 PM, Jim Klimov wrote:
> However it seems that there may be some extra data beside the zfs
> pool in the actual volume (I'd at least expect an MBR or GPT, and
> maybe some iSCSI service data as an overhead). One way or another,
> the "dcpool" can not be found in the phy
I have a oi_148a test box with a pool on physical HDDs, a volume in
this pool shared over iSCSI with explicit commands (sbdadm and such),
and this iSCSI target is initiated by the same box. In the resulting iSCSI
device I have another ZFS pool "dcpool".
Recently I found the iSCSI part to be a pote
