How often does the log get written in normal use, and how big does it get, how fast? If it's a low-bandwidth sort of thing, could it go to some kind of solid-state storage?
Larry Dickson
Cutting Edge Networked Storage
On 9/16/08, Koen Vermeer <koen@vermeer.tv> wrote:
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
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
