From: Xen <list@xenhideout.nl>
To: Linux lvm <linux-lvm@redhat.com>
Subject: [linux-lvm] how to change UUID of PV of duplicate partition (followup)
Date: Fri, 06 Jan 2017 20:10:20 +0100 [thread overview]
Message-ID: <78cb8a27a39f59bc31b11e1044af620f@dds.nl> (raw)
I mean,
This is what I mean:
Found duplicate PV 3U9ac3Ah5lcZUf03Iwm0cgMMaKxdflg0: using /dev/sdb4
not /dev/sdc4
Using duplicate PV /dev/sdb4 without holders, replacing /dev/sdc4
Volume group containing /dev/sdb4 has active logical volumes
Physical volume /dev/sdb4 not changed
0 physical volumes changed / 1 physical volume not changed
It immediately replaced the good PV with the bad PV (that I was trying
to change) so I cannot actually get to the "bad" PV (which is duplicate)
to change it without booting an external system in which I can effect
one disk in isolation.
But, after running that command my root filesystem was now mounted
read-only instantly so even just attaching the disk basically causes the
entire system to instantly fail.
Real good right.
Probably my entire fault right :-/.
"Let's cause this system to crash, we'll attach a harddisk." "Job done!"
Actually I guess in this case it replaced the bad with the good but
behind the scenes something else happened as well. This time it is
hiding /dev/sdc4, the other time it was hiding /dev/sdb4, it seems to be
random.
Basically any eSata system that a disk gets attached to could cause the
operating system to fail. The same would probably be true of regular USB
disks.
Even inserting a USB stick could crash a system like this.
next reply other threads:[~2017-01-06 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 19:10 Xen [this message]
2017-01-06 19:19 ` [linux-lvm] how to change UUID of PV of duplicate partition (followup) David Teigland
2017-01-06 19:21 ` Xen
2017-01-06 20:06 ` Zdenek Kabelac
2017-01-06 20:13 ` Xen
2017-01-06 20:11 ` Xen
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=78cb8a27a39f59bc31b11e1044af620f@dds.nl \
--to=list@xenhideout.nl \
--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).