Date: Tue, 15 Jun 2010 11:44:56 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-fs@freebsd.org Subject: Re: CFT: periodic scrubbing of ZFS pools Message-ID: <20100615114456.49994h9g40qhcnms@webmail.leidinger.net> In-Reply-To: <AANLkTilBqAsDnDs4nlsVjBdt1U9554t9rNuzMruqRJqE@mail.gmail.com> References: <20100610162629.38992mazf0sfdqg0@webmail.leidinger.net> <hut8o7$q2o$1@dough.gmane.org> <20100611172033.42001s90ahe57oe8@webmail.leidinger.net> <AANLkTilBqAsDnDs4nlsVjBdt1U9554t9rNuzMruqRJqE@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Ivan Voras <ivoras@freebsd.org> (from Fri, 11 Jun 2010 18:11:45 +0200): > On 11 June 2010 17:20, Alexander Leidinger <Alexander@leidinger.net> wrote: >> Quoting Ivan Voras <ivoras@freebsd.org> (from Fri, 11 Jun 2010 14:04:24 >> +0200): > >>> Fairly good and useful, but could you add a small check of "zpool >>> status" information before scrubbing that would a) complain LOUDLY AND >>> VISIBLY if a previous scrub failed and b) skip issuing a new scrub >>> command if there is such an error, to avoid stressing possibly broken >>> hardware? >> >> Can you please provide an example of such a failed scrub? > > You should probably treat any status message that doesn't have "none > requested" or "scrub completed with 0 errors..." as failed. I prefer to make it explicit instead of failing on everything which is unknown. > I could setup a gnop device with errors to prove it if you'd like :) Would be great. Bye, Alexander. -- "My two friends have my share of the money, I'll have to speak to them." -- Vito Corleone, "Chapter 14", page 197 http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100615114456.49994h9g40qhcnms>