From: AJ Lewis <alewis@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Extending a stripped Logical Volume
Date: 04 Jan 2005 13:40:27 -0600 [thread overview]
Message-ID: <x058y79htjo.fsf@null.msp.redhat.com> (raw)
In-Reply-To: <mailman.10663.1103890645.8459.linux-lvm@redhat.com>
Olmo Gonz�lez <olmo@olmo.org> writes:
> I am new to this list, seeking for some help.
>
> I have setup LVM2 under debian sarge (2.6.8-k7 kernel).
>
> I originally created a volumen group (nasvg) on 4 x ST3200822A ATA
> DISK drives. I created a stripped logical volume spanning these 4
> disks and using up al PE's available. I then attached two aditional
> ST3200822A ATA DISK drives and I would now want to resive my logical
> volumen to use al the PE's provided by the two new disks. The problem
> is I can't extend the logical volume, getting the following error:
>
> gollum:~# lvextend -L+1G /dev/nasvg/naslv
> Using stripesize of last segment 64KB
> Extending logical volume naslv to 746.23 GB
> Insufficient allocatable extents suitable for parallel use for
> logical volume naslv: 191036 required
>
> I have been googl'ing and it seems that this has to do with
> restrictions on resizing sttriped LV's. However, the information I
> have found says the restrictions no longer apply to LVM2.
You should be able to 'lvextend -L+1G /dev/nasvg/naslv -i1' if you
have and additional 1G of free space in the VG. However, based on the
vgdisplay output below, it looks like you only have 3.72G free (or
95388 extents), so you'd want do do: 'lvextend -l+95388
/dev/nasvg/naslv -i2' if you want to stripe it across the 2 new disks,
or 'lvextend -l+95388 /dev/nasvg/naslv -i1' if you want it to be a
linear segment.
> gollum:~# vgdisplay
> --- Volume group ---
> VG Name nasvg
> System ID
> Format lvm2
> Metadata Areas 6
> Metadata Sequence No 25
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 1
> Open LV 1
> Max PV 0
> Cur PV 6
> Act PV 6
> VG Size 1.09 TB
> PE Size 4.00 MB
> Total PE 286168
> Alloc PE / Size 190780 / 745.23 GB
> Free PE / Size 95388 / 372.61 GB
> VG UUID LWqtTF-F8vA-yjXt-AYwK-yFQr-skDa-s9UVRC
>
> --- Logical volume ---
> LV Name /dev/nasvg/naslv
> VG Name nasvg
> LV UUID GMm5PD-6Rdk-h8lG-35Fw-rZp3-L42s-N6k9QC
> LV Write Access read/write
> LV Status available
> # open 1
> LV Size 745.23 GB
> Current LE 190780
> Segments 1
> Allocation inherit
> Read ahead sectors 0
> Block device 254:0
>
Regards,
--
AJ Lewis Voice: 612-638-0500
Red Hat Inc. E-Mail: alewis@redhat.com
720 Washington Ave. SE, Suite 200
Minneapolis, MN 55414
Current GPG fingerprint = D9F8 EDCE 4242 855F A03D 9B63 F50C 54A8 578C 8715
Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the
many keyservers out there...
next parent reply other threads:[~2005-01-04 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.10663.1103890645.8459.linux-lvm@redhat.com>
2005-01-04 19:40 ` AJ Lewis [this message]
[not found] <mailman.15037.1105141586.8459.linux-lvm@redhat.com>
2005-01-11 17:00 ` [linux-lvm] Extending a stripped Logical Volume AJ Lewis
2005-01-07 23:43 Olmo González Alcojor
-- strict thread matches above, loose matches on Subject: below --
2004-12-24 12:19 Olmo González
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=x058y79htjo.fsf@null.msp.redhat.com \
--to=alewis@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