Bernd Schubert wrote:
On Thursday 11 October 2007 16:19:37 Jeff Garzik wrote:
1) Just about the only valid optimization is to ensure that only the
write path must be limited to small chunks, not both read- and
write-paths. Tejun had a patch to do this a long time ago, but it's an
open question whether the large amount of code is worth it for a rare
combination.
How large? This patch is rather small? Where can I find it?
http://home-tj.org/wiki/index.php/Sil_m15w
The problem came up, when 200GB drives were replaced by *newer* 250GB drives
(well maybe not the newest, no idea were they came from).
Anyway, I'm testing for more than 24h already and didn't observe any data
corruption as without the patch. I know this is only an obersavation and no
definite prove...
Also, this is with 3114, maybe this chip behaves a bit different than 3112?
3114 + new SATA drive is definitely a new one for us.
It would help to (a) use the latest kernel, (b) post your .config with
the latest kernel, (c) post lspci booted into latest kernel, and (d)
post dmesg booted into latest kernel.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
