From: Kasper Dupont <70006427576745453539@expires.04.sep.2006.kasperd.net>
To: linux-raid@vger.kernel.org
Subject: Re: No syncing after crash. Is this a software raid bug?
Date: Fri, 3 Mar 2006 08:30:18 +0100 [thread overview]
Message-ID: <20060303073016.GA662@hactar.lan> (raw)
In-Reply-To: <20060301215641.GA27042@hactar.lan>
> Do you have write-cache enabled on the mirrors?
How do I find out about that?
> Sometimes I have differences between RAID1 mirrors in 2.4, too.
I have not experienced this with 2.4. However the 2.4 and 2.6
machines are not exactly the same hardware. But AFAIR they both
use Promise controllers and Seagate disks.
> Even with clean shutdown or reboot sequences.
Actually I think some of the differences on the swap device have
happened on clean shutdowns.
> However, in my case, it turns out
> that this always affects areas which are "free" on the filesystem layer.
Does the raid layer have any way to know if they are free and
treat them differently?
> that I have md5sums of all my files which don't show up any
> differences when I either copy the non-zero content over the zeros or the
> other way around.
OK. Then it may very well be free areas. (Or perhaps journal)
> Especially I have never experienced such "normal" differences on my swap
> RAID1 mirrors.
So far I have only seen it happen on swap. I thought that might
be because that machine swaps a lot.
(A copy of any replies to my email address will be appreciated).
--
Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
#define _(_)"d.%.4s%."_"2s" /* This is my new email address */
char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,6,_+2,_+7,_+6);
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-03-03 7:30 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 [this message]
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
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=20060303073016.GA662@hactar.lan \
--to=70006427576745453539@expires.04.sep.2006.kasperd.net \
--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).