Update while telko

doc.zih.tu-dresden.de/docs/jobs_and_resources/migration_to_barnard.md

@@ -210,7 +210,7 @@ target filesystems.
     ```
 
     Please refer to the table holding the settings
-    (cf. [subection workspaces on Barnard](#workspaces-on-barnard)) for the max. duration and
+    (cf. [subsection workspaces on Barnard](#workspaces-on-barnard)) for the max. duration and
     `ws_allocate --help` for all available options.
 
 ??? "Migration to work filesystem `/data/horse`"
@@ -221,19 +221,31 @@ target filesystems.
         `dtmv` instead of `dtcp` since this data has already been copied to a special directory on
         the new `horse` filesystem. Thus, you just need to move it to the right place (the Lustre
         metadata system will update the correspoding entries).
+     FIX: workspaces are within the subdirectories `ws/0` and `ws/1`, respectively. A corresponding
 
         ```console
-        marie@barnard$ dtmv /data/horse/lustre/scratch2/0/marie-numbercrunch /data/horse/ws/marie-numbercrunch
+        marie@barnard$ dtmv /data/horse/lustre/scratch2/0/marie-numbercrunch/<useful data> /data/horse/ws/marie-numbercrunch/
+        ```
+
+        We are synchronizing this (**last: October 18**) to `/data/horse/lustre/scratch2/`.
+
+        Please do **NOT** copy those data yourself. Instead check if it is already sychronized
+        to `/data/horse/lustre/scratch2/ws/0/marie-numbercrunch`.
+
+        In case you need to update this (Gigabytes, not Terabytes!) please run `dtrsync` like in
+
+        ```
+        marie@barnard$ dtrsync -a /data/old/lustre/scratch2/ws/0/marie-numbercrunch/<useful data>  /data/horse/lustre/scratch2/ws/0/marie-numbercrunch/
         ```
 
     === "Source: old `/ssd`"
 
         The old `ssd` filesystem is mounted at `/data/old/lustre/ssd` on the datamover nodes and the
-        workspaces are within the subdirectory `ws/`. A corresponding data transfer using `dtcopy`
+        workspaces are within the subdirectory `ws/`. A corresponding data transfer using `dtcp`
         looks like
 
         ```console
-        marie@barnard$ dtcp --recursive /data/old/lustre/ssd/ws/marie-numbercrunch /data/horse/ws/marie-numbercrunch
+        marie@barnard$ dtcp --recursive /data/old/lustre/ssd/ws/marie-numbercrunch/<useful data> /data/horse/ws/marie-numbercrunch/
         ```
 
     === "Source: old `/beegfs`"
@@ -243,7 +255,7 @@ target filesystems.
         data transfer using `dtcp` looks like
 
         ```console
-        marie@barnard$ dtcp --recursive /data/old/beegfs/ws/0/marie-numbercrunch /data/horse/ws/marie-numbercrunch
+        marie@barnard$ dtcp --recursive /data/old/beegfs/ws/0/marie-numbercrunch/<useful data> /data/horse/ws/marie-numbercrunch/
         ```
 
 ??? "Migration to `/data/walrus`"
@@ -252,30 +264,41 @@ target filesystems.
 
         The old `scratch` filesystem is mounted at `/data/old/lustre/scratch2` on the datamover
         nodes and the workspaces are within the subdirectories `ws/0` and `ws/1`, respectively. A
-        corresponding data transfer using `dtcopy` looks like
+        corresponding data transfer using `dtcp` looks like
 
         ```console
-        marie@barnard$ dtcp --recursive /data/old/lustre/scratch2/ws/0/marie-numbercrunch /data/walrus/ws/marie-numbercrunch
+        marie@barnard$ dtcp --recursive /data/old/lustre/scratch2/ws/0/marie-numbercrunch/<useful data> /data/walrus/ws/marie-numbercrunch/
+        ```
+
+        We are synchronizing this (**last: October 18**) to `/data/horse/lustre/scratch2/`.
+
+        Please do **NOT** copy those data yourself. Instead check if it is already sychronized
+        to `/data/horse/lustre/scratch2/ws/0/marie-numbercrunch`.
+
+        In case you need to update this (Gigabytes, not Terabytes!) please run `dtrsync` like in
+
+        ```
+        marie@barnard$ dtrsync -a /data/old/lustre/scratch2/ws/0/marie-numbercrunch/<useful data>  /data/walrus/lustre/ws/marie-numbercrunch/
         ```
 
     === "Source: old `/ssd`"
 
         The old `ssd` filesystem is mounted at `/data/old/lustre/ssd` on the datamover nodes and the
-        workspaces are within the subdirectory `ws/`. A corresponding data transfer using `dtcopy`
+        workspaces are within the subdirectory `ws/`. A corresponding data transfer using `dtcp`
         looks like
 
         ```console
-        marie@barnard$ dtcp --recursive /data/old/lustre/ssd/ /data/walrus/ws/marie-numbercrunch
+        marie@barnard$ dtcp --recursive /data/old/lustre/ssd/<useful data> /data/walrus/ws/marie-numbercrunch/
         ```
 
     === "Source: old `/beegfs`"
 
         The old `beegfs` filesystem is mounted at `/data/old/beegfs` on the datamover nodes and the
         workspaces are within the subdirectories `ws/0` and `ws/1`, respectively. A corresponding
-        data transfer using `dtcopy` looks like
+        data transfer using `dtcp` looks like
 
         ```console
-        marie@barnard$ dtcp --recursive /data/old/beegfs/ws/0/marie-numbercrunch /data/walrus/ws/marie-numbercrunch
+        marie@barnard$ dtcp --recursive /data/old/beegfs/ws/0/marie-numbercrunch/<useful data> /data/walrus/ws/marie-numbercrunch/
         ```
 
 ??? "Migration from `/lustre/ssd` or `/beegfs`"
@@ -288,13 +311,18 @@ target filesystems.
     We are synchronizing this (**last: October 18**) to `/data/horse/lustre/scratch2/`.
 
     Please do **NOT** copy those data yourself. Instead check if it is already sychronized
-    to `/data/walrus/warm_archive/ws`.
+    to `/data/horse/lustre/scratch2/ws/0/marie-numbercrunch`.
 
     In case you need to update this (Gigabytes, not Terabytes!) please run `dtrsync` like in
-    `dtrsync -a /data/old/lustre/scratch2/ws/0/my-workspace/newest/  /data/horse/lustre/scratch2/ws/0/my-workspace/newest/`
+    ```
+    marie@barnard$ dtrsync -a /data/old/lustre/scratch2/ws/0/marie-numbercrunch/<useful data>  /data/horse/lustre/scratch2/ws/0/marie-numbercrunch/
+    ```
 
 ??? "Migration from `/warm_archive`"
 
+    MF: Gleiches Schema scratch für walrus
+    ws_allocate -F walrus numbercrunch
+
     The process of syncing data from `/warm_archive` to `/data/walrus/warm_archive` is still ongoing.
 
     Please do **NOT** copy those data yourself. Instead check if it is already sychronized