From: Alasdair G Kergon <agk@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [Lsf-pc] [LSF/MM ATTEND] [TOPIC] fs/block interface discussions
Date: Thu, 11 Dec 2014 00:52:22 +0000 [thread overview]
Message-ID: <20141211005222.GB26014@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20141210184651.GB9398@quack.suse.cz>
On Wed, Dec 10, 2014 at 07:46:51PM +0100, Jan Kara wrote:
> But still you first need to stop all writes to the filesystem, then do a
> sync, and then allow writing again - which is exactly what freeze does.
And with device-mapper, we were asked to support the taking of snapshots
of multiple volumes simultaneously (e.g. where the application data is
stored across more than one filesystem). Thin dm snapshots can handle
this (the original non-thin ones can't).
Alasdair
next prev parent reply other threads:[~2014-12-11 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 11:49 [Cluster-devel] [LSF/MM ATTEND] [TOPIC] fs/block interface discussions Steven Whitehouse
2014-12-10 12:48 ` [Cluster-devel] [Lsf-pc] " Jan Kara
2014-12-10 14:13 ` Steven Whitehouse
2014-12-10 18:46 ` Jan Kara
2014-12-11 0:52 ` Alasdair G Kergon [this message]
2014-12-12 11:46 ` Steven Whitehouse
2014-12-12 20:22 ` Jan Kara
2014-12-12 20:38 ` Alex Elsayed
2014-12-12 20:49 ` Alex Elsayed
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=20141211005222.GB26014@agk-dp.fab.redhat.com \
--to=agk@redhat.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).