public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Jeremy Jackson <jerj@coplanar.net>
Cc: Alvaro Figueroa <fede2@fuerzag.ulatina.ac.cr>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Adding snapshot capability to Linux
Date: Tue, 23 Apr 2002 14:22:29 -0600	[thread overview]
Message-ID: <20020423202229.GV3017@turbolinux.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0204231041010.8087-100000@weyl.math.psu.edu> <007f01c1eaf9$a63aeb40$7e0aa8c0@bridge>

On Apr 23, 2002  12:04 -0700, Jeremy Jackson wrote:
> This type of snapshot is very desirable.  It can be done by remounting
> the fs ro, then taking EVMS or LVM snapshot, but you can't do that with open
> files.
> 
> For a journaling fs cooperation with snapshot while rw, the fs must accept
> a snapshot request, pause in flight IO, sync all pending buffers, flush
> it's log, mark fs clean (almost like umount) continue the block dev
> snapshot, mark fs in use, resume io.
> 
> How about having all FS export methods for this, and VFS export to
> userspace.

Please do your homework.  What you describe already exists.  The VFS
methods (write_super_lockfs and unlockfs) are already there, and all
of the journaling filesystems support this.  The LVM and EVMS code has
patches to call these VFS methods.  For some reason the VFS-lock patch
has not yet been included in the kernel, but it should be.

As for filesystem-level snapshots (i.e. blocking write requests at the
VFS layer and doing COW) that is what snapfs (previously mentioned) does.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-04-23 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 10:58 Adding snapshot capability to Linux Libor Vaněk
2002-04-22 12:06 ` Peter Wächtler
2002-04-22 12:19   ` Libor Vanek
2002-04-22 12:42     ` Jasper Spaans
2002-04-22 15:02       ` Alvaro Figueroa
2002-04-23  5:36   ` rpm
2002-04-23 14:30     ` Alvaro Figueroa
2002-04-23 14:45       ` Alexander Viro
2002-04-23 14:58         ` Xavier Bestel
2002-04-23 18:48         ` Libor Vanek
2002-04-23 19:04         ` Jeremy Jackson
2002-04-23 20:22           ` Andreas Dilger [this message]
2002-04-22 17:07 ` Andreas Dilger
2002-04-22 17:41   ` Kent Borg
2002-04-22 18:39     ` Andreas Dilger
2002-04-22 18:19   ` Sandy Harris

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=20020423202229.GV3017@turbolinux.com \
    --to=adilger@clusterfs.com \
    --cc=fede2@fuerzag.ulatina.ac.cr \
    --cc=jerj@coplanar.net \
    --cc=linux-kernel@vger.kernel.org \
    /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