Feature #3831

onedb fsck - If database inconsistency cannot be resolved automatically indicate that this item may require manual intervention to resolve

Added by Mike Fischer about 6 years ago. Updated almost 6 years ago.

Status:ClosedStart date:06/09/2015
Priority:NormalDue date:
Assignee:Carlos Martín% Done:


Category:Core & System
Target version:Release 4.14
Resolution:fixed Pull request:


There appear to be conditions which the onedb fsck cannot reconcile.

One example scenario (but not limited to this) is where a VM was deployed, but the vnet it was referencing has since been deleted.
When running onedb fsck, this inconsistency is detected, however the expectation is that onedb automatically resolves these items.
If scenarios exist where it cannot repair the error, these items should be highlighted in the output to indicate that the administrator will need to investigate/repair that scenario manually.

$ onedb fsck -u user -d opennebula
VM 21059 is using VNet 761, but it does not exist 

Possible suggestion at end of fsck output, list items not automatically repaired.

Total errors found: 10
Total errors repaired: 9
Total errors not repaired: 1
Investigate and reconcile as required:

VM 21059 is using VNet 761, but it does not exist

Associated revisions

Revision 90496a0a
Added by Carlos Martín almost 6 years ago

Feature #3831: Mark unresolved problems in fsck


#1 Updated by Ruben S. Montero about 6 years ago

  • Tracker changed from Request to Feature
  • Category set to Core & System
  • Priority changed from Low to Normal
  • Target version set to Release 4.14

#2 Updated by Ruben S. Montero almost 6 years ago

  • Assignee set to Carlos Martín

#3 Updated by Carlos Martín almost 6 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

Good suggestion, it's now done in master.

Also available in: Atom PDF