F OpenNebula/one#6567: fsck dry flag (#2967)

* F OpenNebula/one#6567: fsck dry flag * Update database.rst
OpenNebula · Jul 29, 2024 · 030f27d · 030f27d
1 parent 1e43d66
commit 030f27d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 0 deletions.
diff --git a/source/installation_and_configuration/opennebula_services/database.rst b/source/installation_and_configuration/opennebula_services/database.rst
@@ -141,6 +141,8 @@ onedb fsck
 
 Checks the consistency of OpenNebula objects inside the database and fixes any problems it finds. For example, if the machine where OpenNebula is running crashes or loses connectivity to the database, you may have the wrong number of VMs running in a Host or incorrect usage quotas for some users.
 
+To repair any error, first you need to stop OpenNebula and then run the ``onedb fsck`` command. To check consistency, without writing fixes, use the ``--dry`` option.
+
 .. prompt:: text $ auto
 
     $ onedb fsck

diff --git a/source/intro_release_notes/release_notes/whats_new.rst b/source/intro_release_notes/release_notes/whats_new.rst
@@ -87,6 +87,7 @@ API and CLI
 ================================================================================
 - ``onedb create-index`` command has been removed, a new :ref:`VM search <vm_search>` engine has been implemented to allow flexible queries and improve performance.
 - `OneFlow message logging improved <https://github.com/OpenNebula/one/issues/6553>`__.
+- :ref:`New dry flag for onedb fsck command <onedb_fsck>`: check DB consistency, while the OpenNebula is running, but without writing fixes to the DB.
 
 
 KVM