From: Chris Cox <chris_cox@stercomm.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm on a share environnement (SAN inside)
Date: Thu, 27 Sep 2007 12:36:27 -0500 [thread overview]
Message-ID: <46FBEA1B.7070905@stercomm.com> (raw)
In-Reply-To: <D1DF25FB-02EE-46BF-92AF-4DB9039BFFB8@ensil.unilim.fr>
hubert chomette wrote:
> Hi,
> I recently install a SAN at my work. One lun is used for XEN and can be
> used by two xen server.
> For more flexibility I use lvm on this lun. I was very happy of the
> result, unless I discover (during a conversation with a friend) that lvm
> metadata can be compromised if the two server simulty modify metadata.
> - So what can I do?
Use seperate LUNs. I'm not sure what your friend is talking about.
Unless you have two machines using the same LUN, in which case
there are issues... this would be a cluster filesystem issue, or
near-high availability issue...
> - Is it possible to allow LVM metadata modification by only one server?
> - should I use clvm instead?
Metadata won't creep outside of what is visible.
> - Is it possible to migrate lvm to clvm without any data lost?
Not sure.
>
> thank's for your help
>
> regards,
>
> ps: sorry for my poor english
>
>
>
>
> _______________________________________________
> 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/
>
--
Chris Cox
Sr. Unix Sys Admin
next prev parent reply other threads:[~2007-09-27 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 13:50 [linux-lvm] lvm on a share environnement (SAN inside) hubert chomette
2007-09-27 17:36 ` Chris Cox [this message]
2007-09-27 19:01 ` hubert chomette
2007-09-27 21:12 ` Chris Cox
2007-09-28 0:18 ` hubert chomette
2007-09-28 15:50 ` Chris Cox
2007-09-28 7:12 ` David Robinson
2007-10-02 10:11 ` hubert chomette
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=46FBEA1B.7070905@stercomm.com \
--to=chris_cox@stercomm.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.