File Systems¶

This section provides information about the file systems at HPC2N. Since your home directory is per default quite small, you should keep files needed for your jobs in your project storage.

There are also instructions on how to compress and archive your data and other files.

The section ‘Filetransfer’ gives some information about how to do file transfers here at HPC2N.

Overview¶

$HOME¶

This is your home-directory (pointed to by the $HOME variable). It has a quota limit of 25GB per default. Your home directory is backed up regularly.

Since the home directory is quite small, it should not be used for most production jobs. These should instead be run from project storage directories.

To find the path to your home directory, either run pwd just after logging in, or do the following:

b-an01 [~/store]$ cd
b-an01 [~]$ pwd
/home/u/username
b-an01 [~]$

It is not generally possible to get more space in your home directory. You should generally use project storage instead. If you need more of that, the PI in your project should apply for it.

However, if you really need more space in your home directory, have your PI contact support@hpc2n.umu.se and include a good explanation of what you need the extra space for.

Project storage¶

Project storage is where a project’s members have the majority of their storage. It is applied for through SUPR, as a storage project. While storage projects needs to be applied for separately, they are usually linked to a compute project.

This is where you should keep your data and run your batch jobs from. It offers high performance when accessed from the nodes making it suitable for storage that are to be accessed from parallel jobs, and your home directory (usually) has too little space.

Project storage is located below /proj/nobackup/ in the directory name selected during the creation of the proposal.

Quota¶

The size of the storage depends on the allocation. There are small, medium, and large storage projects, each with their own requirements. You can read about this on SUPR. The quota limits are specific for the project as such, there are no user level quotas on that space.

There are actually 4 quota limits for the project storage space. Soft and hard limit for disk usage and soft and hard limit for the number of files. The hard limits are really hard limits. You can never go above them. You can be above the soft limit for a grace period, but after the grace period the soft limit will behave as a hard limit until you have gone below the soft limit again.

Misc¶

It is recommended to use the project’s storage directory for the projects data. Layout structure in that project directory is the responsibility of the project itself.

/scratch¶

Our recommendation is that you use the project storage instead of /scratch when working on Compute nodes or Login nodes.

On the computers at HPC2N there is a directory called /scratch. It is a small local area split between the user using the node and it can be used saving (temporary) files you create or need during your computations. Please do not save files in /scratch you don’t need when not running jobs on the machine, and please make sure your job removes any temporary files it creates.

When anybody need more space than available on /scratch, we will remove the oldest/largest files without any notices.

The size of /scratch depends on the type of nodes and that size is split between the number of cores that your job has on the node.

• Kebnekaise, standard compute nodes: ~170 GB
• Kebnekaise, GPU nodes: ~170 GB
• Kebnekaise, Largemem nodes: ~350 GB

SweStore - Nationally Accessible Storage¶

For data archiving and long-term storage we recommend our users to use the SweStore Nationally Accessible Storage. This is a robust, flexible and expandable long term storage system aimed at storing large amounts of data produced by various Swedish research projects.

For more information, see the documentation for SweStore available at docs.swestore.se.

Archiving and compressing¶

There are a number of options for archiving and compressing directories and files at HPC2N.

Note that in the below examples, $ and b-an01 [~]$ are bash prompts from the terminal and you should not write these.

tar (more information)¶

This program saves many files together into a single archive file, and it also restores individual files from the archive. Automatic archive compression/decompression options exists, as well as special features that allow tar to be used for incremental and full backups. The command tar –help will give the format (defaults to gnu). This is generally only important for files larger than 8 GB.

Examples¶

$ tar cvf myfile.tar myfile.txt 
myfile.txt

$ tar cvfz myfile.tar.gz myfile.txt 
myfile.txt

$ tar tvf myfile.tar
-rwxr-xr-x username/folk 23717 2009-10-02 15:48:48 myfile.txt

$ tar xvf myfile.tar
myfile.txt

$ tar xvfz myfile.tar.gz 
myfile.txt

$ tar cvfz mydir.tar.gz C/
C/
C/hello
C/hello.c
C/hello_submit

$ tar cvfz myfile.tar.gz *.c
calc.c
converting.c
hello.c

gzip (more information)¶

Compression utility designed as a replacement for compress, with much better compression and no patented algorithms. The standard compression system for all GNU software.

Examples¶

$ gzip myfile.txt

$ gunzip myfile.txt.gz 

bzip2 (more information)¶

Strong, lossless data compressor based on the Burrows-Wheeler transform. Also available as a library.

Examples¶

$ bzip2 myfile.txt

$ bunzip2 myfile.txt.bz2 

zip (more information)¶

Simple compression and file packaging utility. Note that the maximum size limit of a zip file is 4GB and if this size limit is exceeded, the file becomes prone to corruption. This further leads to failure of the extraction process and inaccessibility of your data.

Zip examples¶

$ zip myfile.zip myfile.txt 
  adding: myfile.txt (deflated 57%)

$ unzip myfile.zip
Archive:  myfile.zip
  inflating: myfile.txt              

$ zip -r mydir.zip C/
  adding: C/ (stored 0%)
  adding: C/hello (deflated 66%)
  adding: C/hello.c (deflated 3%)
  adding: C/hello_submit (deflated 24%)

$ zip -r my_c_files.zip . -i \*.c
  adding: hello.c (deflated 3%)
  adding: C/hello.c (deflated 3%)
  adding: converting.c (deflated 31%)
  adding: calc.c (deflated 5%)

Archiving/compressing on Windows¶

There are a number of Windows programs using the same formats. These are a few of the more popular ones:

• 7-Zip. Free Windows software package that can handle all the above formats.
• WinZip. Commercial Windows software package that can handle all the above formats.
• WinRAR. Commercial Windows software package that can handle all the above formats.

File transfer¶

There are several possible ways to transfer files and data to and from HPC2N’s systems.

The examples below mostly covers Linux and macOS. If you are transferring from a Windows system, then we have some information in the File transfers section under the Windows connection guide.

Note that in the below examples, $ and b-an01 [~]$ are bash prompts from the terminal and you should not write these.

Jump to specific section: [ FTP | SCP | SFTP | LFTP | rsync ]

FTP - NOT PERMITTED! ¶

FTP (File Transfer Protocol) is a simple data transfer mechanism. FTP is the original program for data transfer, but it was not designed for secure communications. FTP exists on the systems, but HPC2N does not permit connections using FTP because of the security problems. There are several modern FTP clients which support either SFTP or SCP which are similar, secure protocols for file transfer. Use one of those methods instead of FTP.

SCP ¶

SCP (Secure CoPy) is a simple way of transferring files between two machines that use the SSH (Secure SHell) protocol. You may use SCP to connect to any system where you have SSH (log-in) access. There are some graphical file transfer programs which offers SCP as protocol and it is also a command line program on most Linux, Unix, and Mac OS X systems. SCP can copy single files, but will also recursively copy directory contents if given a directory name.

Command-line usage

$ scp sourcefilename user@hostname:somedir/destfilename

$ scp irf.png user@machine.umu.se:C/irf.png
Password: 
irf.png                   100% 2100     2.1KB/s   00:00    

$ scp user@hostname:somedir/sourcefilename destfilename

$ scp user@machine.umu.se:irf.png irfpic.png
Password: 
irf.png                   100% 2100     2.1KB/s   00:00    

$ scp -r sourcedirectory/ user@hostname:somedir/

Installation

SFTP ¶

SFTP (SSH File Transfer Protocol or sometimes called Secure File Transfer Protocol) is a network protocol that provides file transfer over a reliable data stream. You may use SFTP to connect to most of HPC2N’s systems. SFTP is a command -line program on most Unix, Linux, and Mac OS X systems. It is also available as a protocol choice in some graphical file transfer programs. SFTP has more features than SCP and allows for other operations on remote files, such as remote directory listing, and it is also possible to resume interrupted transfers. Note, however, that command-line SFTP cannot recursively copy directory contents. If you need to do so, you must either use SCP or a graphical SFTP client.

Command-line usage

$ sftp -B buffersize user@hostname

Examples

enterprise-d [~]$ sftp user@kebnekaise.hpc2n.umu.se
Connecting to kebnekaise.hpc2n.umu.se...
user@kebnekaise.hpc2n.umu.se's password:
sftp> put file.c C/file.c
Uploading file.c to /home/u/user/C/file.c
file.c                          100%    1    0.0KB/s   00:00
sftp> put -P irf.png pic/
Uploading irf.png to /home/u/user/pic/irf.png
irf.png                         100% 2100    2.1KB/s   00:00
sftp>

sftp> get file2.c C/file2.c
Fetching /home/u/user/file2.c to C/file2.c
/home/u/user/file.txt  100%  1  0.1KB/s 00:00    
sftp> get -P file3.c C/
Fetching /home/u/user/file3.c to C/file3.c
/home/u/user/file.txt  100%  1  0.4KB/s 00:00    
sftp> exit
enterprise-d [~]$ 

The following two flags can be useful

• -B: optional, specify buffer size for transfer; larger may increase speed, but costs memory
• -P: optional, preserve file attributes and permissions

Regarding buffer size; in order to find a optimal buffer size, use the following formula:

optimal buffer size = 2 x bandwidth x delay

or

optimal buffer size = bandwidth x RTT

RTT = round trip time, which you get from ping, since delay is about ping average time/2.

ping average = 2.653 ms

See http://fasterdata.es.net/TCP-tuning/ for more information.

Installation

LFTP ¶

LFTP is a command-line file-transfer program for Linux and Unix systems. FTP, HTTP, FISH, SFTP, HTTPS and FTPS protocols. LFTP has additional features not provided by SFTP such as bandwidth throttling, transfer queues, and parallel transfers. It may be used interactively or scripted. Every operation in LFTP is reliable, that is any non-fatal error is handled and the operation is retried automatically. So if downloading breaks, it will be restarted from the point automatically.

In order to connect over SFTP to our resources, the username and hostname shall be prefixed by sftp://

LFTP has shell-like command syntax allowing you to launch several commands in parallel in background (&). It is also possible to group commands within () and execute them in background. All background jobs are executed in the same single process. You can bring a foreground job to background with ^Z (c-z) and back with command wait' (orfg’ which is alias to wait'). To list running jobs, use commandjobs’. With parallel transfers LFTP can be much faster than SCP or SFTP, so its use is encouraged when possible.

LFTP is simply a client, so it is not needed on the remote machine involved in a transfer (the remote system need only support SFTP).

Examples

lftp> cat file | gzip > file.gz
lftp> get file &

lftp> (cd /path && get file) &

The first command retrieves the file from the ftp server and passes its contents to gzip which in turn stores the compressed data to file.gz. Other commands show how to start commands or command groups in the background.

LFTP has a built in mirror which can download or update a whole directory tree. There is also reverse mirror (mirror -R) which uploads or updates a directory tree on server.

More interactive examples

$ lftp sftp://user@hostname

lftp :~> mget *.dat

lftp :~> put filename.dat

lftp :~> mirror --parallel=5 remotedir localdir/

lftp :~> mirror -R --parallel=8 localdir remotedir/

Batch usage

$ lftp sftp://user@hostname -e "mget *.dat"

$ lftp sftp://user@hostname -f transfer.lftp

rsync ¶

rsync is a utility for efficiently transferring and synchronizing files between a computer and a storage drive and across networked computers by comparing the modification times and sizes of files. It is commonly found on Unix-like operating systems and is under the GPL-3.0-or-later license.

rsync FLAGS source destination

Where source is the source directory, either on a local system, local disk, or remote system and destination is the destination directory on local or remote system or disk.

rsync has many useful flags, which you can find with the man rsync commmand. Here we will only cover the most common:

• -r: recursive
• -a: archive. It syncs recursively and preserves symbolic links, modification times, groups/owners, and permissions. Equivalent to -rlptgoD.
• -v: verbose
• -n: Check before running
• -z: Compress before transfer
• -P: Combines flags –progress (progress bar for tranfer) and –partial (resume interrupted tranfer of a file).
• --no-o: Do not preserve owner. Default unless you use -a. Useful if you have a different username on the remote and local system.
• --no-perms: Do not preserve permissions. Default unless you added -a.
• --no-links: Do note preserve symbolic links. Default unless you are using -a.

Examples

$ rsync -r dir1/ dir2

rsync -rlpt username@remote_host:sourcedir/ /path/to/localdir

$ rsync -a dir1/ dir2

$ rsync -a /path/to/localdir/ username@remote_host:destination_directory

$ rsync -a username@remote_host:/path/to/sourcedir/ /path/to/localdir

$ rsync -azP username@remote_host:/path/to/sourcedir/ /path/to/localdir

$ rsync -a --no-o --no-links --no-perms -v username@remote_host:/path/to/sourcedir/ /path/to/localdir