Skip to content

L
lxc
Commit fbbf5192 by Serge Hallyn
Options

document new lxc-create btrfs behavior

Signed-off-by: 's avatarSerge Hallyn <serge.hallyn@ubuntu.com>
parent d44e88c2
Showing with 6 additions and 4 deletions
doc/lxc-create.sgml.in
...@@ -131,10 +131,12 @@ Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA ...@@ -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' has the same meaning as 'none', but also allows the optional
<replaceable>--dir ROOTFS</replaceable> to be specified, meaning <replaceable>--dir ROOTFS</replaceable> to be specified, meaning
that the container rootfs should be placed under the specified path, that the container rootfs should be placed under the specified path,
rather than the default. rather than the default. If 'btrfs' is specified, then the
The option 'btrfs' need not be specified as it will be used target filesystem must be btrfs, and the container rootfs will be
automatically if the <filename>@LXCPATH@</filename> filesystem is found to created as a new subvolume. This allows snapshotted clones to be
be btrfs. If backingstore is 'lvm', then an lvm block device will 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: used and the following further options are available:
<replaceable>--lvname lvname1</replaceable> will create an LV <replaceable>--lvname lvname1</replaceable> will create an LV
named <filename>lvname1</filename> rather than the default, which named <filename>lvname1</filename> rather than the default, which
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment