Is there anyway, yet, to import a pool with corrupted space_map errors, or "zio-io_type != ZIO_TYPE_WRITE" assertions?
I have a pool comprised of 4 raidz2 vdevs of 6 drives each. I have almost 10 TB of data in the pool (3 TB actual disk space used due to dedup and compression). While testing various failure modes, I have managed to corrupt the pool to the point where it won't import. So much for being bulletproof. :( If I try to import the pool normally, it give corrupted space_map errors. If I try to "import -F" the pool, it complains that "zio-io_type != ZIO_TYPE_WRITE". I've also tried the above with "-o readonly=on" and "-R some/other/root" variations. There's also no zfs.cache file anywhere to be found, and creating a blank file doesn't help. Does this mean that a 10 TB pool can be lost due to a single file being corrupted, or a single piece of pool metadata being corrupted? And that there's *still* no recovery tools for situations like this? Running ZFSv28 on 64-bit FreeBSD 8-STABLE. For the curious, the failure mode that causes this? Rebooting while 8 simultaneous rsyncs were running, which were not killed by the shutdown process for some reason, which prevented 8 ZFS filesystems from being unmounted, which prevented the pool from being exported (even though I have a "zfs unmount -f" and "zpool export -f" fail-safe), which locked up the shutdown process requiring a power reset. :( -- Freddie Cash fjwc...@gmail.com _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
