Excerpts from Leon MeÃner's message of 2011-03-15 13:26:17 -0400: > On Tue, Mar 15, 2011 at 12:58:43PM -0400, Chris Mason wrote: > > Excerpts from Leon MeÃner's message of 2011-03-14 20:28:56 -0400: > > > Hi, > > > > > > i'm having a problem with a damaged btrfs after power loss. When i try > > > to mount the fs mount either segfaults (trace at bottom) or hangs in > > > "D" state together with [btrfs-transacti]. > > > > > > Please CC me as i'm not an the list. > > > # btrfsck -s 1 /dev/sdb2 > > > > Does btrfsck /dev/sdb2 work? -s 1 selects a different super, hopefully > > all the supers are the same. If plain btrfsck runs without failing we > > can easily work around the log tree crash. > > Yes it does (i think), output is below. > > # btrfsck /dev/sdb2 > root 256 inode 257 errors 800 > found 50907959296 bytes used err is 1 > total csum bytes: 46730092 > total tree bytes: 407293952 > total fs tree bytes: 315609088 > btree space waste bytes: 111966302 > file data blocks allocated: 184320000000 > referenced 56142348288 > Btrfs v0.19-35-g1b444cd Ok, if you have the latest btrfs-progs from git, you can make btrfs-zero-log ./btrfs-zero-log /dev/xxx It will make you skip the log replay that is crashing the box on your next mount. -chris -- 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
