LSF is usually used in networks with shared file space. When shared file space is not available, use the bsub -f command to have LSF copy needed files to the execution host before running the job, and copy result files back to the submission host after the job completes.
LSF attempts to run the job in the directory where the bsub command was invoked. If the execution directory is under the user’s home directory, sbatchd looks for the path relative to the user’s home directory. This handles some common configurations, such as cross-mounting user home directories with the /net automount option.
If the directory is not available on the execution host, the job is run in /tmp. Any files created by the batch job, including the standard output and error files created by the -o and -e options to bsub, are left on the execution host.
LSF provides support for moving user data from the submission host to the execution host before executing a batch job, and from the execution host back to the submitting host after the job completes. The file operations are specified with the -f option to bsub.
LSF uses the lsrcp command to transfer files. lsrcp contacts RES on the remote host to perform file transfer. If RES is not available, the UNIX rcp command is used. If LSF_REMOTE_COPY_COMMAND is specified in lsf.conf, lsrcp uses that command and any options to transfer files instead.
The -f "[local_file operator [remote_file]]" option to the bsub command copies a file between the submission host and the execution host. To specify multiple files, repeat the -f option.
File name on the submission host.
File name on the execution host.
The files local_file and remote_file can be absolute or relative file path names. You must specify at least one file name. When the file remote_file is not specified, it is assumed to be the same as local_file. Including local_file without the operator results in a syntax error.