Jaime, That’s heavily workload dependent. We run a traditional HPC cluster and have a 7 day grace on home and 14 days on scratch. By setting the soft and hard limits appropriately we’ve slammed the door on many a runaway user / group / fileset. YMMV… Kevin On Jul 31, 2017, at 3:03 PM, Jaime Pinto <pinto at scinet.utoronto.ca<mailto:pinto at scinet.utoronto.ca>> wrote: If your grace period is set to 7 days I can assure you that in an HPC environment it's the equivalent of not having quotas effectively. You should set it to 2 hours or 4 hours. In an environment such as ours a runway process can easily generate 500TB of data or 1 billion inodes in few hours, and choke the file system to all users/jobs. Jaime — Kevin Buterbaugh - Senior System Administrator Vanderbilt University - Advanced Computing Center for Research and Education Kevin.Buterbaugh at vanderbilt.edu<mailto:Kevin.Buterbaugh at vanderbilt.edu> - (615)875-9633 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170731/afc44c76/attachment.html>