From: Phil Turmel <philip@turmel.org>
To: "Rainer Fügenstein" <rfu@oudeis.org>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Found duplicate PV: using /dev/sda3 not /dev/md1
Date: Mon, 16 Jun 2014 10:35:26 -0400 [thread overview]
Message-ID: <539F00AE.9090504@turmel.org> (raw)
In-Reply-To: <19411862.20140616155327@oudeis.org>
Hi Rainer,
[CC to list added back. Use reply-to-all on kernel.org lists]
On 06/16/2014 09:53 AM, Rainer Fügenstein wrote:
>
> PT> Your problem is that you are using version 0.90 metadata. It and v1.0
> PT> put the superblock at the end of the member devices, and it cannot be
> PT> found if the device size changes. Plus, the data starts at sector zero,
> PT> so if the MD superblock isn't found, the device content is identified
> PT> without the raid layer.
>
> If I understand it correctly, the error happened (apart from the
> superblock version) because of the reboot(s) before a) md1 was grown
> and/or/maybe b) sync was finished.
Probably, but v0.9 arrays are vulnerable to whole-disk vs. partition
misidentification, and should never be used on a partition that
encompasses the end of a disk.
> PT> These metadata formats should only be used with boot partitions that
> PT> need to be readable without assembling the array.
> this was how the centos installer created the raid (with 0.90). will
> keep it that way on md0 (which holds /boot and root).
>
> PT> You need to stop /dev/md1 as soon as possible to eliminate the chances
> PT> of further corruption.
>
> [root@gateway home]# mdadm --manage --stop /dev/md1
> mdadm: fail to stop array /dev/md1: Device or resource busy
> Perhaps a running process, mounted filesystem or active volume group?
>
> [root@gateway home]# lsof | grep md1
> md1_raid1 461 root cwd DIR 9,0 4096 2 /
> md1_raid1 461 root rtd DIR 9,0 4096 2 /
> md1_raid1 461 root txt unknown /proc/461/exe
>
> since nothing else than md1_raid1 is accessing /dev/md1, I assume it
> is safe to --force --stop?
What is running as process ID 461? That needs to be killed off, and any
mount involving /dev/md1 stopped.
> PT> If you must keep the server online, I recommend the following steps:
>
> big thanks, your strategy is much better than the one I had planned
> (and fills some knowledge gaps).
Your situation is the primary reason I recommend LVM.
Phil
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-16 14:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 21:58 Found duplicate PV: using /dev/sda3 not /dev/md1 Rainer Fügenstein
2014-06-15 18:35 ` Rainer Fügenstein
2014-06-16 2:46 ` Phil Turmel
[not found] ` <19411862.20140616155327@oudeis.org>
2014-06-16 14:35 ` Phil Turmel [this message]
2014-06-16 18:20 ` Re[2]: " Rainer Fügenstein
2014-06-16 20:15 ` Phil Turmel
2014-06-16 20:28 ` Re[2]: " Rainer Fügenstein
2014-06-16 20:54 ` Phil Turmel
2014-06-17 1:27 ` Re[2]: " Rainer Fügenstein
2014-06-17 11:57 ` Phil Turmel
2014-06-17 12:00 ` Phil Turmel
2014-06-17 14:12 ` Re[2]: " Rainer Fügenstein
2014-08-06 12:49 ` Re[3]: " Rainer Fügenstein
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=539F00AE.9090504@turmel.org \
--to=philip@turmel.org \
--cc=linux-raid@vger.kernel.org \
--cc=rfu@oudeis.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 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.