...
- We use these variables to provide some examples. The variables are optional. You can use your filenames directly. Please note that the variable for several files have to formatted differently, depending on the preferred access method.
- Single File
- F=/hs/store/users/2023/2023-11-30_liegmahl/home_edvs1.tgz
If you have special characters (e.g., spaces, brackets, ...) in your filename: Try to avoid them. Yes, really try to avoid thenthem (this is no joke)! However, if are forced to use special characters it will get nasty. You have
have to quote the filename and/or
protect the special characters and in the filename with "\": F="/hs/platforms/WORM/aircraft/polar6/macs/exdata/P6-244_ANT_23_24_2311300801/20231130-150529_[Record\ All]/111498_RGB/09835_041255631_500.macs".
and in addition you have to quote the ssh command correctly (see example)
- Please understand that support for this kind of "self-made problems" is very limited on our side. We officially only support recommended characters (e.g., https://www.forschungsdaten-bildung.de/dateien-organisieren)
- Directories
- D="/hs/store/users/2023/2023-11-30_liegmahl"
- Multiple Files (for saminfo.sh):
- Create a file containing all files you want to process: FL=<contains-one-file-per-line.txt> (one file per line)
- Copy the file to a specific hssrv2 server, e.g. hssrv2a: rsync $FL hssrv2a:/tmp/$FL (Hint: If $FL is located in your $HOME, there is no need to upload it
) - execute ssh hssrv2a saminfo.sh <option> -F/tmp/$FL (see examles below)
- Multiple Files (for RestAPI):
- DIR="store/users/2023/2023-11-30_liegmahl" # Note: no "/hs" here!
FC='"$DIR/home_edvs1.tgz","$DIR/isibhv_personal.tgz","$DIR/isipd_home_pd.tgz"'
- Single File
- Some additional tasks can be done with ssh hssrv2 saminfo.sh
| Access method & Task | RestAPI | ssh hssrv '...' (using CLI) | ssh hssrv 'saminfo.sh ...' (using RestAPI) |
|---|---|---|---|
filestat (everything/all) | eval $CURL -X GET $SERV/file?path="$F" eval $CURL -X PUT --data \'{\"path\":[$FC]}\' $SERV/batchfile | sls ls -D $F $"F"' # use -E to show show | ssh hssrv2 'saminfo.sh -ga -f'"$F" |
filestat (something) | eval $CURL -X GET $SERV/file?path="$F" | jq -r '. | {path, onlineblocks, flags, error}' | like above, but -gs instead of -ga | |
filestat (online/offline) | eval $CURL -X GET $SERV/file?path="$F" | jq -r .onlineblocks eval $CURL -X PUT --data \'{\"path\":[$FC]}\' $SERV/batchfile | jq -r '.infos[] | {path, onlineblocks}' | like above, but -go instead of -ga | |
stage | eval $CURL -X POST $SERV/request/stage?path="$F" eval $CURL -X PUT --data \'{\"path\":[$FC]}\' $SERV/request/batchstage | saminfo.sh -f'"$F" -Cstage | like above, but -s instead of -ga |
show scheduler state | eval $CURL -X GET $SERV/queues | -- | ssh hssrv2 saminfo.sh -S |
|
| ||
mkdir | -- | mkdir/hs/projects/<project>/newdir | -- |
release | release $F saminfo.sh -f'"$F" -Crelease |
| |
quota | ssh hssrv2 saminfo.sh -q | -- | |
Count number of (online/staging) files in directory | saminfo.sh -f"$D" -Ccount |
|
File flags
The RestAPI and saminfo.sh -g[s|a] provide file information as flags. You can decode them by adding -v1 or take a look into this table:
...