linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Chris Mason <chris.mason@oracle.com>
Cc: "Xin Zhao" <uszhaoxin@gmail.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how do versioning filesystems take snapshot of opened files?
Date: Wed, 4 Jul 2007 08:02:47 +1000	[thread overview]
Message-ID: <18058.51079.350424.273688@notabene.brown> (raw)
In-Reply-To: message from Chris Mason on Tuesday July 3

On Tuesday July 3, chris.mason@oracle.com wrote:
> 
> Getting a snapshot that is useful with respect to application data
> requires help from the application.

Certainly.

>                                      The app needs to be shutdown or
> paused prior to the snapshot and then started up again after the
> snapshot is taken.

Alternately, the app needs to be able to cope with unexpected system
shutdown (aka crash) and the same ability will allow it to cope with
an atomic snapshot.  It may be able to recover more efficiently from
an expected shutdown, so being able to tell the app about an impending
snapshot is probably a good idea, but it should be advisory only.

NeilBrown

      parent reply	other threads:[~2007-07-03 22:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03  5:28 how do versioning filesystems take snapshot of opened files? Xin Zhao
     [not found] ` <778391c50707022236v5157a933qea1994cf4cbce879@mail.gmail.com>
2007-07-03  5:44   ` Xin Zhao
2007-07-03 13:09 ` Chris Mason
2007-07-03 16:12   ` Xin Zhao
2007-07-03 16:35     ` Bryan Henderson
2007-07-03 16:24   ` Bryan Henderson
2007-07-03 16:31     ` Xin Zhao
2007-07-03 17:04       ` Chris Mason
2007-07-03 17:15         ` Xin Zhao
2007-07-03 17:38           ` Chris Mason
2007-07-03 21:06             ` Bryan Henderson
2007-07-03 21:17               ` Xin Zhao
2007-07-03 22:02   ` Neil Brown [this message]

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=18058.51079.350424.273688@notabene.brown \
    --to=neilb@suse.de \
    --cc=chris.mason@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uszhaoxin@gmail.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).