From: "Nick Evgeniev" <nick@octet.com>
To: "Neil Brown" <neilb@cse.unsw.edu.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-pre8-ac5 ide & raid0 bugs
Date: Wed, 29 May 2002 16:56:42 +0400 [thread overview]
Message-ID: <000901c20710$486c3f40$baefb0d4@nick> (raw)
In-Reply-To: <000901c206f0$cfd42620$baefb0d4@nick> <15604.45243.291277.197140@notabene.cse.unsw.edu.au>
Hi,
Yes, I'm using lvm 1.1rc1 on top of raid0. Hardware details:
dual piii box on via Apollo pro133 chipset (via694)
two ATA-100 drives (FUJITSU MPG3204AH) attached to on-board controller
(PROMISE 20265)
& one drive attached to VIA controller. RAID0 is made on top of first two
drives.
1. I don't have any problem with drive attached to via controller (in DMA33
mode)
2. The only problem that I have is with UDMA100 drives attached to promise
controller... Also I have to notice that log messages about ide errors are
related to drive that has no errors (according to smartctl -l, while another
drive has a few records in its log)
3. I had no problems with ide with 2.4.7 kernel for a months...
> > >-----------------------------
> > But now I've got even more bugs in log like:
> > >-----------------------------
> > May 29 11:28:06 vzhik kernel: raid0_make_request bug: can't convert
block
> > across chunks or bigger than 16k 37713311 4
> > May 29 11:28:06 vzhik kernel: raid0_make_request bug: can't convert
block
> > across chunks or bigger than 16k 37713343 4
>
> This is a request for a 4K block that is not 4K aligned... this
> shouldn't happen.
> Are you using LVM or something to partition the raid0 array?
> ... though I seem to recall that LVM always partitions in multiples of
> 4K so that shouldn't be a problem.
next prev parent reply other threads:[~2002-05-29 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 9:11 2.4.19-pre8-ac5 ide & raid0 bugs Nick Evgeniev
2002-05-29 10:43 ` Neil Brown
2002-05-29 12:56 ` Nick Evgeniev [this message]
2002-06-04 18:41 ` Bill Davidsen
2002-06-05 10:20 ` Nick Evgeniev
2002-06-08 20:06 ` Andre Hedrick
2002-06-10 20:57 ` Bill Davidsen
2002-06-11 4:18 ` Andre Hedrick
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='000901c20710$486c3f40$baefb0d4@nick' \
--to=nick@octet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=nick@octet.spb.ru \
/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