In our experience, we tried the quota feature of condor and mounted loopback file systems before going to separate file system partitions. The separate file systems were the only thing that worked for us. Loopback file systems cause a huge performance hit. I would not recommend that. Also we found that the lag of the expressions often did not catch the disk full before it filled up.
From: htcondor-users-bounces@xxxxxxxxxxx [mailto:htcondor-users-bounces@xxxxxxxxxxx]
On Behalf Of John Lambert
I'm ssh keyless this weekend, so I can't check, but I believe I remember some we had discovered for this purpose. I'll take a look and let you know if I find anything.
Your other option, assuming these are UNIX machines, is to create some disk images with dd, and then mount them as loopback devices. If you used some sort of copy on write imaging (QEMU's qcow comes to mind) you could transfer the images, mount them as loopback devices with a precommand script and use that as your execute directory. Management of this system would likely be very difficult however.
On Saturday, March 30, 2013, Paul Brenner <paul.r.brenner@xxxxxx> wrote: