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 16:51:57 +0800 [thread overview]
Message-ID: <be7468bb0701110051p507e1736q2eccdd490d7ac21@mail.gmail.com> (raw)
In-Reply-To: <5adb39f00701102307tebf5624sd2656d17b87978a3@mail.gmail.com>
On 1/11/07, David Tran <davidtt3@gmail.com> wrote:
> Thank for your help.
> My pvs:
> linux-server:/ # pvscan
> PV /dev/hdb1 VG gdata lvm2 [111.79 GB / 0 free]
> PV /dev/hde1 VG gdata lvm2 [279.46 GB / 40.00 MB free]
> PV /dev/hdf1 VG gdata lvm2 [153.38 GB / 153.38 GB free] (this is the
> new hd)
> Total: 3 [544.62 GB] / in use: 3 [544.62 GB] / in no VG: 0 [0 ]
> I think that it is enogh free space, because I add one more HD already.
> More over, vgdisplay show it has: Free PE / Size 39276 / 153.42 GB
so /dev/gdata/priv is striped? you can check by running:
lvdisplay /dev/gdata/priv
and look for the value of Segments.
if its more than 1, it is sriped. and to resize it:
lvextend -L +100G -t -i1 /dev/gdata/priv /dev/hdf1
which will only use the free PEs from /dev/hdf1. the -t will only test
the process. if says it is ok, re-run the command w/o the "-t".
> Thank you.
>
--
roderick e. tapang, nclp
retapang at gmail dot com
(o_.' http://counter.li.org/
//\ ----------------------
V_/_ Linux User # 253842
next prev parent reply other threads:[~2007-01-11 8:51 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
2007-01-11 7:07 ` David Tran
2007-01-11 8:51 ` roderick tapang [this message]
-- 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=be7468bb0701110051p507e1736q2eccdd490d7ac21@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).