All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alasdair G Kergon <agk@uk.sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] problem
Date: Wed Jan  8 17:09:02 2003	[thread overview]
Message-ID: <20030108231014.I28021@uk.sistina.com> (raw)
In-Reply-To: <20030108225455.H28021@uk.sistina.com>; from agk@uk.sistina.com on Wed, Jan 08, 2003 at 10:54:55PM +0000

Procedure to follow:
  
   vgcfgbackup -P -f /tmp/vgbackup rootvg

   Edit the backup file as follows:
   Add "WRITE" to the status line and remove "PARTIAL"

e.g.
   status = ["RESIZEABLE", "PARTIAL", "READ"]
becomes
   status = ["RESIZEABLE", "READ", "WRITE"]


Remove the whole PV section for your "unknown device"
- referenced as "pv1" in this example.

                pv1 {
                        id = "TBCgjx-ne5X-4fHP-aHqe-dKJR-Vwnb-kjDhWQ"
                        device = "unknown device"       # Hint only

                        status = ["ALLOCATABLE"]
                        pe_start = 128
                        pe_count = 5    # 20 Megabytes
                }


Remove the whole LV section for any LVs that refer to the pv you
removed above (pv1 here referenced inside "stripes") e.g.

                tmp {
                        id = "4eTLYv-PTDr-FXvv-58Xk-Q4Th-p8yi-GeKCHr"
                        status = ["READ", "WRITE", "VISIBLE"]
                        segment_count = 1

                        segment1 {
                                start_extent = 0
                                extent_count = 3        # 12 Megabytes

                                type = "striped"
                                stripe_count = 1        # linear

                                stripes = [
                                        "pv1", 0
                                ]
                        }
                }

Write the metadata back to disk:
  vgcfgrestore -f /tmp/vgbackup rootvg

Alasdair
-- 
agk@uk.sistina.com

  reply	other threads:[~2003-01-08 17:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 12:03 [linux-lvm] problem Daniel Wittenberg
2003-01-08 14:12 ` Steven Lembark
2003-01-08 14:32   ` Daniel Wittenberg
2003-01-08 15:45     ` Alasdair G Kergon
2003-01-08 16:24       ` Daniel Wittenberg
2003-01-08 16:29         ` Alasdair G Kergon
2003-01-08 16:34           ` Daniel Wittenberg
2003-01-08 16:54             ` Alasdair G Kergon
2003-01-08 17:09               ` Alasdair G Kergon [this message]
2003-01-08 17:14                 ` Alasdair G Kergon
2003-01-09 14:26                 ` Daniel Wittenberg
  -- strict thread matches above, loose matches on Subject: below --
2002-12-26  1:34 [linux-lvm] Problem nellis
2002-12-26  7:17 ` Guido Guenther

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=20030108231014.I28021@uk.sistina.com \
    --to=agk@uk.sistina.com \
    --cc=linux-lvm@sistina.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.