Excerpts from C Anthony Risinger's message of 2010-12-01 11:03:23 -0500: > On Wed, Dec 1, 2010 at 10:01 AM, Chris Mason <chris.mason@xxxxxxxxxx> wrote: > > Excerpts from C Anthony Risinger's message of 2010-12-01 09:51:55 -0500: > >> On Wed, Dec 1, 2010 at 8:21 AM, Josef Bacik <josef@xxxxxxxxxx> wrote: > >> > > >> > === How do we want subvolumes to work from a user perspective? === > >> > > >> > 1) Users need to be able to create their own subvolumes. ÂThe permission > >> > semantics will be absolutely the same as creating directories, so I don't think > >> > this is too tricky. ÂWe want this because you can only take snapshots of > >> > subvolumes, and so it is important that users be able to create their own > >> > discrete snapshottable targets. > >> > > >> > 2) Users need to be able to snapshot their subvolumes. ÂThis is basically the > >> > same as #1, but it bears repeating. > >> > >> could it be possible to convert a directory into a volume? Âor at > >> least base a snapshot off it? > > > > I'm afraid this turns into the same complexity as creating a new volume > > 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? Almost, for no good reason at all our cp --reflink doesn't reflink across subvols. I'll get that fixed up. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
