Date: Wed, 15 Aug 2012 15:19:36 +0800 From: Marcelo Araujo <araujobsdport@gmail.com> To: =?ISO-8859-1?Q?Karli_Sj=F6berg?= <Karli.Sjoberg@slu.se> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Hang when importing pool Message-ID: <CAOfEmZiULMau7y6mXuCA4A1rhWJz29LOXmUTo4WiX5i-FFzQnQ@mail.gmail.com> In-Reply-To: <49C9D08A-85EF-4D23-B07F-F3980CBA5A97@slu.se> References: <D13A3EA7-B229-4B78-915E-A3CC3162DB8A@slu.se> <CAOjFWZ52XvMO%2BA7cwa3fnkJcXMCbGgWD91gvZsmW8Navh0AZ9A@mail.gmail.com> <49C9D08A-85EF-4D23-B07F-F3980CBA5A97@slu.se>
next in thread | previous in thread | raw e-mail | index | archive | help
2012/8/15 Karli Sj=F6berg <Karli.Sjoberg@slu.se> > > > I=B4m willing to try anything at this point. Any longshots you have are m= ost > welcome, since it couldn=B4t get any worse:( > > Dear Karli, As you are willing to try anything, you can try it by your own risk, I'd like just to point out that, you shall lost data. You can try two different options and both of them are dangerous for your data: 1) Import the pool in verbatim mode, even if there is any faulted vdevs, this option treats the pool configuration as it is completed. # zpool import -V pool | id 2) Used with the -F recovery option, try to import a non-importable pool from an extreme rewind. # zpool import -V pool | id Once again, as an advice, use those 2 options above, only if you really don't have any more ideas to solve your problem. Both of options can damage your data, and you might never recover it once again. Best Regards, --=20 Marcelo Araujo araujo@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOfEmZiULMau7y6mXuCA4A1rhWJz29LOXmUTo4WiX5i-FFzQnQ>