From: Digimer <lists@alteeve.ca>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: lihuiba <magazine.lihuiba@163.com>
Subject: Re: [linux-lvm] LVM high availability
Date: Fri, 14 Jun 2013 11:22:06 -0400 [thread overview]
Message-ID: <51BB351E.4020707@alteeve.ca> (raw)
In-Reply-To: <16dd71d1.f00b.13f3e5336d3.Coremail.magazine.lihuiba@163.com>
On 06/13/2013 12:16 PM, lihuiba wrote:
> Please consider the following case:
> there are multiple storage servers each configured as LVM on top of a RAID,
> and the servers are connected by DRBD to synchronize the RAIDs.
>
> The question is
> 1) can I safely active a read-only volume on all of the servers?
Depends on your file system. GFS2 and OCFS2 is fine. Most all others are
not. In either case, you can't mount a Secondary DRBD resource no matter
what.
> 2) can I safely active a read-write volume on a randomly chosen server?
You need a cluster-aware files system like GFS2 and, in the context of
LVM, you need clustered VGs and LVs which requires clvmd to be running.
> 3) how about thin pool and volumes?
I've not played with these.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
next prev parent reply other threads:[~2013-06-14 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 16:16 [linux-lvm] LVM high availability lihuiba
2013-06-14 15:22 ` Digimer [this message]
2013-06-21 6:44 ` Marian Csontos
2013-06-21 7:32 ` matthew patton
2013-06-23 14:32 ` lihuiba
2013-06-24 8:21 ` Zdenek Kabelac
2013-06-27 3:19 ` Huiba Li
-- strict thread matches above, loose matches on Subject: below --
2000-09-27 19:57 [linux-lvm] LVM High Availability Michael J Kellen
2000-09-28 4:59 ` Michael Lausch
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=51BB351E.4020707@alteeve.ca \
--to=lists@alteeve.ca \
--cc=linux-lvm@redhat.com \
--cc=magazine.lihuiba@163.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.