Date: Sat, 23 Jan 2010 08:21:11 -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: <5da0588e1001230521h3cbef0b9m9781bb7eb6ff92c@mail.gmail.com> In-Reply-To: <4B5AF018.7070503@modulus.org> References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <ed91d4a81001230011t7aef2da8h3be13d2494c06550@mail.gmail.com> <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> <4B5AE8D7.9000103@modulus.org> <5da0588e1001230443r1fee3b45o906690bc0115bb4e@mail.gmail.com> <4B5AF018.7070503@modulus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I can't; any operations on the file yield EIEIO...err, EIO, input/output error. - Rich On Sat, Jan 23, 2010 at 7:48 AM, Andrew Snow <andrew@modulus.org> wrote: > Rich wrote: >> >> 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. > > That is the normal behaviour if there are no additional copies of the data > to go from (via mirroring or RAIDZ): it sees that the file has blocks with > incorrect checksums, but it won't take action as there's no way to know if > the file data is corrupt or the checksum value is wrong. > > You might be able to clear it by renaming the file and copying it back in > place, and thus the new file will not have any bad checksums (but likely > will contain corrupt data). > > - Andrew > -- You are an insult to my intelligence! I demand that you log off immediately.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5da0588e1001230521h3cbef0b9m9781bb7eb6ff92c>