From: Serge Hallyn Date: Thu, 15 Aug 2013 20:37:30 +0000 (-0500) Subject: document new lxc-create btrfs behavior X-Git-Tag: lxc-1.0.0.alpha1~1^2~77 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=fbbf51926e113e5e70d6ea507ed7d1019d0e0aa8;p=thirdparty%2Flxc.git document new lxc-create btrfs behavior Signed-off-by: Serge Hallyn --- diff --git a/doc/lxc-create.sgml.in b/doc/lxc-create.sgml.in index f9b0228ec..a8de5b5b6 100644 --- a/doc/lxc-create.sgml.in +++ b/doc/lxc-create.sgml.in @@ -131,10 +131,12 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA 'dir' has the same meaning as 'none', but also allows the optional --dir ROOTFS to be specified, meaning that the container rootfs should be placed under the specified path, - rather than the default. - The option 'btrfs' need not be specified as it will be used - automatically if the @LXCPATH@ filesystem is found to - be btrfs. If backingstore is 'lvm', then an lvm block device will be + rather than the default. If 'btrfs' is specified, then the + target filesystem must be btrfs, and the container rootfs will be + created as a new subvolume. This allows snapshotted clones to be + created, but also causes rsync --one-filesystem to treat it as a + separate filesystem. + If backingstore is 'lvm', then an lvm block device will be used and the following further options are available: --lvname lvname1 will create an LV named lvname1 rather than the default, which