On Thu, Oct 9, 2008 at 4:53 AM, . <[EMAIL PROTECTED]> wrote: > While it's clearly my own fault for taking the risks I did, it's > still pretty frustrating knowing that all my data is likely still > intact and nicely checksummed on the disk but that none of it is > accessible due to some tiny filesystem inconsistency. ?With pretty > much any other FS I think I could get most of it back. > > Clearly such a small number of occurrences in what were admittedly > precarious configurations aren't going to be particularly convincing > motivators to provide a general solution, but I'd feel a whole lot > better about using ZFS if I knew that there were some documented > steps or a tool (zfsck? ;) that could help to recover from this kind > of metadata corruption in the unlikely event of it happening.
Well said. You have hit on my #1 concern with deploying ZFS. FWIW, I belive that I have hit the same type of bug as the OP in the following combinations: - T2000, LDoms 1.0, various builds of Nevada in control and guest domains. - Laptop, VirtualBox 1.6.2, Windows XP SP2 host, OpenSolaris 2008.05 @ build 97 guest In the past year I've lost more ZFS file systems than I have any other type of file system in the past 5 years. With other file systems I can almost always get some data back. With ZFS I can't get any back. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
