From: Miles Fidelman <mfidelman@traversetechnologies.com>
To: debian-user <debian-user@lists.debian.org>,
linux-raid@vger.kernel.org, linux-lvm@redhat.com
Subject: progress, but... - re. fixing LVM/md snafu
Date: Sun, 05 Apr 2009 13:05:50 -0400 [thread overview]
Message-ID: <49D8E4EE.3020703@traversetechnologies.com> (raw)
Hello again Folks,
So.. I'm getting closer to fixing this messed up machine.
Where things stand:
I have root defined as an LVM2 LV, that should use /dev/md2 as it's PV.
/dev/md2 in turn is a RAID1 array built from /dev/sda3 /dev/sdb3 and
/dev/sdc3
Instead, LVM is reporting: "Found duplicate PV
2ppSS2q0kO3t0tuf8t6S19qY3ypWBOxF: using /dev/sdb3 not /dev/sda3"
and the /dev/md2 is reporting itself as inactive (cat /proc/mdstat) and
active,degraded (mdadm --detail)
---
I'm guessing that, during boot:
- the raid array failed to start
- LVM found both copies of the PV, and picked one (/dev/sdb3)
- everything then came up and my server is humming away
but: the md array can't rebuild because the most current device in it is
already in use
so... I'm looking for the right sequence of events, with the minimum
downtime to:
1. stop changes to /dev/sdb3 (actually, to / - which complicates things)
2. rebuild the RAID1 array, making sure to use /dev/sdb3 as the starting
point for current data
3. restart in such a way that LVM finds /dev/md2 as the right PVM
instead of one of its components
Each of these is just tricky enough that I'm sure there are lots of
gotchas to watch out for.
So.. any suggestions?
Thanks very much,
Miles Fidelman
_______________________________________________
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/
next reply other threads:[~2009-04-05 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 17:05 Miles Fidelman [this message]
2009-04-05 21:44 ` progress, but... - re. fixing LVM/md snafu Goswin von Brederlow
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=49D8E4EE.3020703@traversetechnologies.com \
--to=mfidelman@traversetechnologies.com \
--cc=debian-user@lists.debian.org \
--cc=linux-lvm@redhat.com \
--cc=linux-raid@vger.kernel.org \
/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).