Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

At any given time, the set of login and data-mover nodes that are accessible may be determined by running the following commands from a terminal session on whichever login or data-mover node you have logged into

Code Block
languagetext
username@setonix-06:~> dig @150.229.2.5 setonix.pawsey.org.au  +noall +answer
setonix.pawsey.org.au.  3600    IN      A       146.118.12.26
setonix.pawsey.org.au.  3600    IN      A       146.118.12.27
setonix.pawsey.org.au.  3600    IN      A       146.118.12.22
username@setonix-06:~>
username@setonix-06:~> nslookup 146.118.12.26 150.229.2.5
26.12.118.146.in-addr.arpa      name = setonix-05.pawsey.org.au.
username@setonix-06:~>
username@setonix-06:~> nslookup 146.118.12.27 150.229.2.5
27.12.118.146.in-addr.arpa      name = setonix-06.pawsey.org.au.
username@setonix-06:~>
username@setonix-06:~> nslookup 146.118.12.22 150.229.2.5
22.12.118.146.in-addr.arpa      name = setonix-01.pawsey.org.au.
username@setonix-06:~>

...

The following example shows the commands to obtain the list of names for the currently available data-mover nodes, having logged into setonix-dm01

Code Block
languagetext
username@setonix-dm01:~> dig @150.229.2.5 data-mover.pawsey.org.au  +noall +answer
data-mover.pawsey.org.au. 3600  IN      A       146.118.74.161
data-mover.pawsey.org.au. 3600  IN      A       146.118.74.160
data-mover.pawsey.org.au. 3600  IN      A       146.118.74.163
data-mover.pawsey.org.au. 3600  IN      A       146.118.74.162
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.161 150.229.2.5
161.74.118.146.in-addr.arpa      name = setonix-dm02.pawsey.org.au.
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.160 150.229.2.5
160.74.118.146.in-addr.arpa      name = setonix-dm01.pawsey.org.au.
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.163 150.229.2.5
163.74.118.146.in-addr.arpa      name = setonix-dm04.pawsey.org.au.
username@setonix-dm01:~>
username@setonix-dm01:~> nslookup 146.118.74.162 150.229.2.5
162.74.118.146.in-addr.arpa      name = setonix-dm03.pawsey.org.au.
username@setonix-dm01:~>

...

Excerpt

Home is often used by a variety of programs use store configuration files and directories along with some cached information. These directories can contain many files and use up quite a bit of storage. An example is vscode, which stores quite a bit of data within the .vscode-server  directory located in $HOME . This directory can contain upwards of 1000 files and use on the order of 100 MB. This will impact your quota on home. We recommend moving such directories to a "fakeHome" directory in: /software/projects/<project>/<username>/fakeHome. Then generate a symbolic link in $HOME that points to the corresponding directory:

Column


Code Block
languagebash
themeDJango
titleTerminal X. Setting .vscode-server directory out of the HOME directory
$ mkdir -p $MYSOFTWARE/fakeHome
$ cp mv-r $HOME/.vscode-server $MYSOFTWARE/fakeHome             # if .vscode_server dir alreadyinitially exists in your $HOME 
$ mkdirrm -pr $MYSOFTWARE/fakeHome$HOME/.vscode-server        # if .vscode_server does not exist yet in your $HOME $ cd $HOME $ ln -s $MYSOFTWARE/ # if .vscode_server dir initially exists in $HOME
$ mkdir -p $MYSOFTWARE/fakeHome/.vscode-server      # if .vscode_server did #not generateinitially aexisted symbolicin link$HOME
(make$ sureln you are in $HOME)-s $MYSOFTWARE/fakeHome/.vscode-server $HOME/.vscode-server       # generate a symbolic link


Note that we are using cp + rm and not mv to transfer the .vscode-server directory to another filesystem in order to get the right ownership of files in the new filesystem and remove their original ownership that is consuming the $HOME quota, otherwise the quota of the transferred files would still be assigned to $HOME quota.

Further explanation of quotas can be found in Pawsey Filesystems and their Use.

Related pages

External links