Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
doku:binf_nodes [2017/08/22 09:59] jz [Submitting Jobs] |
doku:binf_nodes [2017/09/01 13:51] (current) ir [Quotas / How to get more diskspace] |
||
---|---|---|---|
Line 37: | Line 37: | ||
</ | </ | ||
- | Please note that one has to include the --mount=/ | + | Please note that one has to include the --mount=/ |
- | + | ||
- | Additional info on BeeGFS quotas can be found [[https:// | + | |
+ | For additional info refer to [[https:// | ||
==== Available filesystems ==== | ==== Available filesystems ==== | ||
- | The binf nodes export 2 mountpoints which are '' | + | The binf nodes export 2 mountpoints which are '' |
- | If you need much space then you should use the BINFL filesystem, which is 10 times larger than BINFS. | + | If you need much space then you should use the '' |
- | Please keep in mind that BINFS has no redundancy and is seen as fast scratch space. A hardware defect can (and most probably will, and already has) lead to a situation where the whole file systems gets reinitialised, | + | Please keep in mind that '' |
==== Submitting Jobs ==== | ==== Submitting Jobs ==== | ||
Line 86: | Line 85: | ||
==== Pitfalls ==== | ==== Pitfalls ==== | ||
- | * Distributed file systems do not perform well when it comes to random I/O. If you need to do random I/O it would be best to first copy your data into the main memory of the node that is working on the data and do the random I/O in the main memory. To accomplish this you could either use the $TMP filesystem or use the [[http:// | + | * Distributed file systems do not perform well when it comes to random I/O. If you need to do random I/O it would be best to first copy your data into the main memory of the node that is working on the data and do the random I/O in the main memory. To accomplish this you could either use the '' |