From: Jan Bakuwel <jan.bakuwel@diala.gl3>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM corruption/diagnosis
Date: Tue, 05 Apr 2011 16:44:26 +1200 [thread overview]
Message-ID: <4D9A9E2A.7070106@diala.gl3> (raw)
Hi,
OS: Debian Lenny
Hypervisor: Xen 3.2-1
kernel: 2.6.18-6-xen-amd64
lvm2: 2.02.06-4etch1
lvm-common: 1.5.20
Hardware: IBM x3650 hardware RAID5 on SAS with battery backup
I've used LVM2 for years without any issue. I recently diagnosed a
problem with a Windows XP virtual machine running on a Debian Lenny Xen
dom0. After getting reports of stability problems and unexpected
crashes, I restored the VM from a image backup that is known to work. To
my surprise, that image also was crashing unexpectingly. After much
trial and error, I decided to create a new LV and restore the image to
the new LV (rather than using the existing LV). My surprise was even
bigger when that turned out to be the solution: the Windows XP VM has
been running fine since.
Now the daunting (?!) task awaits me to diagnose why one LV is suitable
for a Windows XP VM and another no longer is (even though it has been
fine for at least half a year).
Advise on how I can diagnose potential corruption problems with LVs much
appreciated.
cheers,
Jan
next reply other threads:[~2011-04-05 4:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 4:44 Jan Bakuwel [this message]
2011-04-06 8:53 ` [linux-lvm] LVM corruption/diagnosis Radu Rendec
2011-04-06 20:51 ` Jan Bakuwel
2011-04-06 21:32 ` Jan Bakuwel
2011-04-06 21:52 ` Ron Johnson
2011-04-07 2:06 ` Jan Bakuwel
2011-04-07 2:16 ` Ron Johnson
2011-04-07 5:47 ` Radu Rendec
2011-04-07 8:31 ` Jan Bakuwel
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=4D9A9E2A.7070106@diala.gl3 \
--to=jan.bakuwel@diala.gl3 \
--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).