You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the upgrade we started to see exhausted disk errors when we tried to schedule a job:
But the node has enough free storage. If we observe the nomad node status:
As you can see, nomad uses / instead of /var to calculate allocable space. /var/ was used in 1.5.6. But in unique attributes is fingerprinting the right FS
How can I solve that? I didn't see in the release notes something related with this.
The text was updated successfully, but these errors were encountered:
Hi,
After upgrading our nodes from 1.5.6 -> 1.9.5 we observed differences in storage allocated resources.
We have 2 partitions on our hosts
/
for the OS/var/
for the tasksthis is the storage free:
our data_dir is pointing to /var/nomad . Our config looks like:
After the upgrade we started to see
exhausted disk
errors when we tried to schedule a job:But the node has enough free storage. If we observe the nomad node status:
As you can see, nomad uses
/
instead of/var
to calculate allocable space. /var/ was used in 1.5.6. But in unique attributes is fingerprinting the right FSHow can I solve that? I didn't see in the release notes something related with this.
The text was updated successfully, but these errors were encountered: