that link suggests that this is a problem with a dirty export: http://www.sun.com/msg/ZFS-8000-EY
maybe try importing on system A again, doing a 'zpool export', waiting for completion, then moving to system B to import? On Sun, Mar 1, 2009 at 2:29 PM, Kyle Kakligian <small...@gmail.com> wrote: > What does it mean for a vdev to have an invalid configuration and how > can it be fixed or reset? As you can see, the following pool can no > longer be imported: (Note that the "last accessed by another system" > warning is because I moved these drives to my test workstation.) > > ~$ zpool import -f pool0 > cannot import 'pool0': invalid vdev configuration > > ~$ zpool import > pool: pool0 > id: 5915552147942272438 > 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: > > pool0 UNAVAIL insufficient replicas > raidz1 UNAVAIL corrupted data > c5d1p0 ONLINE > c4d0p0 ONLINE > c4d1p0 ONLINE > c6d0p0 ONLINE > c5d0p0 ONLINE > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
