Re: md raid5 blocked in get_active_stripe after disk failure

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

 



* NeilBrown (neilb@xxxxxxx) wrote:
> If this is easily reproducible (which I think you suggested it is), I would
> put a printk in raid5_end_read_request where it sets "retry = 1" to report
> "trying to fix a failed read".
>
> If you then get a hang but don't get that message, it is a device driver
> problem.  If you do get that message it is probably an md/raid5 problem.

Thanks for the quick reply.

At the time it was easily reproducible (after rebooting as soon as the
nfs clients retried their requests).  Unfortunately, I had to remove the
disk from the array, and will not be able to test the above until next
month.

Kind regards,

..david
--
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


[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