Date: Thu, 10 Jan 2013 13:12:54 -0800 From: Artem Belevich <art@freebsd.org> To: Nicolas Rachinsky <fbsd-mas-0@ml.turing-complete.org> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: slowdown of zfs (tx->tx) Message-ID: <CAFqOu6iUb%2BFieH2%2BmYQj-a4xorSKEejAxg4%2Bt041m28Pq6xC5g@mail.gmail.com> In-Reply-To: <20130110193949.GA10023@mid.pc5.i.0x5.de> References: <20130108174225.GA17260@mid.pc5.i.0x5.de> <CAFqOu6jgA8RWV5d%2BrOBk8D=3Vu3yWSnDkAi1cFJ0esj4OpBy2Q@mail.gmail.com> <20130109162613.GA34276@mid.pc5.i.0x5.de> <CAFqOu6jrng=v8eVyhqV-PBqJM_dYy%2BU7X4%2B=ahBeoxvK4mxcSA@mail.gmail.com> <20130110193949.GA10023@mid.pc5.i.0x5.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 10, 2013 at 11:39 AM, Nicolas Rachinsky <fbsd-mas-0@ml.turing-complete.org> wrote: > There is an UDMA_CRC_Error_Count of 17 and 20 for the two disks with > checksum errors. The other disks have values between 0 and 5. > > And yes, there have been timeouts some time ago. Since the problem did > occur without the timeout occuring again, I considered the timeouts to > be unrelated. And then I forgot them. :( > > > But shouldn't timeouts either produce correct data after a retry or > a read/write error otherwise? if I see CRC counter incrementing often enough that's a good indication that something is wrong. It does not mean that those transactions were the ones that corrupted data, but rather as an indication that things are not right with particular device. It may be a false alarm as CRC errors may happen under normal conditions, but non-trivial number of them is a good sign of trouble. --Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFqOu6iUb%2BFieH2%2BmYQj-a4xorSKEejAxg4%2Bt041m28Pq6xC5g>