Latch Pods provides direct access to all files stored on Latch Data.
/ldata
.
You can also create a link to /ldata
in your home directory for easier access with the following command:
latch cp local_folder latch:///s3_folder
. If you are trying to copy large amount of data to Latch Data, see below/ldata
in the file browser.
os
module. For example, to list all files in a directory and to read a file in Latch Data, you can use the following code snippet:
/ldata
to a local scratch directory inside your Pod.
To efficiently copy large folders from /ldata
to a local directory, see the next section on latch cp
.
latch cp
for swift file copy between local and S3 buckets on Latch Datalatch cp
command to ensure optimal copying speed.
After S3 buckets are mounted to Latch Data, latch cp
can be used for copying
files and directories to any Latch location, including mounted S3 buckets.
For a comprehensive guide on how to copy data between Latch Data and Pods, please visit the documentation here.
latch cp
a local directory that has the same folder name as a folder inside your S3 bucket on Latch Data, latch cp
will overwrite that folder in your Latch Data. If this behavior is undesirable, it is recommended that you change the name of your local directory to not overlap with an existing folder in your S3 bucket./ldata
.
rsync
is not currently supported. The following command will throw an error:
latch cp
is currently the most effective alternative. However, it’s important to note that latch cp
copies entire directories between local and remote paths every time, instead of transferring only the differences.
latch cp
or via the interface on console.latch.bio/data.
Workaround: To get the most up-to-date content for /ldata
, write a fake new file to /ldata
(e.g. touch /ldata/new.txt
), which will trigger a refresh. Alternatively, you can also restart your Pod, which will restart the mount for FUSE.
latch cp
or via the interface on console.latch.bio/data.
Workaround: To get the most up-to-date content for /ldata
, restart the Ldata FUSE mount with:
/ldata
or there’s no data in that directory try re-mounting the filesystem with
latch rsync
to only copy the content differences between local directories and remote Latch directories.