From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alasdair G Kergon Subject: Re: [Cluster-devel] [Lsf-pc] [LSF/MM ATTEND] [TOPIC] fs/block interface discussions Date: Thu, 11 Dec 2014 00:52:22 +0000 Message-ID: <20141211005222.GB26014@agk-dp.fab.redhat.com> References: <5488335C.9090605@redhat.com> <20141210124833.GG25671@quack.suse.cz> <548854EE.1020901@redhat.com> <20141210184651.GB9398@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Steven Whitehouse , linux-fsdevel , cluster-devel , lsf-pc@lists.linux-foundation.org To: Jan Kara Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50109 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932822AbaLKAw2 (ORCPT ); Wed, 10 Dec 2014 19:52:28 -0500 Content-Disposition: inline In-Reply-To: <20141210184651.GB9398@quack.suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: 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