On Wed, Aug 22, 2012 at 10:19:13AM -0700, Not Zippy wrote:

The full output of the btrfs-debug-tree is 190MB compressed, did you
want it still ?

That's not the biggest one I've received :) (2.5G xz compressed) Please
note that it contains filenames, so you may want to filter them out
with

sed -e 's/\(.* name: \).*/\1FILENAME/'

(though sometimes the filename can be useful to give further hints).

As far as the conditions, I was running a repo sync which I had
CTRL-Z, I then got distracted and mistakenly started the sync again
(not sure if you are familiar with repo command, it spawns git
processes to checkout project). The crash did not occur immediately
but it was probably within 2 minutes of me starting this second repo
sync. The lock up was bad enough that BUSIER did not reboot the PC, I
had to power down.

Thanks. Does not seem to be doing anything special and uncommon. The
hard power off could have caught the filesystem in some intermediate
state (ie. a bug to resolve, this should not happen) or the disk wrote
bad data. smartctl may show if there are hard erros on the disk.

After the patch to btrfsck, I got this error:

# ./work/builds/btrfs-progs/btrfsck --repair /dev/sda2

[...]

I'm afraid that the corrupted block confuses fsck too much.

david