From: Daniel Witzel <dannyboy48888@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: parent transid verify failures on 2.6.39
Date: Thu, 23 Jun 2011 18:26:03 +0000 (UTC) [thread overview]
Message-ID: <loom.20110623T202432-379@post.gmane.org> (raw)
In-Reply-To: 1308793398-sup-9234@shiny
I'm game for trying it, been waiting a good bit to recover, and i have spare
drives to save the data to. Just post the git link for it if it's different then
Chris Masons git tree.
next prev parent reply other threads:[~2011-06-23 18:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 22:42 parent transid verify failures on 2.6.39 Andrej Podzimek
2011-06-23 1:45 ` Chris Mason
2011-06-23 18:26 ` Daniel Witzel [this message]
2011-06-23 19:54 ` Josef Bacik
2011-06-23 21:11 ` Daniel Witzel
2011-06-23 21:35 ` Josef Bacik
2011-06-24 15:46 ` Daniel Witzel
2011-06-24 1:30 ` Andrej Podzimek
2011-06-28 15:46 ` Daniel Witzel
2011-06-28 16:44 ` Mitch Harder
2011-06-28 17:04 ` Daniel Witzel
2011-06-28 17:31 ` Daniel Witzel
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 19:06 Craig Johnson
2011-05-25 19:28 ` Josef Bacik
2011-05-25 19:32 ` Craig Johnson
2011-07-03 7:09 ` Skylar
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=loom.20110623T202432-379@post.gmane.org \
--to=dannyboy48888@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).