From: malahal@us.ibm.com
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] re --corelog: does synchronization re-copy all data?
Date: Sun, 22 Feb 2009 23:11:32 -0800 [thread overview]
Message-ID: <20090223071132.GA9670@us.ibm.com> (raw)
In-Reply-To: <49A0A252.30803@smart.net>
Daniel B. [dsb@smart.net] wrote:
> In the LVM Administrator's Guide, at least the one at
> http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/LV_create.html ,
> it says:"
>
> LVM maintains a small log which it uses to keep track of which regions
> are in sync with the mirror or mirrors. By default, this log is kept
> on disk, which keeps it persistent across reboots. You can specify
> instead that this log be kept in memory with the --corelog argument;
> this eliminates the need for an extra log device, but it requires that
> the entire mirror be resynchronized at every reboot.
>
> Does that last sentence mean that _all_ the data is recopied, or just
> that all _regions_ are checked and not all the data necessarily has
> to be copied (perhaps only change regions have to be copied, but
> unchanged regions don't)?
Everything has to be re-copied because it doesn't know what is changed
as the "log" is kept in memory which is lost after a reboot.
> More generally, can LVM perform RAID1-style mirroring with only
> two disks (without having to re-copy everything each boot)
> (and, of course, being recoverable in case either disk fails)?
You should be able to force LVM to create a log device on one of your
two devices (--alloc anywhere)
Thanks, Malahal.
next prev parent reply other threads:[~2009-02-23 7:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 0:54 [linux-lvm] re --corelog: does synchronization re-copy all data? Daniel B.
2009-02-23 7:11 ` malahal [this message]
2009-02-25 4:50 ` Daniel B.
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=20090223071132.GA9670@us.ibm.com \
--to=malahal@us.ibm.com \
--cc=linux-lvm@redhat.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 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.