public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Flory <sflory@rackable.com>
To: "tester7 A." <benew666@hotmail.com>
Cc: linux-kernel@vger.kernel.org, andrea@suse.de
Subject: Re: Hangs with SW RAID5 and 2l.4.21-pre3aa1 patch
Date: Tue, 28 Jan 2003 13:53:59 -0800	[thread overview]
Message-ID: <3E36FBF7.9080809@rackable.com> (raw)
In-Reply-To: F85MjT3XOYR00HgHKkR00003b05@hotmail.com

tester7 A. wrote:

>
> Motherboard: Intel SDS2
> CPU: P-III 1.4
> RAM: 1024MB
> IDE Controller: 3Ware 7500-8
>
> I am trying to test S/W Raid5 with 2.4.21-pre3aa1 patch
> After making the raidtab and doing 'mkraid' and mount xfs FS on /dev/md1,
> it was keeep showing something about 'buffer size changed from 4096 
> --> 512' and back and forth and hangs.
> After reset, it would not boot due to Raid failure.
>
> After booting with 2.4.20 kernel and remove the raidtab and boot to 
> the 2.4.21-pre3aa1 again and repeat the same, 'mkraid' halts and ps 
> -aux shows raid5d and raid5syncd is in RW and DW, respectively.


  Does a 2.4.21-pre3 kernel work?

>
> Is it known bug in 2.4.21-pre33aa1 kernel?
>
>

  I've seen this as well when I attempted to upgrade a system with 2 
raid0, and 1 raid1 devices.  It was a Intel se7500wv, 4G memory, and two 
3ware  7500-8.  The system works just fine with old aa's, and redhat's 
2.4.18-19 kernel.  I didn't have much time to spend with it, and I was 
waiting to test 2.4.21-pre3 before reporting the bug.

-- 
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory  <sflory@rackable.com>




      reply	other threads:[~2003-01-28 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 17:42 Hangs with SW RAID5 and 2l.4.21-pre3aa1 patch tester7 A.
2003-01-28 21:53 ` Samuel Flory [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=3E36FBF7.9080809@rackable.com \
    --to=sflory@rackable.com \
    --cc=andrea@suse.de \
    --cc=benew666@hotmail.com \
    --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