public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2/man lvcreate.8.in Date: Fri, 20 Jan 2012 10:50:00 -0000 [thread overview] Message-ID: <20120120105040.1201.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2012-01-20 10:50:40 Modified files: man : lvcreate.8.in Log message: Thin extend lvcreate man page about snapshot support Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvcreate.8.in.diff?cvsroot=lvm2&r1=1.34&r2=1.35 --- LVM2/man/lvcreate.8.in 2011/12/21 13:58:38 1.34 +++ LVM2/man/lvcreate.8.in 2012/01/20 10:50:39 1.35 @@ -81,9 +81,7 @@ .RB [ \-n | \-\-name .IR SnapshotLogicalVolume { Name | Path }] .BR \-s | \-\-snapshot -.RI { OriginalLogicalVolume { Name | Path } -| -.IR VolumeGroup { Name | Path } +.RI {[ VolumeGroup { Name | Path }/] OriginalLogicalVolumeName .BR \-V | \-\-virtualsize .IR VirtualSize [ bBsSkKmMgGtTpPeE ]} .br @@ -241,16 +239,19 @@ A mirror is divided into regions of this size (in MB), and the mirror log uses this granularity to track which regions are in sync. .TP -.IR \fB\-s ", " \fB\-\-snapshot " " OriginalLogicalVolume { Name | Path } -.RI "| " VolumeGroup { Name | Path } +.IR \fB\-s ", " \fB\-\-snapshot " " OriginalLogicalVolume { Name | Path } Create a snapshot logical volume (or snapshot) for an existing, so called original logical volume (or origin). Snapshots provide a 'frozen image' of the contents of the origin while the origin can still be updated. They enable consistent -backups and online recovery of removed/overwritten data/files. The snapshot -does not need the same amount of storage the origin has. In a typical scenario, -15-20% might be enough. In case the snapshot runs out of storage, use +backups and online recovery of removed/overwritten data/files. +Thin snapshot is created when the origin is a thin volume and +the size is not specified. Thin snapshot shares same blocks within +the thin pool volume. +The snapshot with the specified size does not need the same amount of +storage the origin has. In a typical scenario, 15-20% might be enough. +In case the snapshot runs out of storage, use .BR lvextend (8) to grow it. Shrinking a snapshot is supported by .BR lvreduce (8)
next reply other threads:[~2012-01-20 10:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-20 10:50 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-12-21 13:58 zkabelac 2011-11-10 12:41 zkabelac 2011-11-08 12:12 zkabelac 2011-11-07 10:59 zkabelac 2011-11-04 22:47 zkabelac 2011-10-30 22:08 zkabelac 2011-10-28 20:36 zkabelac 2011-10-28 20:33 zkabelac 2009-09-29 15:11 wysochanski
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20120120105040.1201.qmail@sourceware.org \ --to=zkabelac@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).