Hi,
Is there any indication that can tell I am hitting this particular issue?
I think I hit something similar to that once, IOs were hang within a
raid5 and not returning. I issues w > sysrq-trigger and also have most
of the procfs/<pid> info, so is there something I can look at to
confirm?
On Thu, Jul 12, 2012 at 7:14 AM, NeilBrown <neilb@xxxxxxx> wrote:
> On Wed, 11 Jul 2012 15:07:40 -0700 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>
>> On Mon, Jul 09, 2012 at 02:02:30PM +1000, NeilBrown wrote:
>> >
>> > Hi Mr Stable,
>> >
>> > please apply patch
>> >
>> > commit fab363b5ff502d1b39ddcfec04271f5858d9f26e
>> > Author: Shaohua Li <shli@xxxxxxxxxx>
>> > Date: Tue Jul 3 15:57:19 2012 +1000
>> >
>> > raid5: delayed stripe fix
>> >
>> >
>> > to 3.4.y and 3.2.y.
>> >
>> > It fixes a deadlock in RAID5 which can cause all IO to hang.
>> > It has been demonstrated to fix a real-life problem (the race is not
>> > theoretical).
>>
>> Is it also needed for 3.0.x? It seems to apply there just fine.
>
> Yes it is. Don't know why I missed that.
> I see you've already included it - thanks.
>
> NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[ATA RAID]
[Linux SCSI Target Infrastructure]
[Managing RAID on Linux]
[Linux IDE]
[Linux SCSI]
[Linux Hams]
[Device-Mapper]
[Kernel]
[Linux Books]
[Linux Admin]
[Linux Net]
[GFS]
[RPM]
[git]
[Photos]
[Yosemite Photos]
[Yosemite News]
[AMD 64]
[Linux Networking]