Date: Wed, 3 Sep 2003 21:27:13 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> Cc: freebsd-fs@freebsd.org Subject: Re: very slow fsck on bad disk Message-ID: <20030903212556.C88884@carver.gumbysoft.com> In-Reply-To: <wpwucpsgf9.fsf@heho.snv.jussieu.fr> References: <wpwucpsgf9.fsf@heho.snv.jussieu.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Sep 2003, Arno J. Klaassen wrote: > fsck_ffs -y -b 32 /dev/ad2s1e > > I started this .... "last saturday" and it's still running. > When I look at the dmesg or /var/log messages, my eye > got triggered by this : > > > Sep 3 23:02:27 tabarnac kernel: ad2: hard error cmd=read fsbn 16405947 status=59 error=40 > Sep 3 23:02:32 tabarnac kernel: ad2: hard error cmd=read fsbn 16405948 status=59 error=40 [... disk errors ...] > Am i wrong or does this smell like "each surface error is queued > for syslog, syslog print is triggered every 5 seconds, progress > on fsck ata-disks is hold until next syslog message is printed" It isn't trying to log to the defective volume, is it? And the delays are probably the disk resetting. Errors and timeouts take a while. I would say you are the proud owner of a new doorstop. :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030903212556.C88884>