diff options
| author | Bernd Schubert <bernd-schubert@gmx.de> | 2008-05-23 13:04:34 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-05-24 09:56:10 -0700 |
| commit | 6be9d4940134b36f9ed020aead36f831f19b49f1 (patch) | |
| tree | af74a03897cc8ee2ce4ae68a82a18f1d86d34f31 /drivers/atm/fore200e_firmware_copyright | |
| parent | 6bcfd601861cce45ca73ac1d714f1286b6b3f0d4 (diff) | |
md: md: raid5 rate limit error printk
Last night we had scsi problems and a hardware raid unit was offlined
during heavy i/o. While this happened we got for about 3 minutes a huge
number messages like these
Apr 12 03:36:07 pfs1n14 kernel: [197510.696595] raid5:md7: read error not correctable (sector 2993096568 on sdj2).
I guess the high error rate is responsible for not scheduling other events
- during this time the system was not pingable and in the end also other
devices run into scsi command timeouts causing problems on these unrelated
devices as well.
Signed-off-by: Bernd Schubert <bernd-schubert@gmx.de>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/atm/fore200e_firmware_copyright')
0 files changed, 0 insertions, 0 deletions