
I found I was subscribed to luv-main with a slightly incorrect address (different to what I was emailing as)... anyway...
parent transid verify failed on 699477344256 wanted 11799 found 12458
My btrfs lasted about a week before this happened.
I'm googling around to see what my options are... I have a btrfs send backup of my main subvolume but would lose a bunch of mythtv recordings that I'd rather keep.
Any suggestions appreciated!
All fixed. I restored from the btrfs send backup, and before I did that I copied my mythtv recordings off, and nothing appears to have been lost (although they could all be corrupt... copying them back now). The mysql database appears intact too, even though it would have been active right up until it crashed. The send/receive functions of btrfs are awesome. I have never seen an easier way of recovering before. The send/receive is well documented, but not the actual recovery when things go bad. I ended up re-creating a completely new btrfs volume and receiving the backup into that, which means the UUID's are different etc which is only a bit of a nuisance. I still don't know exactly what triggered the failure. My best guess is bcache, which was documented as not playing nicely with btrfs late last year (http://thread.gmane.org/gmane.comp.file-systems.btrfs/31018), although I'm not seeing any of those particular errors. I was using bcache in writeback mode, but switched back to writethrough for now. James