All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arshavir Grigorian <ag@m-cam.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: partition strategy
Date: Fri, 03 Sep 2004 11:05:18 -0400	[thread overview]
Message-ID: <4138882E.40400@m-cam.com> (raw)
In-Reply-To: <20040903124909.GN6264@agk.surrey.redhat.com>

Alasdair G Kergon wrote:

>>>>>Is it better to create 3 partitions 2 x230G + 1G 
>>>>>Is it better to create 2 paritions 230G and 231G, put both in a vg, 
>>>>>          
>>>>>
>
>  
>
>>>ie the first option.  
>>>      
>>>
>I meant the second option:-)
>
>  
>
>>Could you, please tell me what I am doing wrong? TIA.
>>    
>>
> 
>  
>
>>casals:~# lvextend -l +134 /dev/vg00/lvol0 /dev/hdc3
>> Using stripesize of last segment 8KB
>> Insufficient allocatable extents suitable for parallel use for logical 
>>volume lvol0: 118816 required
>>    
>>
>
>If you don't specify the stripe settings, lvextend uses whatever
>the last segment of the LV you're extending uses i.e. 2 stripes in 
>this case.  So you need to specify -i1 to add a new segment with
>just one stripe.
>
>Alasdair
>  
>
Many thanks. It all makes sense now.
The way I got it working is just creating 2 partititions, getting the 
number of extends from the smaller partition, creating a striped lv with 
that paritition count, then extending it to the remaining the extents as 
with a single stripe.


Arshavir

      reply	other threads:[~2004-09-03 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 19:24 [linux-lvm] partition strategy Arshavir Grigorian
2004-09-01 21:09 ` [linux-lvm] " Arshavir Grigorian
2004-09-02 13:52   ` Stephen Boulet
2004-09-02 17:42   ` Alasdair G Kergon
2004-09-02 22:40     ` Arshavir Grigorian
2004-09-03 12:49       ` Alasdair G Kergon
2004-09-03 15:05         ` Arshavir Grigorian [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=4138882E.40400@m-cam.com \
    --to=ag@m-cam.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.