From: Raptorfan <raptorfan@earthlink.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: tariq wali <ganaiwali@gmail.com>
Subject: Re: [linux-lvm] lvreduce nightmare
Date: Sun, 20 May 2012 17:39:34 -0400 [thread overview]
Message-ID: <4FB96496.70404@earthlink.net> (raw)
In-Reply-To: <CAGQjrKYrgcx+y8M6NnLGZK5Z+hNpH3Fp4E2EysnKGZuObaFuBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On 5/18/2012 10:13 AM, tariq wali wrote:
> so to i guess to do this right i should have
> resize2fs /dev/vg0/data 1.6T or (1600G
> and then lvreduce -n data -L 100G /dev/vg0/data ( to reduce the lvm by
100 )
This is probably a nit-picking.. but seriously consider picking a single
numeric selection for both operations. Either run both commands with an
absolute value (preferable in my opinion; there is NO QUESTION at that
point what your final state should be) or with the delta value. Mixing
both in the commands is another way to confuse what you actually want to
accomplish. If you'd used absolute values to start with there probably
would have been a reduced chance of failure (barring a typo.. though you
still need to verify the resize2fs command completed successfully before
doing the lvreduce).
-r
[-- Attachment #2: Type: text/html, Size: 1151 bytes --]
next prev parent reply other threads:[~2012-05-20 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 15:48 [linux-lvm] lvreduce nightmare tariq wali
2012-05-17 23:13 ` Ray Morris
2012-05-18 0:21 ` Stuart D Gathman
2012-05-18 1:16 ` Andy Smith
2012-05-18 10:25 ` Bryn M. Reeves
2012-05-18 14:13 ` tariq wali
2012-05-19 15:58 ` Stuart D Gathman
2012-05-19 23:14 ` Andy Smith
2012-05-20 8:59 ` tariq wali
2012-05-20 19:45 ` Andy Smith
2012-05-21 9:02 ` Bryn M. Reeves
2012-05-20 21:39 ` Raptorfan [this message]
2012-05-18 9:57 ` Bryn M. Reeves
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=4FB96496.70404@earthlink.net \
--to=raptorfan@earthlink.net \
--cc=ganaiwali@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.