From: Hugo Mills <hugo@carfax.org.uk>
To: Francesco R <vivo75@gmail.com>
Cc: Daniel Witzel <dannyboy48888@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [HELP!] parent transid verify failed on 600755752960 wanted 757102 found 756726
Date: Wed, 22 Jun 2011 19:45:05 +0100 [thread overview]
Message-ID: <20110622184505.GA3837@carfax.org.uk> (raw)
In-Reply-To: <BANLkTikrDb4dGjgSi=1OOaLLcffmrdaLTA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
On Tue, Jun 21, 2011 at 05:01:53PM +0200, Francesco R wrote:
> 2011/6/21 Daniel Witzel <dannyboy48888@gmail.com>:
> > Welcome to the club, I have a similar issue. We pretty much have to wait for the
> > fsck tool to finish being developed. If possible unhook the drives and leave
> > them be until the tool is done. I don't know when it will be done as I am not a
> > developer, mearly a follower.
> >
>
> There are tools to view the metadata stored as raid10? possibly in
> high level language?
>
> I see Chris Mason stopped git commits to btrfs-progs-unstable in 2010,
> there is someone working on it?
There have been lots of commits and patches since then. The "tmp"
branch contains a bunch of commits from Chris, and the
"integration-20110616" branch in my git repository[1] contains more or
less all of the other patches that have made it to this mailing list
since.
Sadly, none of them contain the new btrfsck code. :(
Hugo.
[1] http://git.darksatanic.net/repo/btrfs-progs-unstable.git/
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- There are three mistaiks in this sentance. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-06-22 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:10 [HELP!] parent transid verify failed on 600755752960 wanted 757102 found 756726 Francesco R
2011-06-21 14:01 ` Daniel Witzel
2011-06-21 15:01 ` Francesco R
2011-06-22 18:45 ` Hugo Mills [this message]
2011-06-22 19:29 ` Daniel Witzel
2011-06-22 22:01 ` Andrej Podzimek
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=20110622184505.GA3837@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=dannyboy48888@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=vivo75@gmail.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