Cont: Document workspace allocation on Barnard

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

@@ -147,11 +147,30 @@ target not the source filesystem.
     names! Furthermore, your workspaces might be place on `/data/horse/lustre/scratch2/ws/0` or
     `/data/horse/lustre/scratch2/ws/1`. Use `ws_list` on Taurus(!) to verify the correct path!
 
-!!! Hint "First Step: Allocate a workspace"
+??? Note "First Step: Allocate a workspace"
 
-    Before you invoke any data transer from the old working filesystems to the new ones, you need to
-    allocate a workspace. Both `/data/horse/` and `/data/walrus` can only be used with
-    [workspaces](../data_lifecycle/workspaces.md)
+    Both `/data/horse/` and `/data/walrus` can only be used with
+    [workspaces](../data_lifecycle/workspaces.md). Before you invoke any data transer from the old
+    working filesystems to the new ones, you need to allocate a workspace first.
+
+    The command `ws_list -l` lists the available and the default filesystem for worspaces.
+
+    ```
+    marie@barnard$ ws_list --list
+    available filesystems:
+    horse (default)
+    walrus
+    ```
+
+    As you can see, `/data/horse` is the default workspace filesystem at Barnard. I.e., if you
+    want to allocate, extend or release a workspace on `/data/walrus`, you need to pass the
+    option `--filesystem=walrus` explicitly to the corresponding workspace commands. Please
+    refer to our [workspace documentation](../data_lifecycle/workspaces.md), if you need refresh
+    your knowledge.
+
+    ```
+    marie@barnard$ ws_allocate numbercrunch 90
+         ```
 
 ??? "Migration to `/data/horse`"