diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
index 924d98077b2489ba5f2516f3e21fe49004747ad2..e13c2f695f803330fac9875715f15b4a17cbf97c 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
@@ -25,6 +25,35 @@ times.
## Workspace Management
+### Settings for Workspaces
+
+Since the workspace filesystems are differ in the intended use, the settings for workspace settings
+are not equal across all filesystems. The following table provides the settings for the different
+filesystems.
+
+| Filesystem (use with parameter `--filesystem=<filesystem>`) | Max. Duration in Days | Extensions | Keeptime | [Filesystem Feature](../jobs_and_resources/slurm.md#filesystem-features) |
+|:------------------------------------------------------------|---------------:|-----------:|---------:|:-------------------------------------------------------------------------|
+| ` horse` | 100 | 10 | 30 | |
+| ` walrus` | 100 | 10 | 60 | |
+| `beegfs_global0` (deprecated) | 30 | 2 | 30 | `fs_beegfs_global0` |
+| `beegfs` | 30 | 2 | 30 | `fs_beegfs` |
+{: summary="Settings for Workspace Filesystems."}
+
+!!! warning "End of life filesystems"
+
+ The filesystems `warm_archive`, `ssd` and `scratch` will be switched off end of 2023.
+
+ | Filesystem (use with parameter `--filesystem=<filesystem>`) | Duration, days | Extensions | [Filesystem Feature](../jobs_and_resources/slurm.md#filesystem-features) | Remarks |
+ |:-------------------------------------|---------------:|-----------:|:-------------------------------------------------------------------------|:--------|
+ | `scratch` (default) | 100 | 10 | `fs_lustre_scratch2` | Scratch filesystem (`/lustre/scratch2`, symbolic link: `/scratch`) with high streaming bandwidth, based on spinning disks |
+ | `ssd` | 30 | 2 | `fs_lustre_ssd` | High-IOPS filesystem (`/lustre/ssd`, symbolic link: `/ssd`) on SSDs. |
+ | `warm_archive` | 365 | 2 | 30 | `fs_warm_archive_ws` | Capacity filesystem based on spinning disks |
+
+!!! note
+
+ Currently, not all filesystems are available on all of our five clusters. The page
+ [Working Filesystems](working.md) provides the necessary information.
+
### List Available Filesystems
To list all available filesystems for using workspaces, you can either invoke `ws_list -l` or
@@ -207,16 +236,9 @@ group workspaces.
### Extension of a Workspace
The lifetime of a workspace is finite and different filesystems (storage systems) have different
-maximum durations. A workspace can be extended multiple times, depending on the filesystem.
-
-| Filesystem (use with parameter `--filesystem=<filesystem>`) | Duration, days | Extensions | [Filesystem Feature](../jobs_and_resources/slurm.md#filesystem-features) | Remarks |
-|:-------------------------------------|---------------:|-----------:|:-------------------------------------------------------------------------|:--------|
-| `scratch` (default) | 100 | 10 | `fs_lustre_scratch2` | Scratch filesystem (`/lustre/scratch2`, symbolic link: `/scratch`) with high streaming bandwidth, based on spinning disks |
-| `ssd` | 30 | 2 | `fs_lustre_ssd` | High-IOPS filesystem (`/lustre/ssd`, symbolic link: `/ssd`) on SSDs. |
-| `beegfs_global0` (deprecated) | 30 | 2 | `fs_beegfs_global0` | High-IOPS filesystem (`/beegfs/global0`) on NVMes. |
-| `beegfs` | 30 | 2 | `fs_beegfs` | High-IOPS filesystem (`/beegfs`) on NVMes. |
-| `warm_archive` | 365 | 2 | `fs_warm_archive_ws` | Capacity filesystem based on spinning disks |
-{: summary="Settings for Workspace Filesystem."}
+maximum durations. The life time of a workspace can be adjusted multiple times, depending on the
+filesystem. You can find the concrete values in the
+[section settings for workspaces](#settings-for-workspaces).
Use the command `ws_extend` to extend your workspace:
diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard.md
index ff9dccc8a5198928fd3741081c05c93ca35c7d07..1cff098f3c7a06fdfb04f1a8538d6be2c9fc23db 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard.md
@@ -6,7 +6,7 @@ software and workflows for production there.
!!! note "Migration Phase"
Please make sure to have read the details on the overall
- [Architectural Re-Design 2023](architecture_2023.md#migration-phase) before further reading.
+ [Architectural Re-Design 2023](hardware_overview.md) before further reading.
The migration from Taurus to Barnard comprises the following steps:
@@ -69,14 +69,9 @@ below. In order to support the data life cycle management, the well-known
The filesystems `/data/horse` and `/data/walrus` can only be accessed via workspaces. Please refer
to the [workspace page](../data_lifecycle/workspaces.md), if you are not familiar with the
-workspace concept and the corresponding commands. The following table provides the settings for
-workspaces on these two filesystems.
-
-| Filesystem (use with parameter `--filesystem=<filesystem>`) | Max. Duration in Days | Extensions | Keeptime in Days |
-|:-------------------------------------|---------------:|-----------:|--------:|
-| `/data/horse` (default) | 100 | 10 | 30 |
-| `/data/walrus` | 365 | 2 | 60 |
-{: summary="Settings for Workspace Filesystem `/data/horse` and `/data/walrus`."}
+workspace concept and the corresponding commands. You can find the settings for
+workspaces on these two filesystems in the
+[section Settings for Workspaces](../data_lifecycle/workspaces.md#settings-for-workspaces).
### Data Migration to New Filesystems