Date: Thu, 21 Jun 2012 17:01:29 -0500 From: Mark Felder <feld@feld.me> To: freebsd-fs@freebsd.org Subject: Re: ZFS Checksum errors Message-ID: <op.wf9wsrl234t2sn@tech304> In-Reply-To: <1953965235.30115.1340315339964.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net> References: <E22D2EF22A824CC3A0386E62F407F262@multiplay.co.uk> <566221263.21373.1340225701396.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net> <CAGMYy3tW3By4RLj1=q_-NN7GYS_Yv2QY64A4p0z1x8VDe5F-Hg@mail.gmail.com> <1953965235.30115.1340315339964.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Jun 2012 16:48:59 -0500, <rondzierwa@comcast.net> wrote: > this is causing a lot of down time, and its making linux look very > attractive in my organization. how do I get this untangled short of > reformatting and starting over? I'm pretty confident that you have bad hardware and ZFS is telling you so. It's either a memory issue (ECC RAM being used?), or a problem with your controller, cabling, or HDD. Things like this have happened to people and the problem was a faulty power supply or dirty power, too. When ZFS tells you there are errors and checksum mismatches it's doing its best to PROTECT you from corrupted data and you need to start looking at every piece of hardware in your server that can cause this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wf9wsrl234t2sn>