linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: No syncing after crash. Is this a software raid bug?
Date: Fri, 3 Mar 2006 16:10:51 +0100	[thread overview]
Message-ID: <du9m9r$ddi$1@sea.gmane.org> (raw)
In-Reply-To: 20060303144824.GA15672@hactar.lan

Kasper Dupont <87385155133026632046@expires.04.sep.2006.kasperd.net> 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


  reply	other threads:[~2006-03-03 15:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 12:44 No syncing after crash. Is this a software raid bug? Kasper Dupont
2006-03-01 13:58 ` Luca Berra
2006-03-01 16:24 ` Mike Hardy
2006-03-01 21:56 ` Kasper Dupont
2006-03-02 13:48   ` Mario 'BitKoenig' Holbe
2006-03-03 13:39     ` Heinz Mauelshagen
2006-03-03 14:30       ` Mario 'BitKoenig' Holbe
2006-03-03 22:26         ` Heinz Mauelshagen
2006-03-03 23:01           ` Mario 'BitKoenig' Holbe
2006-03-04  9:01             ` Heinz Mauelshagen
2006-03-04 10:10               ` Mario 'BitKoenig' Holbe
2006-03-03  7:30   ` Kasper Dupont
2006-03-03 12:03     ` Mario 'BitKoenig' Holbe
2006-03-03 12:38       ` Mario 'BitKoenig' Holbe
2006-03-03 14:48     ` Kasper Dupont
2006-03-03 15:10       ` Mario 'BitKoenig' Holbe [this message]
2006-03-04 13:16       ` Kasper Dupont
2006-03-04 13:38         ` Mario 'BitKoenig' Holbe
2006-03-04 19:50         ` Kasper Dupont
2006-03-07 10:47         ` Heinz Mauelshagen
2006-03-07 11:18           ` Kasper Dupont
2006-03-07 12:12             ` Heinz Mauelshagen
2006-03-10  7:43             ` Heinz Mauelshagen
2006-03-10  7:49               ` Kasper Dupont
2006-03-16  7:24                 ` Kasper Dupont
2006-03-16 14:04                   ` Heinz Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='du9m9r$ddi$1@sea.gmane.org' \
    --to=mario.holbe@tu-ilmenau.de \
    --cc=linux-raid@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).