From: Mike Snitzer <snitzer@redhat.com>
To: Guilherme Moro <guilherme.moro@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM snapshot merge and corrupted file
Date: Mon, 2 Dec 2013 09:39:11 -0500 [thread overview]
Message-ID: <20131202143911.GA5331@redhat.com> (raw)
In-Reply-To: <CADsoVx80SzPEnyyzmEFRppTHqBSsyuOuvN+q-eQAOxPd_VHgYg@mail.gmail.com>
On Mon, Dec 02 2013 at 6:41am -0500,
Guilherme Moro <guilherme.moro@gmail.com> wrote:
> Hi,
>
> I know that is a too broad question, but please be kind ;)
> The scenario:
> RHEL 6.2 - snapshot a disk mounted over multipath device mapper
> Upgrade system to RHEL 6.4
> Merge the snapshot to return the system to previous state.
> System get unstable and rebooting cyclic (not reaching user-level, at
> least the logs don't show it)
> Spot a file that got more or less 1200 bytes corrupted (mostly turned to 0).
The first rollback attempt was done in production?
> Sadly, I got called to the machine too late to recover the console
> output of the reboot (it's a blade and no console logs was
> configured), and could figure out if some hardware failure happened.
>
> As I don't have proper logs to further investigate my questions is:
>
> - There are any know issues around snapshotting in this conditions
> (RHEL 6.2 -> RHEL 6.4, multipath)?
Not aware of any.
> - There's any chance of this being a software failure (bug?) and do
> the restore procedure warn me in the logs (/var/log/message?) about
> any failure during the restore (even if hardware related).
>
> My main suspicion for now is a hardware failure somewhere, but I was
> kindly asked to be sure that this can't be a bug.
>
> Any thoughts or pointers (docs, pieces of code, testing reports) would
> be appreciate, so don't be shy :)
The lvm2 testsuite has support for testing snapshot-merge; but it
doesn't test layering snapshot ontop of multipath.
Without context (e.g. logs) for what happened it is really hard to say
definitively whether or not you hit some software bug or if your problem
was hardware failure like you suspect.
next prev parent reply other threads:[~2013-12-02 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 11:41 [linux-lvm] LVM snapshot merge and corrupted file Guilherme Moro
2013-12-02 14:39 ` Mike Snitzer [this message]
2013-12-02 15:46 ` Guilherme Moro
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=20131202143911.GA5331@redhat.com \
--to=snitzer@redhat.com \
--cc=guilherme.moro@gmail.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).