We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
** Changed in
Use of "lvconvert -m 1 --corelog vg00/testdisk" on data that you care
about is a bad idea. This tells LVM to create the log in memory. When a
write occurs, it is written to disk and the log. Should one disk
complete before the other (which is very likely to happen, especially
with non-disk PVs), th
On Gutsy mirroring with two devices works fine:
$ sudo lvconvert -m 1 --corelog vg00/testdisk
Logical volume testdisk converted.
$ sudo lvs -a -o +devices
LV VG Attr LSize Origin Snap% Move Log Copy%
Devices
testdiskvg00 mwi-a- 4.00G
I've reopened this, since lvcreate still fails.
** Changed in: lvm2 (Ubuntu)
Status: Invalid => New
--
lvcreate fails with mirror raid1
https://bugs.launchpad.net/bugs/120792
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
This documentation:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Cluster_Logical_Volume_Manager/LV_create.html
explains that you can keep the log in memory only, which requires a re-scan of
the mirror on bootup.
However, it still doesn't work:
% sudo lvcreate -L 1G -
Sorry I cannot answer any of your questions. The fact is I only know
that LVM works this way (without any details regarding boot process, or
internal mechanizms).
On the other hand I think this thread should be continued somewhere else
(Ubuntu Forums, #ubuntu support channel at irc.freenode.net or
And then, bug 120364...
Anyway, why does it need a log device? It is the first time I hear about a raid
1 needing the number of devices equal to the number of copies + 1. In fact, I
thought than with lvm I could even have two copies of data in the same physical
volume, as in AIX's lvm, for insta
LVM needs 3 devices for a mirror device: two for the mirror devices and one for
the disk log.
The error message is not very straightforward, however, this should be fixed
upstream if it really needs a fix.
For further information please read the lvcreate(8) manual page.
** Changed in: lvm2 (Ubu
