From: travis+ml-linux-lvm@subspacefield.org
To: linux-lvm-request@redhat.com
Subject: [linux-lvm] automatic repartitioning of devices in /etc/lvm/cache/.cache?
Date: Thu, 25 Aug 2016 21:20:22 -0700 [thread overview]
Message-ID: <20160826042022.GS1534@subspacefield.org> (raw)
Hello, I've got a persistent problem in that the second two disks of my array
occasionally have their heads wiped, with a GPT showing up at the beginning
of the partition, with the same partitioning structure as the main disk GPT.
The overall structure is:
md127 = /dev/sd{b,c,d,e}1
LUKS on that
PV/VG/LV on that.
So my ONLY lead so far, that distinguishes sd{d,e}1 (which get wiped)
from sd{b,c}1 is that they were listed in /etc/lvm/cache/.cache.
Is there any way that being listed there could be a side effect, or be
a cause, of disk partition corruption in those devices?
This system crashed and failed to recover, but I strongly suspect that
it was unattended and un-administered between the last boot and an
unrelated kernel panic, whereupon I discovered the disk corruption.
So, I'm wondering, is there any unattended process, or possibly any one
triggered by an admin, that would re-partition a device listed there,
or restore a GPT from backup or something?
--
http://www.subspacefield.org/~travis/ | if spammer then john@subspacefield.org
"Computer crime, the glamor crime of the 1970s, will become in the
1980s one of the greatest sources of preventable business loss."
John M. Carroll, "Computer Security", first edition cover flap, 1977
next reply other threads:[~2016-08-26 5:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 4:20 travis+ml-linux-lvm [this message]
2016-08-26 10:46 ` [linux-lvm] automatic repartitioning of devices in /etc/lvm/cache/.cache? Bryn M. Reeves
2016-08-26 21:30 ` travis+ml-linux-lvm
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=20160826042022.GS1534@subspacefield.org \
--to=travis+ml-linux-lvm@subspacefield.org \
--cc=linux-lvm-request@redhat.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).