From: "Jason H. Smith" <jhs@oes.co.th>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] snapshots on RAID5 blow up machine ("switching cache buffer size")
Date: Fri Jul 4 08:28:01 2003 [thread overview]
Message-ID: <200307021447.25888.jhs@oes.co.th> (raw)
In-Reply-To: <20030702073723.GC30882@questra.com>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1212 bytes --]
On Wednesday 02 July 2003 02:37 pm, Scott Mcdermott wrote:
> I've searched the archives and see that this is related to
> the filesystem using 4k blocks whereas snapshot IO uses 1k
> blocks, so RAID5 code gets confused, but I don't understand
> the internals of the filesystem to be able to say this is
> expected behavior.
>
> My questions are these:
>
> - Is this a RAID5 problem or an LVM problem, or both?
I ran into this a while ago and I eventually decided that, currently,
software RAID 5 and LVM are, to put it nicely, "incompatible" if you want
long-term snapshots. I'm no expert, but IMO, these days, the RAID5
subsystem should not assume i/o of equal chunk sizes, so it is md's
problem. IIRC, the 2.6 kernel is supposed to address this; but there's
not much you can do at the moment.
Somebody please correct me if I'm wrong.
> - Is this problem nonexistent on RAID1 backed or
> RAID10 backed VGs (especially the latter since I am
> contemplating a switch thereto)?
I believe that's correct, but please don't quote me. Testing this should
be simple enough.
--
Jason Smith
Open Enterprise Systems
Bangkok, Thailand
http://www.oes.co.th
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-04 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 2:38 [linux-lvm] snapshots on RAID5 blow up machine ("switching cache buffer size") Scott Mcdermott
2003-07-04 8:28 ` Jason H. Smith [this message]
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=200307021447.25888.jhs@oes.co.th \
--to=jhs@oes.co.th \
--cc=linux-lvm@sistina.com \
/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