From mboxrd@z Thu Jan 1 00:00:00 1970 From: C Anthony Risinger Subject: Re: What to do about subvolumes? Date: Wed, 1 Dec 2010 10:03:23 -0600 Message-ID: References: <20101201142136.GD427@dhcp231-156.rdu.redhat.com> <1291219269-sup-8392@think> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Josef Bacik , linux-btrfs , linux-fsdevel , hch , ssorce To: Chris Mason Return-path: In-Reply-To: <1291219269-sup-8392@think> Sender: linux-btrfs-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Dec 1, 2010 at 10:01 AM, Chris Mason w= rote: > Excerpts from C Anthony Risinger's message of 2010-12-01 09:51:55 -05= 00: >> On Wed, Dec 1, 2010 at 8:21 AM, Josef Bacik wrote= : >> > >> > =3D=3D=3D How do we want subvolumes to work from a user perspectiv= e? =3D=3D=3D >> > >> > 1) Users need to be able to create their own subvolumes. =A0The pe= rmission >> > semantics will be absolutely the same as creating directories, so = I don't think >> > this is too tricky. =A0We want this because you can only take snap= shots of >> > subvolumes, and so it is important that users be able to create th= eir own >> > discrete snapshottable targets. >> > >> > 2) Users need to be able to snapshot their subvolumes. =A0This is = basically the >> > same as #1, but it bears repeating. >> >> could it be possible to convert a directory into a volume? =A0or at >> least base a snapshot off it? > > I'm afraid this turns into the same complexity as creating a new volu= me > and copying all the files/dirs in by hand. ok; if i create an empty volume, and use cp --reflink, it would have the desired affect though, right? C Anthony -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html