Thanks for trying to help me!
My problem is (looks like) solved.
It was a kernel problem. (I think...)
When I switch to 2.6.13-rc6 (from rc3), the problem is gone!
It is very interesting!
I use SWRAID to distribute equal load to nodes.
(raid0 chunksize 32k)
In my system with 2.6.13-rc3 the "node-
- Original Message -
From: "Neil Brown" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc:
Sent: Thursday, August 18, 2005 6:34 AM
Subject: Re: Found a new bug!
> On Monday August 15, [EMAIL PROTECTED] wrote:
> > Thanks, I will test it, when I can...
> >
> > In this moment, my system is an
On Thu, 2005-08-18 at 12:24 +0200, Lars Marowsky-Bree wrote:
> On 2005-08-18T15:28:41, Neil Brown <[EMAIL PROTECTED]> wrote:
> > To handle read failures, I would like the first step to be to re-write
> > the failed block. I believe most (all?) drives will relocate the
> > block if a write cannot
On Thu, 2005-08-18 at 15:28 +1000, Neil Brown wrote:
> However I think I would like to do it a little bit differently.
thanks for your reply, interesting ideas!
> If we want to mirror a single drive in a raid5 array, I would really
> like to do that using the raid1 personality.
> e.g.
>suspe
Neil Brown wrote:
> Thanks for this. There are definitely some good ideas here.
> However I think I would like to do it a little bit differently.
>
> If we want to mirror a single drive in a raid5 array, I would really
> like to do that using the raid1 personality.
> e.g.
>suspend io
>rem
On 2005-08-18T15:28:41, Neil Brown <[EMAIL PROTECTED]> wrote:
> If we want to mirror a single drive in a raid5 array, I would really
> like to do that using the raid1 personality.
> e.g.
>suspend io
>remove the drive
>build a raid1 (with no superblock) using the drive.
>add that ba
