From: "Jeremy Jackson" <jerj@coplanar.net>
To: "Alexander Viro" <viro@math.psu.edu>,
"Alvaro Figueroa" <fede2@fuerzag.ulatina.ac.cr>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Subject: Re: Adding snapshot capability to Linux
Date: Tue, 23 Apr 2002 12:04:00 -0700 [thread overview]
Message-ID: <007f01c1eaf9$a63aeb40$7e0aa8c0@bridge> (raw)
In-Reply-To: <Pine.GSO.4.21.0204231041010.8087-100000@weyl.math.psu.edu>
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 file level COW (not block level),
I wonder if DMAPI available with SGI's XFS (IRIX & Linux)
provides the VFS like hooks that could be used to build such a system.
Perhaps it could be implemented on other FS or generically in VFS. The nice
thing is it's a standard and already has a working implementation (XFS)
from dmapi man page (oss.sgi.com XFS project):
DESCRIPTION
dmi is a system interface used to implement the interface defined in the
X/Open document: Systems Management: Data Storage Management (XDSM) API
dated February 1997. This interface is made available on Silicon Graphics
systems by means of the libdm library.
That spec is available from opengroup.org to view online for free.
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.
Not so bad for journaling fs? Non journaling would be easier, I think.
How about having all FS export methods for this, and VFS export to
userspace.
The holy grail is to generically support consistent online snapshot backup,
no?
Jeremy
----- Original Message -----
From: "Alexander Viro" <viro@math.psu.edu>
To: "Alvaro Figueroa" <fede2@fuerzag.ulatina.ac.cr>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Sent: Tuesday, April 23, 2002 7:45 AM
Subject: Re: Adding snapshot capability to Linux
>
>
> On 23 Apr 2002, Alvaro Figueroa wrote:
>
> > > Instead of changing VFS you can probably make a generic stackable FS
module
> > > .....that can stack on top of the physical filesystems and happily
take
> > > snapshots at "FS" level :) ! and you can use the FIST to create a
basic
> > > stackable FS and then modify it to take care of snapshoting !
> >
> > Since this solution doens't solve Lisbor's request of using it on smb
> > filesystems, well, you could as well save up all of the programmer
> > cycles and use EVMS.
> >
> > It has a pluggin for treating normal partitions as EVMS objets, so you
> > don't need to translate them or so; and with EVMS you can even use RW
> > snapshots.
>
> You _can't_ get consistent snapshots without cooperation from fs. LVM,
> EVMS, whatever. Only filesystem knows what IO needs to be pushed to
> make what we have on device consistent and what IO needs to be held
> back. Neither VFS nor device driver do not and can not have such
> knowledge - it depends both on fs layout and on implementation details.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-04-23 19:05 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 [this message]
2002-04-23 20:22 ` Andreas Dilger
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='007f01c1eaf9$a63aeb40$7e0aa8c0@bridge' \
--to=jerj@coplanar.net \
--cc=fede2@fuerzag.ulatina.ac.cr \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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