TheCheater

No, this pool that I'm suggesting wouldn't be directly tied to any other pool or the main array but the way that it should work would be to act as temporary storage for any file inbound to the unraid server regardless of the destination (array/other pools) and as soon as a file gets fully copied on it the mover would immediately transfer it to it's destination (array/pool). Doing this way and using fast nvme drives you could basically throw at your server "any" amount of data (given you use big enough drives) at the maximum speed the ethernet connection would allow without the need to have a huge ssd pool tied to the array. The special pool that I'm suggesting wouldn't be mutaually exclusive with the current implementation of pools and array but would be active system wise something like this:

Browsing this forum I've seen that a tiered storage (pool 1 -> pool 2 -> ... -> array) with all the relevant mover functions (promote/demote files based on usage etc...) has already been requested multiple times so please consider this part as a "+1" by me. Other than that the feature that I would love to see implemented is the ability to create a pool solely assigned to boosting write speed while ingesting new data on the server. The way I envision this "Write cache pool" is that, once we assign one or more drives to this pool, it would only be used to receive incoming data without any form of retention so as soon as a file transfer is completed (or the write cache is full) the mover would immediately empty the write cache to the relevant actual storage of pools + array. Given that this pool shouldn't ever hold any data on it apart for the time needed to receive it and to move it away it should ideally be set up as striped storage across as many drives we assign to this pool to maximize the throughput during the ingest operations to fully leverage 10g+ networks. To summarize the order of operations would be: network interface --------> write cache pool (striped and emptied ASAP) --------> pool + array storage (current implementation)

I second this, I'm also going to use this case for my tower and a matching icon would be nice