All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Limpach" <chris@pin.lu>
To: linux-lvm@sistina.com, ARechenberg@shermanfinancialgroup.com
Subject: Re: [linux-lvm] Recovering from a hard crash
Date: Mon Feb 24 11:50:02 2003	[thread overview]
Message-ID: <089901c2dc2d$0f3dc2a0$070414ac@pin> (raw)
In-Reply-To: 8075D5C3061B9441944E137377645118012E6B@cinshrexc03.shermfin.com

"Rechenberg, Andrew" <ARechenberg@shermanfinancialgroup.com> wrote:
> Well, unless I'm reading this wrong, it looks as if /dev/md0 and
> /dev/md10 have the same pvdata for some reason.  /dev/md0 is the first
> part of /dev/md10.  Any ideas as to what's going on and how to resolve
> this issue?

md0 is the beginning of md10 and the LVM metadata is located at the start of
the PVs.  This is why vgscan/pvscan sees the same PV on md0 and md10.  I
think (untested...) that the ugly quick fix is to "mv /dev/md0 /dev/notmd0",
this should work because vgscan/pvscan then won't see the device node.  The
less ugly fix is to use LVM2 with a devicename filter which excludes md0.
In the long run (and since this is a test system), I'd suggest that you
recreate your VG from PVs on each /dev/md[0-9] instead of creating and using
/dev/md10.  This also gives you better control of where your
snapshot-copy-on-write-space will be located (best not on the same
disks...).

    christian

  reply	other threads:[~2003-02-24 11:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24  9:21 [linux-lvm] Recovering from a hard crash Rechenberg, Andrew
2003-02-24 11:50 ` Christian Limpach [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-24 14:14 Rechenberg, Andrew
2003-02-25 11:58 ` Christian Limpach
2003-02-24 13:16 Rechenberg, Andrew
2003-02-24  8:56 Rechenberg, Andrew
2003-02-24  8:50 Rechenberg, Andrew

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='089901c2dc2d$0f3dc2a0$070414ac@pin' \
    --to=chris@pin.lu \
    --cc=ARechenberg@shermanfinancialgroup.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.