From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Cronenworth <mike@cchtml.com>
Subject: Re: Honest timeline for btrfsck
Date: Thu, 25 Aug 2011 10:06:32 -0500
Message-ID: <4E5664F8.9090802@cchtml.com>
References: <CAGh96GFhVEfXt=xcb-uGEBA3Ss2fc8BwOpJ2g8tXbm+VimdH3Q@mail.gmail.com> <1312404713-sup-6548@shiny> <loom.20110818T030824-742@post.gmane.org> <1313700115-sup-2457@shiny>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
To: Chris Mason <chris.mason@oracle.com>
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <1313700115-sup-2457@shiny>
List-ID: <linux-btrfs.vger.kernel.org>

Chris Mason wrote:
> There are always bugs to fix, and I have #1 and #2 mostly ready.  I had
> hoped to get #1 out the door before I left on vacation and I still might
> post it tonight.

Hi Chris,

Is there an update on this? I don't see any new code for 
btrfs-progs-unstable, but I might be looking in the wrong place.

Will this fsck tool be able to handle problems such as:
"parent transid verify failed on # wanted # found #" ?

Thanks,
Michael