From: Andrew Morton <akpm@zip.com.au>
To: Jens Axboe <axboe@suse.de>
Cc: Andre Hedrick <andre@linux-ide.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: death by ATA
Date: Fri, 16 Nov 2001 17:21:25 -0800 [thread overview]
Message-ID: <3BF5BB95.77B96DAF@zip.com.au> (raw)
In-Reply-To: <3BF41608.DF8C7068@zip.com.au>, <3BF41608.DF8C7068@zip.com.au> <20011116234558.D11826@suse.de>
Jens Axboe wrote:
>
> On Thu, Nov 15 2001, Andrew Morton wrote:
> > What does "end-request: buffer-list destroyed" mean?
>
> It means that the request was not sane anymore, or specifically that
> clustered number of sectors was set to lower value than current number
> of sectors (which isn't valid, of course). The buffer-list destroyed
> comment tells you that this corruption is most likely due to the
> buffer_head list on the request having been corrupted -- which in turn
> probably means that someone seriously screwed this request.
>
> hda8: bad access: block=5296, count=-2
> end_request: I/O error, dev 03:08 (hda), sector 5296
> hda8: bad access: block=5298, count=-4
> end_request: I/O error, dev 03:08 (hda), sector 5298
> hda8: bad access: block=5300, count=-6
> end_request: I/O error, dev 03:08 (hda), sector 5300
>
> This errors would seem to backup that theory :-)
'k, thanks.
> Is this an SMP board? Also, is
Uniprocessor VIA C3, running 2.4.15-pre4. The controller is a
VT8231. Running at UDMA100.
> end_request: buffer-list destroyed
>
> the very first error message?
Yes, it is.
It is reproducible after around three few hours. Exactly the
same.
-
prev parent reply other threads:[~2001-11-17 1:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 19:22 death by ATA Andrew Morton
2001-11-16 22:45 ` Jens Axboe
2001-11-17 1:21 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BF5BB95.77B96DAF@zip.com.au \
--to=akpm@zip.com.au \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox