This sounds mostly fine, although I have a couple of concerns:

1. Can you pick a more specific name that specifies what is being torrented? Like maybe dumptorrents or similar?

2. I don't know a ton about how torrents work, but will this drastically increase load on NFS other torrent peers sync with our copies? Or...

3. If you're planing to cache dumps locally to avoid NFS load, do you know how much space that will require?

+1 (pending on Andrew's questions)

Thanks for the comments @Andrew

• dumpstorrents sounds like a better name, agreed
• the concerns raised here suggest that it does increase NFS load, though perhaps not to a disruptive level, given how 'infrequently' new torrents would need to be generated? but,
• if cached locally, enough space to hold a few of the most recent dump/categories (300GB?) while the torrent is being generated

In T397861#10962913, @TheresNoTime wrote:

• the concerns raised here suggest that it does increase NFS load, though perhaps not to a disruptive level, given how 'infrequently' new torrents would need to be generated?

Bursts are the main concern here, and it sounds like you're describing something bursty! Is this something with a throttle you can configure?

In T397861#10964875, @Andrew wrote:

In T397861#10962913, @TheresNoTime wrote:

• the concerns raised here suggest that it does increase NFS load, though perhaps not to a disruptive level, given how 'infrequently' new torrents would need to be generated?

Bursts are the main concern here, and it sounds like you're describing something bursty! Is this something with a throttle you can configure?

mktorrent itself doesn't seem to have a way of throttling this, so initially I think I'll:

1. copy a dump from the dumps mount to the 'local disk'
2. run mktorrent on that
3. delete the copied dump
4. repeat

That sounds like it'll be less 'bursty' :)