rsnt_translations
56,420
edits
Frequently Asked Questions: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 155: | Line 155: | ||
<!--T:30--> | <!--T:30--> | ||
Now, depending on how you copy your files, what software you use, that software either will respect the ownership of the directory and apply the correct group, or it may insist on retaining the ownership of the source data. In the latter case you will have a problem like you have now. | Now, depending on how you copy your files, what software you use, that software either will respect the ownership of the directory and apply the correct group, or it may insist on retaining the ownership of the source data. In the latter case, you will have a problem like you have now. | ||
<!--T:31--> | <!--T:31--> | ||
| Line 174: | Line 174: | ||
<!--T:59--> | <!--T:59--> | ||
One of these strings may appear in the "Reason" field of <tt>squeue</tt> output for a waiting | One of these strings may appear in the "Reason" field of <tt>squeue</tt> output for a waiting y-cjob, and is new to Slurm 19.05. | ||
They mean one or more of the nodes Slurm considered for the job are down, or deliberately taken offline, | They mean one or more of the nodes Slurm considered for the job are down, or deliberately taken offline, | ||
or are being reserved for other jobs. On a large busy cluster there will almost always be such nodes. The messages mean | or are being reserved for other jobs. On a large busy cluster, there will almost always be such nodes. The messages mean | ||
effectively the same thing as the reason "Resources" that appeared in Slurm version 17.11. However, these are not | effectively the same thing as the reason "Resources" that appeared in Slurm version 17.11. However, these are not | ||
error messages; jobs submitted are actually in the queue and will eventually be processed. | error messages; jobs submitted are actually in the queue and will eventually be processed. | ||
== How accurate is START_TIME in <tt>squeue</tt> output? == <!--T:33--> | == How accurate is START_TIME in <tt>squeue</tt> output? == <!--T:33--> | ||
We don't show the start time by default with <tt>squeue</tt>, but it can be printed with an option. The start times Slurm forecasts depend on rapidly | We don't show the start time by default with <tt>squeue</tt>, but it can be printed with an option. The start times Slurm forecasts depend on rapidly changing conditions, and are therefore not very useful. | ||
<!--T:34--> | <!--T:34--> | ||
[[Running jobs|Slurm]] computes START_TIME for high-priority pending jobs. These expected start times are computed from currently | [[Running jobs|Slurm]] computes START_TIME for high-priority pending jobs. These expected start times are computed from currently available information: | ||
* What resources will be freed by running jobs that complete; and | * What resources will be freed by running jobs that complete; and | ||
* what resources will be needed by other, higher-priority jobs waiting to run. | * what resources will be needed by other, higher-priority jobs waiting to run. | ||
| Line 209: | Line 209: | ||
==How to fix library not found error== <!--T:54--> | ==How to fix library not found error== <!--T:54--> | ||
When installing | When installing precompiled binary packages in your <code>$HOME</code>, they may fail with an error such as <tt>/lib64/libc.so.6: version `GLIBC_2.18' not found</tt> at runtime. See [[Installing_software_in_your_home_directory#Installing_binary_packages|Installing binary packages]] for how to fix this kind of issue. | ||
== How do you handle sensitive research data? == <!--T:64--> | == How do you handle sensitive research data? == <!--T:64--> | ||