Date: Mon, 12 Jul 2010 13:20:21 +0300 From: Mikolaj Golub <to.my.trociny@gmail.com> To: Dmitry Lunts <eingorn777@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: fsdb&smartctl&/var/log/messages Message-ID: <86aapxc87u.fsf@kopusha.home.net> In-Reply-To: <AANLkTinbWD0LUVig1OsaREeTtnfwukceIxzdzijRqeKy@mail.gmail.com> (Dmitry Lunts's message of "Mon, 12 Jul 2010 00:00:07 %2B0000") References: <AANLkTinbWD0LUVig1OsaREeTtnfwukceIxzdzijRqeKy@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Jul 2010 00:00:07 +0000 Dmitry Lunts wrote: DL> So, the puzzle is: DL> from one hand, pkgdb -uF, /var/log/messages, fsdb point to the same bad DL> sector (4007967) and filename DL> this sector belongs to DL> (and even cat /var/db/pkg/kdeutils-3.5.10_5/+CONTENTS returns Input/Output DL> error), DL> but low level reading of bad sector returns without a sign of error. >>From the other hand, smartctl long test performed immediately after low DL> level read test with dd DL> gives quite another number of bad sector (4007996) which in turn doesn't DL> belong to any file. DL> And what makes me completely lost is that DL> the tests in items 1)-10) were repeated two times and gave the same DL> results! DL> So where are 29 (4007996-4007967) sectors lost? As for me it looks like the following might has happened. Your filesystem block size is 16384 bytes. When reading +CONTENTS fs sent a request to the driver to read a block -- starting from 4007967 sector of 16384 / 512 = 32 sectors. For one of these sectors (4007996) disk returned error. The driver reported about the error printing the address of the first sector of failed request. -- Mikolaj Golub
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86aapxc87u.fsf>