From: Jens Axboe <axboe@suse.de>
To: Paul Larson <plars@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Scsi problems in 2.5.1-pre9
Date: Tue, 11 Dec 2001 17:19:59 +0100 [thread overview]
Message-ID: <20011211161959.GA13498@suse.de> (raw)
In-Reply-To: <1008065277.25964.5.camel@plars.austin.ibm.com> <20011211160543.GZ13498@suse.de>
In-Reply-To: <20011211160543.GZ13498@suse.de>
On Tue, Dec 11 2001, Jens Axboe wrote:
> On Tue, Dec 11 2001, Paul Larson wrote:
> > My hardware is a dual proc PII-300. I was running LTP runalltests.sh
> > and it was on one of the growfiles tests when this problem occurred.
> > The test hung, and I couldn't telnet into the machine or login to it,
> > but I could switch between VC's. On the console, I had screenfulls of
> > errors like this:
> >
> > Incorrect number of segments after building list
> > counted 11, received 7
> > req nr_sec 1024, cur_nr_sec 8
> > Incorrect number of segments after building list
> > counted 14, received 10
> > req nr_sec 1024, cur_nr_sec 8
> > Incorrect number of segments after building list
> > counted 13, received 11
> > req nr_sec 584, cur_nr_sec 8
> > Incorrect number of segments after building list
> > counted 2, received 1
> > req nr_sec 16, cur_nr_sec 8
> > Incorrect number of segments after building list
> > counted 2, received 1
> > req nr_sec 16, cur_nr_sec 8
> > (scsi0:A:5:0): Locking max tag count at 64
> >
> > After doing a hard reboot ext2 made me do a manual fsck, but it seems ok
> > now. I was not able to produce this error in 2.5.1-pre8.
>
> Please don't tell me what hardware you have :-)
It seems to affect all SCSI drivers with CLUSTERING enabled. Don't worry
about data consistency btw, the above is a warning only (the right
segment count is used).
--
Jens Axboe
next prev parent reply other threads:[~2001-12-11 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 10:07 Scsi problems in 2.5.1-pre9 Paul Larson
2001-12-11 16:05 ` Jens Axboe
2001-12-11 16:19 ` Jens Axboe [this message]
2001-12-11 10:34 ` Paul Larson
2001-12-11 16:30 ` Jens Axboe
2001-12-11 16:47 ` Jens Axboe
2001-12-11 16:54 ` Jens Axboe
2001-12-11 21:28 ` Anton Blanchard
2001-12-11 22:04 ` David S. Miller
2001-12-11 22:17 ` Anton Blanchard
2001-12-11 22:27 ` David S. Miller
2001-12-12 9:02 ` Jens Axboe
2001-12-12 9:15 ` David S. Miller
2001-12-12 9:21 ` Jens Axboe
2001-12-12 9:31 ` David S. Miller
2001-12-12 9:32 ` Jens Axboe
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=20011211161959.GA13498@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.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