linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: Brad Voth <brad@voth.name>,
	adilger@sun.com, Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	Jeff Garzik <jeff@garzik.org>, Kay Sievers <kay.sievers@vrfy.org>,
	linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, sfr@canb.auug.org.au
Subject: Re: Notes on support for multiple devices for a single filesystem
Date: Fri, 19 Dec 2008 14:30:15 -0500	[thread overview]
Message-ID: <1229715015.6695.71.camel@think.oraclecorp.com> (raw)
In-Reply-To: <OF3415C20F.793A0D3C-ON88257524.0067548F-88257524.0068BCEC@us.ibm.com>

On Fri, 2008-12-19 at 11:03 -0800, Bryan Henderson wrote:
> "Brad Voth" <brad@voth.name> wrote on 12/18/2008 01:36:12 PM:
> 
> > I can see the desire to have the snapshot at the filesystem level to
> > ensure that the filesystem knows it is consistent.  However, this 
> > can be a duplication of effort because of the need to have snapshots
> > at the block device level for non-fs devices.  Such as raw logical 
> > devices for say a database.  I would think that a viable consistent 
> > solution would be to have the block device snapshot mechanism have a
> > hook into the filesystem api to say, "I'm preparing to take a 
> > snapshot, please quiesce and return" <take block snapshot> "You may 
> > now resume, Mr. Filesystem"

This is what lvm does now with the write_super_lockfs calls.  They work
well for a specific purpose.

At the end of the day snapshots mean different things to different
people and different workloads.  In lots of ways the lvm snapshots work
very well.

But, doing snapshots at the FS level gives you better performance and
more control.

-chris



  reply	other threads:[~2008-12-19 19:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e1f6055f0812181336q105b4ebcy81d72edd2a35baa8@mail.gmail.com>
2008-12-19 19:03 ` Notes on support for multiple devices for a single filesystem Bryan Henderson
2008-12-19 19:30   ` Chris Mason [this message]
2008-11-20 12:18 Btrfs trees for linux-next Chris Mason
2008-12-11  2:34 ` Chris Mason
2008-12-11  3:14   ` Stephen Rothwell
2008-12-11  4:06     ` Andrew Morton
2008-12-11 14:43       ` Chris Mason
2008-12-15 21:03         ` Andreas Dilger
2008-12-17 13:23           ` Notes on support for multiple devices for a single filesystem Christoph Hellwig
2008-12-17 14:50             ` Kay Sievers
2008-12-17 15:08               ` Christoph Hellwig
2008-12-17 15:33                 ` Kay Sievers
2008-12-17 14:53             ` Chris Mason
2008-12-17 19:53             ` Andrew Morton
2008-12-17 20:58               ` Chris Mason
2008-12-17 21:20                 ` Kay Sievers
2008-12-17 21:26                   ` Chris Mason
2008-12-17 21:27                   ` Jeff Garzik
2008-12-18 21:22                     ` Bryan Henderson
2008-12-17 21:24                 ` Andreas Dilger
2008-12-17 21:30                   ` Jeff Garzik
2008-12-17 21:41                   ` Chris Mason
2008-12-22  1:59               ` Liu Hui
2008-12-17 22:04             ` Andreas Dilger
2008-12-17 22:19               ` Dave Kleikamp

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=1229715015.6695.71.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=brad@voth.name \
    --cc=hbryan@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).