proxmox-mirrors/proxmox-backup
1
0
Fork 1
mirror of https://git.proxmox.com/git/proxmox-backup synced 2025-08-13 08:24:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: removable datastores: rephrasing and typos

Browse Source 
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
This commit is contained in:
Fabian Grünbichler 2024-11-26 13:05:49 +01:00
parent 3b9cf7b7a1
commit d9f36232f1
1 changed files with 7 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/storage.rst
View File

@ -178,9 +178,9 @@ using this method the disk will be partitioned and formatted automatically for t
Devices with only one datastore on them will be mounted automatically. Unmounting has
to be done through the UI by clicking "Unmount" on the summary page or using the CLI.
If unmounting should fail, the reason is logged in the unmount-task, and the datastore
will stay in maintenance mode ``unmounting``, which prevents any IO operations. If that should
happen, the maintenace mode has to be reset manually using:
If unmounting fails, the reason is logged in the unmount task log, and the
datastore will stay in maintenance mode ``unmounting``, which prevents any IO
operations. In such cases, the maintenance mode has to be reset manually using:
.. code-block:: console
@ -218,11 +218,10 @@ All datastores present on a device can be listed using ``proxmox-backup-debug``.
# proxmox-backup-debug inspect device /dev/...
Verify jobs are skipped if the removable datastore should not be mounted when they are scheduled,
Sync jobs start, but fail with an error saying the datastore was not mounted. The reason is that
syncs not happening as schduled should at least be noticable. GC and pruning, like verification,
is skipped without a failed task if the datastore should not be mounted.
Verify, Prune and Garbage Collection jobs are skipped if the removable
datastore is not mounted when they are scheduled. Sync jobs start, but fail
with an error saying the datastore was not mounted. The reason is that syncs
not happening as scheduled should at least be noticable.
Managing Datastores
^^^^^^^^^^^^^^^^^^^