From: brem belguebli <brem.belguebli@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Re: Ambiguous mirror log option
Date: Fri, 18 Sep 2009 16:21:32 +0200 [thread overview]
Message-ID: <29ae894c0909180721w40630e22y1c750cdd88562580@mail.gmail.com> (raw)
In-Reply-To: <29ae894c0909180608l7bd4c6c9mb8a0272adf3edaf4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Got the right doc,
the log device MUST belong to the VG, it cannot be an external device, it is
specified as thrid device vhen creating the LV:
lvcreate -m1 --mirrorlog disk -L 9G -n lvolvm1 VMVG /dev/firstleg
/dev/secondleg /dev/log...
2009/9/18, brem belguebli <brem.belguebli@gmail.com>:
>
> Running x86_64 RHEL 5u4
>
> 2009/9/18, brem belguebli <brem.belguebli@gmail.com>:
>>
>> Hi,
>>
>> I've been struggling with lvcreate for more than a hour to create a
>> mirror'ed LV with on disk log, with no success (I'm ashamed! :-| )
>>
>>
>> Here's what I typed on a VG (with 2 X 8678 4MB extents free), it's not a
>> free space issue...
>>
>> lvcreate -m1 --mirrorlog disk -L 9G -n lvolvm1 VMVG, it complains about
>> 2304 more extents required (wich make the exact size of the LV I want to
>> create), plus where to define the log device to use ?
>>
>> same command whith --corelog (instead of --mirrorlog disk) succeeds.
>>
>> Same command without any of these 2 options fails with the same complain
>> as the first (man page says that default no option == mirrolog disk).
>>
>> Any tip ?
>>
>> Regards
>>
>
>
[-- Attachment #2: Type: text/html, Size: 1966 bytes --]
prev parent reply other threads:[~2009-09-18 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 13:07 [linux-lvm] Ambiguous mirror log option brem belguebli
2009-09-18 13:08 ` [linux-lvm] " brem belguebli
2009-09-18 14:21 ` brem belguebli [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=29ae894c0909180721w40630e22y1c750cdd88562580@mail.gmail.com \
--to=brem.belguebli@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).