On Thu 2011-12-01 (14:19), Freddie Cash wrote:
You will need to find a lot of extra RAM to stuff into that machine in
order for it to boot correctly, load the dedeupe tables into ARC, process
the intent log, and then import the pool.
Thanks guys, managed to get 24GB together and it made it
2011-12-02 18:25, Steve Gonczi пишет:
Try to run a zdb -b poolname ..
This should report any leaked or double allocated blocks.
(It may or may not run, it tends to run out of memory and crash on large
I would be curious what zdb reports, and whether you are able to run it
On Fri, Dec 2, 2011 at 02:58, Jim Klimov jimkli...@cos.ru wrote:
My question still stands: is it possible to recover
from this error or somehow safely ignore it? ;)
I mean, without backing up data and recreating the
If the problem is in metadata but presumably the
pool still works,