On Sat, Jul 16, 2011 at 3:51 AM, mck <mick@xxxxxxxxx> wrote: > My laptop btrfs partition has become corrupt after a power+battery > outage. > > # btrfs-show > Label: none uuid: e7b37e5d-c704-4ca8-ae7e-f22dd063e165 > Total devices 1 FS bytes used 116.33GB > devid 1 size 226.66GB used 226.66GB path /dev/sda4 > > I typically mount w/ > -o subvol=xyz,compress,noatime,nodiratime > and take snapshots of (some) subvolumes at every boot. > (not that these snapshots seem to be of much use now). > > Now: > btrfsck gives loads of "root x inode y errors 400" and finishes w/ > found 124906840074 bytes used err is 1 > total csum bytes: 117696892 > total tree bytes: 4385128448 > total fs tree bytes: 3926626304 > btree space waste bytes: 1078295916 > file data blocks allocated: 3619739602944 > referenced 162976624640 > Btrfs Btrfs v0.19 > does btrfsck -s1 complete without error? If yes, you can try btrfs-select-super. > > mounting always results in the crash > > [ 6977.513528] Call Trace: > [ 6977.513542] [<ffffffffa057ac18>] replay_one_dir_item+0x88/0xb0 [btrfs] > [ 6977.513557] [<ffffffffa057d5b3>] replay_one_buffer+0x223/0x330 [btrfs] > [ 6977.513573] [<ffffffffa056a8ba>] ? alloc_extent_buffer+0x7a/0x420 [btrfs] > [ 6977.513584] [<ffffffffa057c139>] walk_down_log_tree+0x339/0x480 [btrfs] > [ 6977.513595] [<ffffffffa057c375>] walk_log_tree+0xf5/0x230 [btrfs] > [ 6977.513606] [<ffffffffa057f1c1>] btrfs_recover_log_trees+0x221/0x310 [btrfs] if there's something mentioning "log", I'd try btrfs-zero-log first. It's not built by default, so you should run "make btrfs-zero-log" on btrfs-tools source directory. -- Fajar -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
