From 986d509dfc2890886bbd4d85e16fb55063efebf6 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Fri, 8 Nov 2024 13:35:43 +0100
Subject: [PATCH] Be more precise
---
doc.zih.tu-dresden.de/docs/jobs_and_resources/capella.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/capella.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/capella.md
index c748b03ce..2520566c1 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/capella.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/capella.md
@@ -69,7 +69,9 @@ Although all other [filesystems](../data_lifecycle/workspaces.md)
Please utilize the new filesystem `cat` as the working filesystem on `Capella`. It has limited
capacity, so we advise you to only hold hot data on `cat`.
To transfer input and result data from and to the filesystems `horse` and `walrus`, respectively,
- you will need to use the [Datamover nodes](../data_transfer/datamover.md).
+ you will need to use the [Datamover nodes](../data_transfer/datamover.md). Regardless of the
+ direction of transfer, you should pack your data into archives (,e.g., using `tar` command)
+ for the transfer.
**Do not** invoke data transfer to the filesystems `horse` and `walrus` from login nodes.
Both login nodes are part of the cluster. Failures, reboots and other work during the
--
GitLab