linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jens Wilke <jens.wilke@de.ibm.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] [PATCH] lvm metadata handling, 	warn only once about missing PV
Date: Fri, 9 Jun 2006 12:30:39 +0200	[thread overview]
Message-ID: <200606091230.40205.jens.wilke@de.ibm.com> (raw)
In-Reply-To: <4489484E.6010806@conterra.de>

On Friday 09 June 2006 12:07, Dieter St�ken wrote:
> Jens Wilke wrote:
> > With patch:
> >
> > # vgchange -ay -P
> >   Partial mode. Incomplete volume groups will be activated read-only.
> >   Missing PV with uuid 'egDxmo-sVp7-OQGB-6mgt-84mk-xioM-ahdzBw' in VG
> > main 2 logical volume(s) in volume group "main" now active
>
> the metadata backup also shows the device name as a hint.
> Is this saved by the on-disk MD, too? Might be helpful to see.

Dieter,

Yes, the on-disk and backup metadata is identical so we have the
device hint. But I don't think that it is really a good idea to show it,
because this would make up a bit pitfall and confusing in stress
situations.

But it would be usefull to add a list of lvs that are partially available
or degraded in case of mirrors, so you have a quick info what is
the actual state of your system.

Best,

Jens

-- 
  Jens Wilke
  Linux on zSeries - Application Development Tools + GCC
  phone +49-(0)7031-16-3936 - tl *120-3936 - email jens.wilke@de.ibm.com
  IBM Germany Lab, Schoenaicher Str. 220, 71032 Boeblingen

  reply	other threads:[~2006-06-09 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09  9:37 [linux-lvm] [PATCH] lvm metadata handling, warn only once about missing PV Jens Wilke
2006-06-09 10:07 ` Dieter Stüken
2006-06-09 10:30   ` Jens Wilke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-08 16:55 Jens Wilke

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=200606091230.40205.jens.wilke@de.ibm.com \
    --to=jens.wilke@de.ibm.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 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).