All of lore.kernel.org
 help / color / mirror / Atom feed
From: ben <benscott@nwlink.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] specifying contiguous yields odd results
Date: Mon, 22 Apr 2013 21:09:59 -0700	[thread overview]
Message-ID: <201304222109.59424.benscott@nwlink.com> (raw)

I have discovered something strange when extending a striped logical volume. 

For example, start with a volume that has three physical volumes and three 
stripes then run lvextend on it. If the policy is set to 'contiguous' then all 
the physical volumes of the last segment must be on the command line. What is 
odd is that the striping can be set to a lower number so not all those 
physical volumes are really used. 


~#lvs  --segments -o +devices
  LV    VG   Attr      #Str Type    SSize Devices
  lvol0 vg8  -wi-a----    3 striped 2.00g /dev/sdc(0),/dev/sdd(0),/dev/sde(0)

~# lvextend -i 2 --alloc contiguous -l +2049 vg8/lvol0 /dev/sdc /dev/sdd
  Using stripesize of last segment 64.00 KiB
  Rounding size (6147 extents) up to stripe boundary size for segment (6148 
extents)
  Extending logical volume lvol0 to 3.00 GiB
  Insufficient suitable contiguous allocatable extents for logical volume lvol0: 
2050 more required

~# lvextend -i 2 --alloc contiguous -l +2049 vg8/lvol0 /dev/sdc /dev/sdd 
/dev/sde
  Using stripesize of last segment 64.00 KiB
  Rounding size (6147 extents) up to stripe boundary size for segment (6148 
extents)
  Extending logical volume lvol0 to 3.00 GiB
  Logical volume lvol0 successfully resized

~# lvs  --segments -o +devices
  LV    VG   Attr      #Str Type    SSize Devices
  lvol0 vg8  -wi-a----    3 striped 2.00g /dev/sdc(0),/dev/sdd(0),/dev/sde(0)
  lvol0 vg8  -wi-a----    2 striped 1.00g /dev/sdc(1366),/dev/sdd(1366)

Is it intended that with contiguous allocation the striping should match or 
not? Thank you.

                 reply	other threads:[~2013-04-23  4:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201304222109.59424.benscott@nwlink.com \
    --to=benscott@nwlink.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.