From: Jan Bakuwel <jan.bakuwel@omiha.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM corruption/diagnosis
Date: Thu, 07 Apr 2011 08:51:11 +1200 [thread overview]
Message-ID: <4D9CD23F.6010208@omiha.com> (raw)
In-Reply-To: <1302079983.27047.454.camel@localhost>
Hi Radu,
Thanks for your response.
> Now the only question that's left to be answered is why the heck a
> windows xp guest (yes, my guest machines are windows xp too) would crash
> (or not even boot) when there is some particular data left in the
> *unallocated* filesystem blocks. But since I have a "certain" opinion
> about microsoft and their products, I just think that life is too short
> to bother yourself with this kind of crap.
That is indeed a good question and the reason why I initially didn't
pursue this track. I wouldn't be surprised if this would indeed be a
"feature" of Windows XP/Microsoft. Another question would be why a)
Windows XP would hang itself up beyond repair after having run for half
a year just fine as well as leaving it's disc space in a unusable state.
After all making image backups of Windows machines and restoring them to
known states is a well tried method.
> I hope this helps you debug the issue you had. It would also be
> interesting if you could try to zero the *original* LVM volume (the one
> that didn't work) and then restore the image once again and see if it
> works. It would prove (or disprove) my theory :)
I'll do just that in the next few days and will report back.
best regards,
Jan
next prev parent reply other threads:[~2011-04-06 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 4:44 [linux-lvm] LVM corruption/diagnosis Jan Bakuwel
2011-04-06 8:53 ` Radu Rendec
2011-04-06 20:51 ` Jan Bakuwel [this message]
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=4D9CD23F.6010208@omiha.com \
--to=jan.bakuwel@omiha.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 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.