All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Harvell <jharvell@dogpad.net>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] pvs complains of missing PVs that are not missing
Date: Thu, 24 Oct 2013 10:30:54 -0500	[thread overview]
Message-ID: <52693D2E.705@dogpad.net> (raw)
In-Reply-To: <5268E9CA.60100@redhat.com>

Le 24/10/2013 04:35, Zdenek Kabelac a �crit :
> Dne 23.10.2013 18:43, Joe Harvell napsal(a):
>>> Hi Joe,
>>>
>>> I am having similar issues in that I have a LVM2 raid1 mirror between a
>>> local disk and a iSCSI disk and once I remove the iSCSI disk and add it
>>> back, the mirror stays broken. I traced the cause of that to be LVM2 
>>> still
>>> complains about a PV missing even though the same PV has been added 
>>> back.
>>>
>>> I wonder if you have resolved your issue and what did you do.
>>> Thanks a lot.
>>> Shi
>>>
>>>
>>> _______________________________________________
>>> 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/
>> Shi,
>>
>> This is not yet resolved.  I'm still waiting for Peter Rajnoha to 
>> follow up
>> after I provided him the information he requested.  He said he might 
>> be able
>> to look at it more closely later this week. In the mean time, I work 
>> around
>> this issue by activating the VG with --partial.  I can access my 
>> data, but I
>> can't make any LVM config changes.
>>
>>
>
> If the missing PV is reattached to your system - you need to
>
> vgextend --restoremissing   /dev/path_to_PV
>
>
> Since once the PV is detected as missing - metadata are update on 
> present PVs,
> and the missing PV is marked as MISSING.
> When such PV reappear - you need to run the command to re-synchronize 
> metadata.
>
> Zdenek
>
> _______________________________________________
> 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/
>
My faith in LVM is restored.  This fixed my problem.  I really need to 
read through all those man pages more closely.

  reply	other threads:[~2013-10-24 15:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-23  4:26 [linux-lvm] pvs complains of missing PVs that are not missing Shi Jin
2013-10-23 16:43 ` Joe Harvell
2013-10-24  9:35   ` Zdenek Kabelac
2013-10-24 15:30     ` Joe Harvell [this message]
2013-10-24 16:26       ` Alasdair G Kergon
  -- strict thread matches above, loose matches on Subject: below --
2013-10-09 21:29 Joe Harvell
2013-10-09 21:49 ` Joe Harvell
     [not found] ` <1381356552.67129.YahooMailNeo@web181504.mail.ne1.yahoo.com>
2013-10-09 23:04   ` Joe Harvell
     [not found]   ` <5255D815.1090704@tekcomms.com>
     [not found]     ` <1381361455.80237.YahooMailNeo@web181502.mail.ne1.yahoo.com>
2013-10-10 15:04       ` Joe Harvell
2013-10-10 18:38         ` Peter Rajnoha
2013-10-10 18:48           ` Peter Rajnoha
2013-10-10 19:48           ` Joe Harvell

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=52693D2E.705@dogpad.net \
    --to=jharvell@dogpad.net \
    --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.