All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Larsen <plarsen@CIBER.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [IMPORTANT]LVM+iSCSI issue..Local Disk disappeared..
Date: Wed, 15 Oct 2008 12:06:54 -0400	[thread overview]
Message-ID: <1224086814.7418.11.camel@localhost.localdomain> (raw)
In-Reply-To: <d5dce2210810150620l2e9c4b44uc519eeeebadd604f@mail.gmail.com>

On Wed, 2008-10-15 at 18:50 +0530, himanshu padmanabhi wrote:
> 
> I am using "iscsi-initiator-utils-6.2.0.865-0.2.fc7" as initiator and 
> "iscsitarget-0.4.15-1" as target. 
> 
> 
> Following is the scenario 
> 
> 
> PV  =  local_disk1       remote_disk1  (i.e PV is formed using 2
> disks 
> 1 local and 1 from iscsitarget) 

Strange construction?
Why not simply format each target as a separate PV and then join them in
a single VG? Much easier to manage. 

That aside - I wouldn't mix and match that way. You're getting very
different response times and security issues on each device. I would
treat them very different.

> VG  =  Vgname 

You need to assign the PV's to your VG.

> LV =  lv_localdisk_1       lv_localremotedisk1 
> lv_remotedisk1 (i.e. 1 lv only from local disk,1 from remote 
> iscsitarget and one from combination of both) 

That makes no sense. You don't use physical volumes when you create
logical ones. You use groups. You don't assign physical devices like
that when you do LVs.

> I performed "logout" operation on "remote_disk1" after deactivating 
> "lv_localremotedisk1 and           lv_remotedisk1" on it using 
> "lvchange" command. 
> 
> 
> Then result I should at least get, 
> 
> 
> PV  =  local_disk1    (remote_disk1 is removed now) 
> 
> 
> VG = Vgname 
> 
> 
> LV = lv_localdisk1     (So LVs containing PVs as "remote_disk1" are 
> deactivated.It can be in combination with local disk also)

No - things don't work that way. If you damage/remove a PV from a VG -
everything in that VG gets disabled until the whole VG is operational.
It doesn't matter if your LV is in the area damaged or not.

> i.e They all were lost temporarily. 

Not temporarily. As long as the VG is bad, nothing is there. You should
see all available PVs but the way you set it up, you didn't do a PV on
each disk so when the disk-group sees one disk missing the whole disk
group is offline, you loose your PV, your VG gets deactivated = the
result you see.

> When I logged in to the same target and activated the LVs on 
> "remote_disk1",I got my original configuration.i.e. 

Because your PV is now present, the VG can activate etc.


--- 
Regards
    Peter Larsen

We have met the enemy, and he is us.
		-- Walt Kelly

  reply	other threads:[~2008-10-15 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 13:20 [linux-lvm] [IMPORTANT]LVM+iSCSI issue..Local Disk disappeared himanshu padmanabhi
2008-10-15 16:06 ` Peter Larsen [this message]
2008-10-16 10:27   ` himanshu padmanabhi
2008-10-16 10:48     ` Klaus Strebel
2008-10-16 15:20     ` Peter Larsen
2008-10-20  7:40       ` himanshu padmanabhi
2008-10-20 17:14         ` Peter Larsen

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=1224086814.7418.11.camel@localhost.localdomain \
    --to=plarsen@ciber.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.