public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: wysochanski@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 man/lvcreate.8.in tools/lvcreate.c Date: Wed, 29 Apr 2009 20:14:00 -0000 [thread overview] Message-ID: <20090429201421.24523.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: wysochanski@sourceware.org 2009-04-29 20:14:21 Modified files: man : lvcreate.8.in tools : lvcreate.c Log message: Fixup whitespace. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvcreate.8.in.diff?cvsroot=lvm2&r1=1.5&r2=1.6 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/lvcreate.c.diff?cvsroot=lvm2&r1=1.184&r2=1.185 --- LVM2/man/lvcreate.8.in 2009/04/29 20:11:46 1.5 +++ LVM2/man/lvcreate.8.in 2009/04/29 20:14:21 1.6 @@ -147,7 +147,7 @@ .B lvdisplay(8) on the snapshot in order to check how much data is allocated to it. Note that a small amount of the space you allocate to the snapshot is -used to track the locations of the chunks of data, so you should +used to track the locations of the chunks of data, so you should allocate slightly more space than you actually need and monitor the rate at which the snapshot data is growing so you can avoid running out of space. --- LVM2/tools/lvcreate.c 2009/04/26 08:12:12 1.184 +++ LVM2/tools/lvcreate.c 2009/04/29 20:14:21 1.185 @@ -563,7 +563,7 @@ size_t len; char *vorigin_name; struct logical_volume *lv; - + if (!(segtype = get_segtype_from_string(cmd, "zero"))) { log_error("Zero segment type for virtual origin not found"); return 0; @@ -747,7 +747,7 @@ "be mixed."); return 0; } - + if (!lv_info(cmd, org, &info, 0, 0)) { log_error("Check for existence of snapshot " "origin '%s' failed.", org->name);
reply other threads:[~2009-04-29 20:14 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090429201421.24523.qmail@sourceware.org \ --to=wysochanski@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).