From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvextend docmentation vs. implementation (lvm2-2.02.39), Suse-11.1
Date: Wed, 10 Feb 2010 14:22:26 +0000 [thread overview]
Message-ID: <20100210142226.GF18505@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <4B72BAF5.9090005@tlinx.org>
On Wed, Feb 10, 2010 at 05:56:05AM -0800, Linda A. Walsh wrote:
> Sorry -- I was using it with capital "L" not lower case...didn't know
> there were two separate switches... my bad.
> thanks,
The implementation of the feature turned out simpler with -l than with -L.
(Because sizes supplied with -L require conversion to 'natural units'
of extents which may involve rounding.)
Alasdair
prev parent reply other threads:[~2010-02-10 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 6:38 [linux-lvm] lvextend docmentation vs. implementation (lvm2-2.02.39), Suse-11.1 Linda A. Walsh
2010-02-10 8:22 ` Christine Caulfield
2010-02-10 9:20 ` Ray Morris
2010-02-10 13:56 ` Linda A. Walsh
2010-02-10 14:22 ` Alasdair G Kergon [this message]
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=20100210142226.GF18505@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
/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: link
Be 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 NNTP newsgroup(s).