On Aug 14, 2014, at 11:27 AM, Marc MERLIN <[email protected]> wrote: > On Thu, Aug 14, 2014 at 12:52:35PM -0400, Austin S Hemmelgarn wrote: >> I don't think it is likely that the Samsung SSD is to blame, in my >> experience Samsung's SSD's are better than almost every other brand >> except Intel, and I know that they honor write-barriers correctly. >> The likely issue is that the system hung during the process of a commit, >> which is one of the few things that I know of that consistently corrupts >> the filesystem. There isn't really anything I know of to prevent it, >> except for making your system as stable as possible. >> Interestingly, this type of thing is the only issue I've ever had with >> BTRFS that wasn't traceable to hardware problems. > > That was my understanding too, thanks for confirming. > > Until this bug gets fixed, I'm perplexed as to why btrfs-zero-log isn't > fixing this. > Can't I unroll the last commits until I get to a stable one?
What do you get for btrfs-debug-tree -R <dev> Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
