From: Alasdair G Kergon <agk@redhat.com>
To: Guillermo Schulman <guillermos@avature.net>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Problems with snapshot rollback
Date: Thu, 20 Dec 2012 15:11:06 +0000 [thread overview]
Message-ID: <20121220151106.GB11558@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <50D32703.70307@avature.net>
If you *intend* to rollback, have you considered doing the test in
the snapshot itself (which can be written to) and not bothering
with a later merge?
But for any unpredictable problems with devices, first thing to rule out is
unintended interference from udev.
Alasdair
prev parent reply other threads:[~2012-12-20 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 14:56 [linux-lvm] Problems with snapshot rollback Guillermo Schulman
2012-12-20 15:11 ` Alasdair G Kergon [this message]
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=20121220151106.GB11558@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=guillermos@avature.net \
--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).