> On Dec 19, 2016, at 4:53 PM, Kent Overstreet <kent.overstreet@xxxxxxxxx> wrote: > >> On Mon, Dec 19, 2016 at 04:00:40PM -0500, Josef Bacik wrote: >> Ok that works fine in the short term for you, but ideally you wouldn't have >> to fix the test every time you wanted to run it on bcachefs. Do you have a >> suggestion of how to make this generic enough to support you as well without >> dd'ing the whole drive? Thanks, > > Yes, but it'd be a lot of work :) > > Change log-writes so that instead of replaying the log, you have it create a > block device representing that specific point in the log - and then service read > requests by looking them up however you like. So, it'd be just like mounting > snapshots. > > It might not be too difficult since we can deal with crappy performance or > memory usage here, but I don't know if it's really worth the effort. One thing I was definitely going to do is use the dm thin provisioning so I could snapshot between each check so we don't have to replay from the beginning every time we want to check a different mark. Replaying the whole thing is fine for small runs like the fsx thing, but when you want to say run fsstress for a minute and replay to every fua and fsck and mount it gets tedious fast. Thanks, Josef-- 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
