From: Marian Csontos <mcsontos@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
unix.co@gmail.com
Subject: Re: [linux-lvm] /dev/mapper entries
Date: Tue, 13 May 2014 09:14:20 +0200 [thread overview]
Message-ID: <5371C64C.2010907@redhat.com> (raw)
In-Reply-To: <CAAKRE72CA+c2waO_g5xAdyocB58UvzUgqi26RQUGZZTe0TAVog@mail.gmail.com>
On 05/13/2014 07:53 AM, Umar Draz wrote:
> Hi All
>
> I have 2 systems where I have shared SAN sotrage, I am using LVM without
> cluster.
Hello Umar,
which version of lvm and what distribution? There is lvmetad in newer
versions of LVM and you may need to rescan PVs (pvscan --cache $PV)
However using shared storage without cluster locking is nothing but
asking for trouble...
It is advised to either partition the storage (set zones or whatever the
SAN allows) or to set global_filter/filter on both machines so each of
the machines sees only appropriate LUNs it is intended to see and use.
Regards,
-- Martian
>
> If I create a logical volume on server1 and then on server2 (vgchange
> --refresh or vgchange -a y) I can get that logical volume on server2 as
> well.
>
> The same thing I am using on volume deletion e.g.
>
> If I remove volume from server1 its properly remove the volume and also all
> of its entries, and then I refresh the volume group on server2 its also
> refresh its self but a entry in /dev/mapper not removing
>
> how to refresh this /dev/mapper/ on other server while deleting volumes
>
> Br.
>
> Umar
>
>
>
> _______________________________________________
> 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/
>
prev parent reply other threads:[~2014-05-13 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 5:53 [linux-lvm] /dev/mapper entries Umar Draz
2014-05-13 7:14 ` Marian Csontos [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=5371C64C.2010907@redhat.com \
--to=mcsontos@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=unix.co@gmail.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).