I am wondering where Slurm is getting the "0" value from that I see in the error...
I went spelunking in the 16.05 source for "count too low", and I found the string in ./src/common/gres.c beginning at line 2045: if ((fast_schedule < 2) && (gres_data->gres_cnt_found < gres_data->gres_cnt_config)) { if (reason_down && (*reason_down == NULL)) { xstrfmtcat(*reason_down, "%s count too low (%"PRIu64" < %"PRIu64")", context_ptr->gres_type, gres_data->gres_cnt_found, gres_data->gres_cnt_config); } rc = EINVAL; } Where is the "gres_cnt_found" value is being calculated from? -----Original Message----- From: Will Dennis Sent: Thursday, March 21, 2019 11:13 PM To: slurm-users@lists.schedmd.com Subject: RE: [slurm-users] Can one specify attributes on a GRES resource? Yes, all the nodes with those GRES types have a gres.conf with those names/counts set... -----Original Message----- From: slurm-users [mailto:slurm-users-boun...@lists.schedmd.com] On Behalf Of Chris Samuel Sent: Thursday, March 21, 2019 10:47 PM To: slurm-users@lists.schedmd.com Subject: Re: [slurm-users] Can one specify attributes on a GRES resource? On 21/3/19 7:39 pm, Will Dennis wrote: > Why does it think that the "gres/gpu_mem_per_card" count is 0? How can I fix > this? Did you remember to distribute gres.conf as well to the nodes? -- Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA