From: "Christian Schröder" <cs@deriva.de>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Is cLVM necessary when accessing different logical volumes on a shared iSCSI target?
Date: Sat, 06 Jul 2013 14:47:43 +0200 [thread overview]
Message-ID: <51D811EF.7070102@deriva.de> (raw)
In-Reply-To: <1372859936.18752.YahooMailNeo@web181505.mail.ne1.yahoo.com>
Hi Matthew,
thanks again for your comments. The idea to use tags is very
interesting. I will have a deeper look at it. However, I still do not
understand if filtering (either hard-coded or using tags) is *necessary*
to make things working or if it is just *adviseable* to prevent using a
volume simultaneously from both clients?
When I tried to set up the scenario as described, I encountered another
problem which might be related to the sharing stuff: When I virtually
disconnect the physical volume (by disconnecting from the iSCSI server)
and reconnect again, I get i/o errors when I try to access a logical
volume. I have tried pvscan, vgscan and lvscan, but nothing helps.
Interestingly, the volume group and all logical values are found by
vgscan / lvscan, but I cannot access it. Is this the expected behavior?
Is there any chance (besides rebooting the client machine) to recover
from such a situation?
Regards,
Christian
--
Deriva GmbH Tel.: +49 551 489500-42
Financial IT and Consulting Fax: +49 551 489500-91
Hans-B�ckler-Stra�e 2 http://www.deriva.de
D-37079 G�ttingen
Amtsgericht G�ttingen | HRB 3240
Gesch�ftsf�hrer: Dirk Baule, Christian Schr�der
Deriva CA Certificate: http://www.deriva.de/deriva-ca.cer
next prev parent reply other threads:[~2013-07-06 12:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 17:27 [linux-lvm] Is cLVM necessary when accessing different logical volumes on a shared iSCSI target? Christian Schröder
2013-07-03 2:12 ` matthew patton
2013-07-03 13:07 ` Christian Schröder
2013-07-03 13:58 ` matthew patton
2013-07-06 12:47 ` Christian Schröder [this message]
2013-07-06 17:40 ` matthew patton
2013-07-08 10:56 ` Christian Schröder
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=51D811EF.7070102@deriva.de \
--to=cs@deriva.de \
--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.