From: "Simon Matter" <simon.matter@invoca.ch>
To: "Chris Adams" <cmadams@hiwaay.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File corruption on LVM2 on top of software RAID1
Date: Thu, 4 Aug 2005 14:38:39 +0200 (CEST) [thread overview]
Message-ID: <50089.213.188.237.106.1123159119.squirrel@localhost> (raw)
In-Reply-To: <20050803180835.GA1043467@hiwaay.net>
> Once upon a time, "Simon Matter" <simon.matter@invoca.ch> said:
>>In my tests I get corrupt files on LVM2 which is on top of software
>> raid1.
>>(This is a common setup even mentioned in the software RAID HOWTO and has
>>worked for me on RedHat 9 / kernel 2.4 for a long time now and it's my
>>favourite configuration). Now, I tested two different distributions,
>> three
>>kernels, three different filesystems and three different hardware. I can
>>always reproduce it with the following easy scripts:
>
> See:
>
> http://bugzilla.kernel.org/show_bug.cgi?id=4946
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=152162
>
> There's a one-line patch in there; see if that fixes the problem for
> you.
Hi Chris,
Thank you for your help, indeed this oneliner fixes the corruption. I have
tested with 2.6.12.3 + bio_clone fix and also built an updated RedHat EL4
kernel with the fix included. No corruption anymore.
This fix should be applied to most kernels shipped with the latest Linux
distributions. At least those products called Enterprise something should
hurry in the interest of their customers. Do you think this will happen
anytime soon?
--
Simon Matter
Invoca Systems
next prev parent reply other threads:[~2005-08-04 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.joi2dm7.1l4o8in@ifi.uio.no>
2005-08-03 18:08 ` File corruption on LVM2 on top of software RAID1 Chris Adams
2005-08-04 12:38 ` Simon Matter [this message]
2005-08-03 16:31 Simon Matter
2005-08-05 2:58 ` Andrew Morton
2005-08-05 2:58 ` Andrew Morton
2005-08-05 3:01 ` Andrew Morton
2005-08-05 7:56 ` Simon Matter
2005-08-05 8:02 ` Andrew Morton
2005-08-05 8:02 ` Andrew Morton
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=50089.213.188.237.106.1123159119.squirrel@localhost \
--to=simon.matter@invoca.ch \
--cc=cmadams@hiwaay.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.