Eeesh these are older than I thought, I pushed to https://github.com/josefbacik/fstests.git. The fsx work is there and is generic, the fsstress one has some btrfs specific stuff but you can just pull that crap out and it'll work on anything. Let me know if you need anything else, thanks, Josef Sent from my iPhone > On Dec 18, 2016, at 3:46 PM, Kent Overstreet <kent.overstreet@xxxxxxxxx> wrote: > >> On Sun, Dec 18, 2016 at 03:38:54PM -0500, Josef Bacik wrote: >> On Sun, Dec 18, 2016 at 3:12 PM, Kent Overstreet <kent.overstreet@xxxxxxxxx> >> wrote: >>> On Thu, Dec 15, 2016 at 04:15:27AM +0000, Josef Bacik wrote: >>>> dm-log-writes is probably what you want. Thanks, >>> >>> Oh, that actually looks pretty cool. >>> >>> Don't suppose anyone is working on making use of it in xfstests? >> >> Actually I had two xfstests, one that used fsstress and just made sure every >> commit point was valid (every FUA/FLUSH it found in the log) and then one >> that modified fsx to output a known good image every time it ran fsync and >> mark the log to make sure fsync did the correct thing. I need to go back >> and clean them up and get the upstream, but I've been pretty heavily >> distracted with other things for the last year or two. I'll make getting >> those upstream a priority after Christmas. Thanks, > > Don't suppose you could throw up just what you've currently got somewhere? It'd > save me some work. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
