public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Thayne Harbaugh <tharbaugh@lnxi.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: buffer-list destroyed message
Date: Sat, 26 Apr 2003 11:25:52 +0200	[thread overview]
Message-ID: <20030426092552.GZ1012@suse.de> (raw)
In-Reply-To: <1051291883.1172.358.camel@tubarao>

On Fri, Apr 25 2003, Thayne Harbaugh wrote:
> I have a system that spits out the following error message:
> 
> scsi_end_request: buffer-list destroyed
> 
> It appears to come from drivers/scsi/scsi_lib.c: __scsi_end_request()
> 
> I can see that the code detects a mis-match in the number of sectors. 
> I'm wondering if anyone can enlighten me on how serious this problem is
> (the machine appears to work fine), what might be causing the problem,
> and how I might fix things.

The problem is very serious and is usually accompanied by data
corruption. So I suggest you check your filesystems! It depends on the
driver, though. I can say with absolute certainty that a healthy system
should _never_ see those messages.

> I searched the archives and only found one mail that seemed relevant:
> 
> http://marc.theaimsgroup.com/?l=linux-scsi&m=93303946423398&w=2
> 
> The comment for the MegaRAID refers to SMP and that the system appears
> to continue to function with no problems - two symptoms of the machine I
> have.  Yep, not a lot of information.

So almost certainly a megaraid bug. Is is easily reproduceable? Does it
occur with a UP kernel?

-- 
Jens Axboe


  reply	other threads:[~2003-04-26  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 17:31 buffer-list destroyed message Thayne Harbaugh
2003-04-26  9:25 ` Jens Axboe [this message]
2003-04-29 14:46   ` Thayne Harbaugh

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=20030426092552.GZ1012@suse.de \
    --to=axboe@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tharbaugh@lnxi.com \
    /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