Date: Sat, 23 Jan 2010 07:43:35 -0500 From: Rich <rincebrain@gmail.com> To: Andrew Snow <andrew@modulus.org> Cc: freebsd-fs@freebsd.org Subject: Re: Errors on a file on a zpool: How to remove? Message-ID: <5da0588e1001230443r1fee3b45o906690bc0115bb4e@mail.gmail.com> In-Reply-To: <4B5AE8D7.9000103@modulus.org> References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <ed91d4a81001230011t7aef2da8h3be13d2494c06550@mail.gmail.com> <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> <4B5AE8D7.9000103@modulus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
zpool clear always clears the checksum column whenever I run it. Then, as soon as I touch those files again, or run a scrub, the checksum error numbers tick up on those three disks, and those entries appear in /var/log/messages. - Rich On Sat, Jan 23, 2010 at 7:17 AM, Andrew Snow <andrew@modulus.org> wrote: > Rich wrote: >> >> Scrubbing repeatedly does nothing to remove the note about that error, >> and I'd rather like to avoid trying to recreate a 7TB pool. > > If you have bad hardware, its quite possible for ZFS to get itself into a > state that it cannot repair itself. =A0The claim about "never needs fsck"= only > applies if the hardware is doing what is expected of it. This especially > goes for a pool with zero redundancy, like yours. > > Its pretty good that ZFS can report the checksum failures where with othe= r > filesystems wouldn't even know something's wrong until it starts returnin= g > garbled data or crashes the whole kernel. > > I presume you have already tried "zpool clear" ? > > - Andrew > > --=20 Life is a yo-yo, and mankind ties knots in the string.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5da0588e1001230443r1fee3b45o906690bc0115bb4e>