So since Time Machine has migrated to APFS we have a situation where the entire TM volume is read-only to a regular admin user. That makes sense for a lot of reasons, but it also means benchmarking a TM disk “in situ” has become difficult, say if you’re suspecting the disk is not performing so well and you want to check details.
Now TM does put a lot of information out to unified log (the “new” console log system), and that includes transfer rates, but it all pertains to TM performance, not necessarily a proxy for raw disk performance. So if you’re looking for something else that a benchmarking tool gives you, that tool likely needs write access to the TM volume, which we no longer have.
Are there any simple workarounds? I already tried removing the disk from TM, which works, but it doesn’t magically make the disk writable. Any other ideas? Obviously there’s more drastic measures (clone, remove from TM, format, benchmark, clone back, add to TM) and if you were better prepared ahead of time you could account for this as well (when setting up TM disk create second container on same disk, use one for TM and the other for benchmarking), but I was hoping there might be some little trick I could use to allow the benchmark to just run in place, without too much kerfuffle.