On Wed, 2013-05-15 at 10:39 -0700, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 05/15/13 10:20, O. Hartmann wrote: > > Several machines running FreeBSD 10.0-CURRENT #0 r250636: Tue May > > 14 21:13:19 CEST 2013 amd64 were scrubbing the pools over the past > > two days. Since that takes a while, I was sure I could shutdown the > > boxes and scrubbing will restart next restart automatically. > > > > Not this time! On ALL(!) systems (three) the pools remains > > destroyed/corrupted showing this message(s) (as a representative, I > > will present only one): > > Have you tried to import the pool with '-f -F -X', i.e.: > > zpool import -f -F -X ASGARD00 ? > > Cheers, > - -- > Xin LI <[email protected]> https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die
All right,
I had first to export the pool before i could import it again. After
import, the scrubbing goes on and it seems all right so far.
The One-Disk-Pool, the other one that failed, seems to have different
IDs since import compalins about multiple existences of a pool with the
very same name. How can this happen?
root@b211:/root # zpool import
pool: BACKUP00
id: 257822624560506537
state: FAULTED
status: The pool metadata is corrupted.
action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported
using
the '-f' flag.
see: http://illumos.org/msg/ZFS-8000-72
config:
BACKUP00 FAULTED corrupted data
ada3p1 ONLINE
pool: BACKUP00
id: 9337833315545958689
state: FAULTED
status: One or more devices contains corrupted data.
action: The pool cannot be imported due to damaged devices or data.
The pool may be active on another system, but can be imported
using
the '-f' flag.
see: http://illumos.org/msg/ZFS-8000-5E
config:
BACKUP00 FAULTED corrupted data
8544670861382329237 UNAVAIL corrupted data
signature.asc
Description: This is a digitally signed message part
