linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Michael Marxmeier <mike@msede.com>
To: paul@clubi.ie
Cc: jan@gondor.com, ak@suse.de, linux-lvm@msede.com
Subject: Re: [linux-lvm] LVM 0.8final for 2.2.15/2.2.16?
Date: Thu, 08 Jun 2000 2:22:14 MESZ	[thread overview]
Message-ID: <200006080022.CAA16063@e35.marxmeier.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0006080005180.26807-100000@fogarty.jakma.org>; from "Paul Jakma" at Jun 8, 100 12:18 (midnight)

> 
> On Wed, 7 Jun 2000, Jan Niehusmann wrote:
> 
> > The snapshot logic simply doesn't know what a filesystem is. It just
> > clones the block device.
> 
> this i knew.. :)
> 
> > So the fs may be in en inconsistent state, if you do the snapshot
> > while some write operation is in progress on the cloned
> > filesystem.
> 
> ok. so the solution is what? a call in the vfs to complete pending
> writes, and hold off on modifying any blocks?

IMHO when creating a snapshot LVM could simply sync all outstanding
buffers for the block device vialog block_fsync() (not sure if this
is already done -- Heinz care to comment?).
This should also take care of pending fs meta information thus
we should get a consistent state.

The question is how atomic this is? Since fsync_dev() currently
does a lock_kernel() is might even be sufficient.


Any reason why this is not suffiecient?

Michael

--
Michael Marxmeier           Marxmeier Software AG
E-Mail: mike@msede.com      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/

  reply	other threads:[~2020-11-27 16:17 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 [this message]
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
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=200006080022.CAA16063@e35.marxmeier.com \
    --to=mike@msede.com \
    --cc=ak@suse.de \
    --cc=jan@gondor.com \
    --cc=linux-lvm@msede.com \
    --cc=paul@clubi.ie \
    /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).