linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@Sistina.com>
To: Jos Visser <josv@osp.nl>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM 0.8final for 2.2.15/2.2.16?
Date: Fri, 9 Jun 2000 08:59:45 +0200	[thread overview]
Message-ID: <20000609085945.C6522@hmsysv.t-online.de> (raw)
In-Reply-To: <20000608143407.D9694@jadzia.josv.com>; from josv@osp.nl on Thu, Jun 08, 2000 at 02:34:07PM +0200

On Thu, Jun 08, 2000 at 02:34:07PM +0200, Jos Visser wrote:
> And thus it came to pass that Paul Jakma wrote:
> (on Thu, Jun 08, 2000 at 12:49:53PM +0100 to be exact)
> 
> > On Thu, 8 Jun 2000, Andi Kleen wrote:
> > 
> > > consider a database that uses user space journaling using fsync:
> > > to make its disk files consistent after the snapshot it requires
> > > both the log write and the data write. When one is missing the
> > > log needs to be replayed, which requires writes.
> > 
> > but doesn't the call to block_fsync that Heinz confirmed exists cover
> > this?
> > 
> > nothing can cover the case where app data consistency depends on a future
> > write(). But that's the app's problem, and anyway a good database should
> > be consistent/recover itself if it's died between write(?)'s. right?
> > 
> > (in which case lvm snapshot is perfectly suitable for backing up
> > databases..)
> 
> Most databases want you to store their log and data spaces in different 
> (logical) volumes.

Exactly.

That's why i'll implement atomic activation off multiple snapshot.

The idea is:

 - prepare multiple _inactive_ snapshots
 - activate them afterwards at once

Heinz

> To create a consistent image you would want to be
> able to snapshot multiple logical volumes atomically in one operation.
> HP's LVM supports this through the "multiple atomical lvsplit"
> feature (as of HP-UX 10 if memory serves me right).
> 
> ++Jos
> 
> -- 
> The InSANE quiz master is always right!
> (or was it the other way round? :-)

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                Sistina Software Inc.
Senior Consultant/Developer                      Bartningstr. 12
                                                 64289 Darmstadt
                                                 Germany
Mauelshgen@Sistina.com                           +49 6151 710386
                                                      FAX 710396
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2000-06-09  6:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000607100145.A6300@gondor.com>
2000-06-07 23:18 ` [linux-lvm] LVM 0.8final for 2.2.15/2.2.16? Paul Jakma
2020-11-27 16:17   ` Michael Marxmeier
2000-06-08  0:47     ` Paul Jakma
2000-06-08  8:23       ` Jos Visser
2000-06-08  8:34         ` Andi Kleen
2000-06-08 11:49           ` Paul Jakma
2000-06-08 12:34             ` Jos Visser
2000-06-09  6:59               ` Heinz J. Mauelshagen [this message]
2000-06-08  7:52     ` Heinz J. Mauelshagen
2000-06-06  9:51 Paul Jakma
2000-06-06 14:42 ` Andi Kleen
2000-06-06 22:30   ` Paul Jakma
2000-06-06 22:46     ` Andi Kleen
2000-06-07  0:03       ` Paul Jakma
2000-06-07  0:09       ` Paul Jakma
2000-06-12 13:20   ` Paul Jakma
2000-06-12 19:53     ` Jay Weber

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=20000609085945.C6522@hmsysv.t-online.de \
    --to=mauelshagen@sistina.com \
    --cc=josv@osp.nl \
    --cc=linux-lvm@msede.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;
as well as URLs for NNTP newsgroup(s).