From: Jim Minter <jminter@redhat.com>
To: dm-devel@redhat.com
Subject: Re: potential dm-thin recovery issue
Date: Wed, 06 Mar 2013 16:13:14 +0000 [thread overview]
Message-ID: <51376B1A.2090201@redhat.com> (raw)
In-Reply-To: <20130306142706.GB4852@raspberrypi>
On 03/06/13 14:27, thornber@redhat.com wrote:
> On Wed, Mar 06, 2013 at 08:26:55AM -0500, Jim Minter wrote:
>> Hello,
>>
>> Following on from my previous e-mail ("dm-thin discard issue"), I'm having trouble recovering from the metadata corruption state I got into. I'm using the latest userland tools cloned from https://github.com/jthornber/thin-provisioning-tools . Here's what I've tried; am I going wrong somewhere, or is there potentially an issue with the tools?
>
> Are you using the v1.5 tag? or just taking my latest dev?
>
> - Joe
>
I don't see a v1.5 tag -- I cloned straight from master.
Cheers,
Jim
prev parent reply other threads:[~2013-03-06 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1196562.58.1362575588488.JavaMail.javamailuser@localhost>
2013-03-06 13:26 ` potential dm-thin recovery issue Jim Minter
2013-03-06 14:27 ` thornber
2013-03-06 16:13 ` Jim Minter [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=51376B1A.2090201@redhat.com \
--to=jminter@redhat.com \
--cc=dm-devel@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.