IIRC, uncorrectable bitrot even in a nonessential file detected by ZFS used to cause a kernel panic. Bug ID 4924238 was closed with the claim that bitrot-induced panics is not a bug, but the description did mention an open bug ID 4879357, which suggests that it's considered a bug after all.
Can somebody clarify the intended behavior? For example, if I'm running Solaris in a VM, then I shut down the VM, flip a bit in the file which hosts the disk for the VM such that a nonessential file on that disk is corrupted, and then power up the VM and try to read that file so that ZFS detects bitrot and there's no mirror available to correct the bitrot, then what is supposed to happen? This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list [EMAIL PROTECTED] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
