Hi,
I have tried this before and I would like to temper your expectations.
If you use a placement policy to allow users to write any files into your
"small" pool (e.g. by directory), they will get E_NOSPC when your small
pool fills up. And they will be confused because they can't see the pool
Hi Scale-folk.
I have an IBM ESS GH14S building block currently configured for my HPC
workloads.
I've got about 1PB of /scratch filesystem configured in mechanical spindles via
GNR and about 20TB of SSD/flash sitting in another GNR filesystem at the
moment. My intention is to destroy that
