On 11/28/06, Frank Cusack <[EMAIL PROTECTED]> wrote:
I suspect this will be the #1 complaint about zfs as it becomes more popular. "It worked before with ufs and hw raid, now with zfs it says my data is corrupt! zfs sux0rs!"
That's not the problem, so much as "zfs says my file system is corrupt, how do I get past this?" With ufs, f'rinstance, I'd run an fsck, kiss the bad file(s) goodbye, and be on my way. With zfs, there's this ominous message saying "destroy the filesystem and restore from tape". That's not so good, for one corrupt file. And even better, turns out erasing the file might just be enough. Although in my case, I now have a new bad object. Sun pointed me to docs.sun.com (thanks, that helps!) but I haven't found anything in the docs on this so far. I am assuming that my bad object 45654c is an inode number of a special file of some sort, but what? And what does the range mean? I'd love to read the docs on htis
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
