All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Eisenkölbl" <eisenkoe@cargo-partner.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] clusteredVG+mirroredLV
Date: Wed, 25 Apr 2007 10:29:52 +0200	[thread overview]
Message-ID: <462F1180.1010602@cargo-partner.com> (raw)
In-Reply-To: <47D4EAB4-1EA1-42DB-A8F9-C412B07E0005@engineyard.com>

Do you know when it will be released?
Will it work with with RHEL 5?

Jayson Vantuyl wrote:
> Mirroring (and snapshotting) does not currently work with clustered 
> VGs.  This is because cmirror (and csnap) is not released yet.
>
> On Apr 25, 2007, at 2:48 AM, Michael Eisenk�lbl wrote:
>
>> Hi all,
>>
>> i want to create a two node cluster with three iSCSI devices.
>> the iSCSI devices should be mirrored (2mirror+1log) to be more secure.
>> I am going to configure 3 PVs and after a clustered volume group, so 
>> this is no problem.
>> but when I am trying to create the mirrored logical volume (on this 
>> clusteredVG), I got the following error message:
>>
>> lvcreate command failed.
>> Command attempted: "/usr/sbin/lvcreate -n mirrorLV -l 6 -m1 mirrorVG 
>> /dev/sde1 /dev/sdb1 /dev/sdc1" - System Error Message:   Error 
>> locking on node server4: Internal lvm error, check syslog
>> Aborting. Failed to activate mirror log. Remove new LVs and retry.
>> Failed to create mirror log.
>>
>> I deleted everything and retried it, but everytime the same error.
>> cluster is working good. clvmd is also started with locking mode 2.
>> if I try to create a normal VG with a mirrored LV everythings fine.
>> if I try to create a clustered VG with a normal LV everythings fine.
>> but not a clustered VG with a mirrored LV...... why?
>>
>> maybe somebody can help me with this situation.
>>
>> kind regards
>> Michael
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com <mailto:linux-lvm@redhat.com>
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
>
> -- 
> Jayson Vantuyl
> Systems Architect
> *Engine Yard <http://www.engineyard.com>*
> jvantuyl@engineyard.com <mailto:jvantuyl@engineyard.com>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2007-04-25  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <462332EF.5090505@cargo-partner.com>
     [not found] ` <462E65D2.5070008@cargo-partner.com>
2007-04-25  7:48   ` [linux-lvm] clusteredVG+mirroredLV Michael Eisenkölbl
2007-04-25  8:16     ` Jayson Vantuyl
2007-04-25  8:29       ` Michael Eisenkölbl [this message]
2007-04-25 12:18       ` Michael Eisenkölbl
     [not found] <20070425121838.70D3A732E7@hormel.redhat.com>
2007-04-25 14:46 ` Lin_ChiiShing
2007-04-25 15:31   ` Jonathan Brassow
2007-04-25 20:00     ` Michael Eisenkölbl
2008-01-29  8:55     ` Michael Eisenkölbl

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=462F1180.1010602@cargo-partner.com \
    --to=eisenkoe@cargo-partner.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.