linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Chris Mason <chris.mason@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	adilger@sun.com, sfr@canb.auug.org.au,
	linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: Notes on support for multiple devices for a single filesystem
Date: Wed, 17 Dec 2008 16:27:58 -0500	[thread overview]
Message-ID: <49496EDE.5080101@garzik.org> (raw)
In-Reply-To: <ac3eb2510812171320i414d89d4x9840954275774d51@mail.gmail.com>

Kay Sievers wrote:
> Features like the very nice and useful directory-based snapshots would
> also not be possible with simple block-based multi-devices, right?

Snapshotting via block device has always been an incredibly dumb hack, 
existing primarily because filesystem-based snapshots did not exist for 
the filesystem in question.

Snapshots are better at the filesystem level because the filesystem is 
the only entity that knows when the filesystem is quiescent and 
snapshot-able.

ISTR we had to add ->write_super_lockfs() to hack in support for LVM in 
this manner, rather than doing it the right way.

	Jeff



  parent reply	other threads:[~2008-12-17 21:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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  5:55       ` Stephen Rothwell
2008-12-11 14:43       ` Chris Mason
2008-12-15 21:03         ` Andreas Dilger
2008-12-15 22:55           ` Kay Sievers
2008-12-16  1:37             ` Chris Mason
2008-12-16  1:39               ` Kay Sievers
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 [this message]
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
     [not found] <e1f6055f0812181336q105b4ebcy81d72edd2a35baa8@mail.gmail.com>
2008-12-19 19:03 ` Bryan Henderson
2008-12-19 19:30   ` Chris Mason

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=49496EDE.5080101@garzik.org \
    --to=jeff@garzik.org \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris.mason@oracle.com \
    --cc=hch@infradead.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).