On Jan 1, 2014, at 2:27 PM, Oliver Mangold <o.mang...@gmail.com> wrote:
> I fear, I broke my FS by running btrfsck. I tried 'btrfsck --repair' and it > fixed several problems but finally crashed with some debug message from > 'extent-tree.c', so I also tried 'btrfsck --repair --init-extent-tree'. It is sort of a (near) last restort, you know this right? What did you try before btrfsck? Did you set dmesg -n7, then mount -o recovery and if so what was recorded in dmesg? > > produces log messages: > > Jan 01 21:45:09 home kernel: btrfs: device fsid > 31a5d433-4f7b-49cc-9bc0-9422471f5194 devid 1 transid 4793 > /dev/mapper/primary-home > Jan 01 21:45:09 home kernel: btrfs: disk space caching is enabled > Jan 01 21:45:09 home kernel: parent transid verify failed on 2176851968 > wanted 4792 found 4793 > Jan 01 21:45:09 home kernel: parent transid verify failed on 2176851968 > wanted 4792 found 4793 > Jan 01 21:45:09 home kernel: btrfs: open_ctree failed If you previously tried -o recovery, before btrfsck did you try btrfs-zero-log and if so what were the results in console and in dmesg? Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
