Date: Tue, 14 Apr 2009 13:23:33 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Sean Bruno <sean.bruno@dsl-only.net> Cc: freebsd-hackers@FreeBSD.org, Alexander Motin <mav@FreeBSD.org> Subject: Re: smart self-test vs 7200.12/ich9r/ahci Message-ID: <49E46425.9070205@icyb.net.ua> In-Reply-To: <49E35F92.6080400@icyb.net.ua> References: <49DDF710.4050004@icyb.net.ua> <1239562968.11309.1.camel@localhost.localdomain> <49E2E47D.5070402@icyb.net.ua> <1239637734.24831.56.camel@localhost.localdomain> <49E35F92.6080400@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
on 13/04/2009 18:51 Andriy Gapon said the following: > on 13/04/2009 18:48 Sean Bruno said the following: >> The "self-test" never goes beyond "90%" complete? > > Yes, exactly. Even for the short one, which is supposed to complete in 1 > minute: Another data point. This disk was in an experimental 3-way mirror zpool, two other devices were Hitachi HDP725050GLA360 and WDC WD5000AAKS-00A7B2. Self-tests were scheduled at the same time for all 3 disks in smartd.conf. The Hitachi and Western Digital disks were able to complete the tests before start of a work day, but the Seagate disk was stuck at 90%. Now I removed it from the mirror (designated it as a hot-spare) and now the self-tests work as expected for it. Makes me wonder: what was that access pattern that prevented self-test progress of the Seagate disk but did not affect the other two. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49E46425.9070205>