Re: No syncing after crash. Is this a software raid bug?

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

 



Kasper Dupont <87385155133026632046@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> On the 2.6 system where I see the differences between mirrors
> /proc/ide/hde/settings:wcache                  1

write cache enabled.
Btw... don't disable it on a production system without previously
thinking about it :) Disabling write cache leads to massive performance
decrease on heavy simultaneous I/O... On a system with (IMHO not heavy
but significant) simultaneous I/O I got 35MB/s write speed on dd with
write cache enabled and it shrunk down to 9MB/s with write cache
disabled - while load grew up from ~0 to ~8.

> On a 2.4 system where I see no differences between mirrors I
> /proc/ide/hde/settings:wcache                  0               0               1               rw
> So how should I interpret this?

As I said - on 2.4 write cache reporting through /proc is broken: it
always reports disabled write cache, while it is not necessarily
disabled. Use hdparm -I instead (big I, not small i).


regards
   Mario
-- 
"Why are we hiding from the police, daddy?"      | J. E. Guenther
"Because we use SuSE son, they use SYSVR4."      | de.alt.sysadmin.recovery

-
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