Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Subject: Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
From: NeilBrown <neilb@xxxxxxx>
Date: Tue, 7 Jan 2014 09:46:19 +1100
Cc: linux-raid <linux-raid@xxxxxxxxxxxxxxx>
In-reply-to: <CAGRgLy5wy54cCiXkuwTTqUugaKCukUgUNq7vzf75TV0=f2+2bA@mail.gmail.com>

On Mon, 6 Jan 2014 17:12:10 +0200 Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
wrote:

> Thanks, Neil!
> The test that was failing, passes now.
> 
> Thanks for the patch,
> Alex.
> 
> 

Thanks for testing.  I'll send the fix upstream shortly.

NeilBrown

Attachment: signature.asc
Description: PGP signature

References:
- raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  - From: Alexander Lyakas
- Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  - From: NeilBrown
- Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  - From: Alexander Lyakas

Prev by Date: Re: [RFC v2 0/2] New RAID library supporting up to six parities
Next by Date: Re: Why 4k native drives haven't arrived
Previous by thread: Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
Next by thread: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID Wiki] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux Block] [Linux IDE] [Linux SCSI] [Linux Hams] [Device Mapper] [Device Mapper Cryptographics] [Kernel] [Linux Admin] [Linux Net] [GFS] [RPM] [git] [Yosemite Forum]

Powered by Linux