On Wed, Aug 24, 2011 at 1:23 PM, Cindy Swearingen
<cindy.swearin...@oracle.com> wrote:
> I wonder if you need to make links from the original device
> name to the new device names.
>
> You can see from the zdb -l output below that the device path
> is pointing to the original device names (really long device
> names).
Thank you for this suggestion. I've created symlinks from the
/dev/dsk directory pointing to the dd image, but zpool import says the
same thing. However, look at the error message below. zpool can
see the hostname of the last system to use the pool, but the date
looks like the epoch (Dec 31 1969). Is this meaningful?
# ln -s /jbod1-diskbackup/restore/deep_Lun0.dd
/dev/dsk/c4t526169645765622E436F6D202020202030303330383933323030303130363120d0s0
# ln -s /jbod1-diskbackup/restore/deep_san01_lun.dd
/dev/dsk/c4t526169645765622E436F6D202020202030303131383933323030303130354220d0s0
# zpool import -d .
pool: deep
id: 8026270260630449340
state: UNAVAIL
status: The pool was last accessed by another system.
action: The pool cannot be imported due to damaged devices or data.
see: http://www.sun.com/msg/ZFS-8000-EY
config:
deep UNAVAIL
insufficient replicas
/jbod1-diskbackup/restore/deep_san01_lun.dd UNAVAIL cannot open
/jbod1-diskbackup/restore/deep_Lun0.dd UNAVAIL cannot open
# zpool import -d . -F deep
cannot import 'deep': pool may be in use from other system, it was
last accessed by vali.REDACTED (hostid: 0x2a8c28ca) on Wed Dec 31
16:00:00 1969
use '-f' to import anyway
# zpool import -d . -F -f deep
cannot import 'deep': one or more devices is currently unavailable
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
