linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "roderick tapang" <retapang@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvextend Insufficient free space
Date: Thu, 11 Jan 2007 09:41:19 +0800	[thread overview]
Message-ID: <be7468bb0701101741h6ef6adacs38bb89d134fcf890@mail.gmail.com> (raw)
In-Reply-To: <5adb39f00701082249g3a13757csf27383fa9a27e53d@mail.gmail.com>

On 1/9/07, David Tran <davidtt3@gmail.com> wrote:
>   Cur PV                3
>   Act PV                3
>   VG Size               544.62 GB
>   PE Size               4.00 MB
>   Total PE              139424
>   Alloc PE / Size       100148 / 391.20 GB
>   Free  PE / Size       39276 / 153.42 GB
>   VG UUID
> gROPCK-xUmS-Tk99-nTmp-S63F-otHE-9QJukD
> -------------------------------------------------------------
> /////// So I have 153.42 GB free space NOW
> -------------------------------------------------------------
> linux-server:/ # lvextend -L +100G /dev/gdata/priv
>   Extending logical volume priv to 177.80 GB
>   Insufficient free space: 45517 extents needed, but only 39276 available

is /dev/gdata/priv striped? if it is, it looks like the PVs don't have
enough PEs each to accommodate equal stripe distribution.
wha'ts the output of "pvs"?

-- 
roderick e. tapang, nclp
retapang at gmail dot com

(o_.'       http://counter.li.org/
//\         ----------------------
V_/_        Linux User   #  253842

  parent reply	other threads:[~2007-01-11  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  6:49 [linux-lvm] lvextend Insufficient free space David Tran
2007-01-09 23:07 ` Dave Wysochanski
2007-01-11  1:41 ` roderick tapang [this message]
2007-01-11  7:07   ` David Tran
2007-01-11  8:51     ` roderick tapang
  -- strict thread matches above, loose matches on Subject: below --
2007-01-25  9:03 Bernhard Hoelcker

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=be7468bb0701101741h6ef6adacs38bb89d134fcf890@mail.gmail.com \
    --to=retapang@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 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).