All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Vermeer <koen@vermeer.tv>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Mirrored LV
Date: Tue, 16 Sep 2008 23:12:45 +0200	[thread overview]
Message-ID: <1221599565.6037.82.camel@localhost> (raw)
In-Reply-To: <20080916204241.GA9810@us.ibm.com>

Op dinsdag 16-09-2008 om 13:42 uur [tijdzone -0700], schreef
malahal@us.ibm.com:
> The log records what regions of your master device are in sync with your
> other mirror device. It is used to synchronize the failed regions from
> the master to your other device when your 'other device' comes back to
> life. This should work whether your log device is in memory or on a PV
> by itself as long as you don't de-activate or restart your machine. The
> log data on a PV can be useful for reboots.

I had written a lot of text with extra questions, but it seems I just
don't get it - yet.

If I understand you correctly, you're statements are about when the
'other device' is failing. Is this right? If so, then the log should
normally show that everything is synced. In that case, it's not of much
use in normal operation. Now, when one disk fails, I need to replace it,
and rebuild the mirror. So again, I don't need it, because I have to
copy everything anyway. Only when a disk is temporarily gone, it may be
of some use. Does this make sense?

Best,
Koen

  reply	other threads:[~2008-09-16 21:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 19:20 [linux-lvm] Mirrored LV Koen Vermeer
2008-09-16 19:56 ` Georges Giralt
2008-09-16 20:20   ` Koen Vermeer
2008-09-16 20:42 ` malahal
2008-09-16 21:12   ` Koen Vermeer [this message]
2008-09-16 21:57     ` malahal
2008-09-17  7:36       ` Koen Vermeer
2008-09-19 15:06       ` Koen Vermeer
2008-09-19 17:31         ` malahal
2008-09-19 22:01           ` Koen Vermeer
2008-09-20  3:39             ` Jonathan Brassow
2008-09-22 21:21               ` malahal
2008-09-23  8:41               ` Koen Vermeer
2008-09-16 23:01     ` Larry Dickson
2008-09-17  1:22       ` malahal

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=1221599565.6037.82.camel@localhost \
    --to=koen@vermeer.tv \
    --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.