From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alex Elsayed <eternaleye@gmail.com>
Subject: Re: Kernel BUG on mounting BtrFS / after reboot
Date: Thu, 18 Feb 2010 17:38:22 +0000 (UTC)
Message-ID: <loom.20100218T183230-637@post.gmane.org>
References: <loom.20100212T220341-877@post.gmane.org> <20100217141813.GH29430@think> <loom.20100218T013258-629@post.gmane.org> <20100218150238.GL10559@think>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: linux-btrfs@vger.kernel.org
Return-path: <linux-btrfs-owner@vger.kernel.org>
List-ID: <linux-btrfs.vger.kernel.org>

Chris Mason <chris.mason <at> oracle.com> writes:

> 
> Ugh ok.  The first thing I'd like to do is give you a patch to
> completely disable the tree log replay and give you the chance to backup
> critical data.
> 
> Do you already have a backup of the critical things on this drive?  The
> problem you're hitting is that tree-logging code is trying to replay an
> fsync of a file, but it can't find the file to replay.  This could be a
> small and localized corruption or it could be a larger problem.  We'll
> have to fix things one at a time to figure it out.
> 
> The easiest way to move forward would be to save a complete copy of the
> FS with dd, but that's probably not very easy given the size.
> 
> -chris

Well, I ran badblocks on the drive, and it was happily silent, so that's a good 
sign. I alo attached btrfsck output upthread, which says that there are 44 
inodes with errors. Unfortunately, I don't really have a drive big enough to 
back up to. I may be able to borrow one from a friend, though.