linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@redhat.com>
To: Alessandro MACUZ <alessandro.macuz@gmail.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] I can't have the mirror_log mirrored, LVM	complains "there is no suitable space"
Date: Thu, 4 Jul 2013 17:40:16 +0100	[thread overview]
Message-ID: <20130704164016.GB3344@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <CAFrGbuWmVKH+N970R6qrCEV1BaSSWyLix-4+66sP_Q84+bAFqQ@mail.gmail.com>

On Thu, Jul 04, 2013 at 04:27:51PM +0200, Alessandro MACUZ wrote:
> root@Microknoppix:/tmp/lvm2-2_02_98# lvconvert -vvv -m1 --mirrorlog
> mirrored --alloc normal /dev/lvgrptstnlvm/root /dev/sdb1

So you want to convert an existing LV into a mirror (-m1) with a mirrored log
with the default allocation policy allocating all new extents from /dev/sdb1.

The current layout:

>         /dev/sda1 0:      0   1536: root(0:0)
>         /dev/sda1 1:   1536    767: NULL(0:0)
>         /dev/sdb1 0:      0   2271: NULL(0:0)
>         /dev/sdb2 0:      0     31: NULL(0:0)
>         /dev/sdc 0:      0      7: NULL(0:0)

The Physical Extents that can used for allocation during this process:

>         Adding PE range: start PE 0 length 2271 on /dev/sdb1

Details of the allocation requested:

>         Allowing allocation on /dev/sdb1 start PE 0 length 2271
>         Parallel PVs at LE 0 length 1536: /dev/sda1

>         Still need 1538 total extents:
>           1 (1 data/0 parity) parallel areas of 1536 extents each
>           2 mirror logs of 1 extents each

So it is looking for 1536 extents on a disk that is not /dev/sda1
and 2 further extents for the mirrored log on different disks from each other.

But it only has one disk available - /dev/sdb1 - so this will fail unless
you go down to --alloc anywhere.

So what should you do?
If you want a mirrored log, decide where to put it and provide the command
with additional space on another disk to hold it.

So let it use part of /dev/sda1 perhaps by appending '/dev/sda1:1536' to
the command or if that isn't enough, try something like '/dev/sdb2:0 /dev/sdc:0'.

Alasdair

      reply	other threads:[~2013-07-04 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02  0:14 [linux-lvm] I can't have the mirror_log mirrored, LVM complains "there is no suitable space" Alessandro MACUZ
2013-07-02 16:08 ` Alessandro MACUZ
2013-07-02 16:24   ` Alessandro MACUZ
2013-07-03 22:44     ` Alessandro MACUZ
2013-07-04 10:55       ` matthew patton
2013-07-04 12:45         ` Alessandro MACUZ
2013-07-04 11:18 ` Alasdair G Kergon
2013-07-04 11:43   ` Alessandro MACUZ
2013-07-04 14:27     ` Alessandro MACUZ
2013-07-04 16:40       ` Alasdair G Kergon [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=20130704164016.GB3344@agk-dp.fab.redhat.com \
    --to=agk@redhat.com \
    --cc=alessandro.macuz@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).