| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4D1633F2.3040109@jcz.nl> Date: Sat, 25 Dec 2010 19:12:02 +0100 From: Jaap Crezee <jaap@....nl> To: linux-kernel@...r.kernel.org Subject: Re: Slow disks. On 12/25/10 13:19, Mikael Abrahamsson wrote: > On Sat, 25 Dec 2010, Rogier Wolff wrote: > Read errors will use parity drive and be re-written by the md layer. Can you show us *that* code? I don't recall seeing this behaviour.... Just one read error and "bang". Or does the kernel not report the first few read errors and just continues without telling us? I don't like that. With a normal disk without raid I would have had some log telling me the disk got bad? Jaap -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists