All of lore.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <qiyong@fc-cn.com>
To: Block Device <blockdevice@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A standard snapshot notification framework in Linux ?
Date: Tue, 15 Nov 2005 16:24:08 +0800	[thread overview]
Message-ID: <20051115082408.GA3249@localhost.localdomain> (raw)
In-Reply-To: <64c763540511142345g4ca0b184y28962dae494f22b4@mail.gmail.com>

On Tue, Nov 15, 2005 at 01:15:54PM +0530, Block Device wrote:
> Hi,
> 
>    does the linux kernel provide a mechanism whereby applications can
> register themselves
> to be notified when a snapshot is being taken of the volume they might
> be writing to.
> 
>    If there is no such framework then how do backup applications
> guarantee ( application level ) consistency. I have seen freeze_bdev

call sync and mount read-only, or go down to init 1.

	Coywolf

> and friends which work for file systems and how the device mapper uses
> them. But when it comes to application level consistency, a mechanism
> is required to give the application a chance to flush &  quiesce its
> writes so that the backup taken will be consistent for the application
> also. Windows has the VSS ( Volume Shadow Service ) which provides an
> elaborate framework for this. Is anyone working on something similar
> for Linux and if not why is it not such a worthwhile idea ?
> 
> Regards
> BD

      reply	other threads:[~2005-11-15  8:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15  7:45 A standard snapshot notification framework in Linux ? Block Device
2005-11-15  8:24 ` Coywolf Qi Hunt [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=20051115082408.GA3249@localhost.localdomain \
    --to=qiyong@fc-cn.com \
    --cc=blockdevice@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.