[
https://issues.apache.org/jira/browse/HDDS-13825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032050#comment-18032050
]
Huang Guan Hao commented on HDDS-13825:
---------------------------------------
I'm interesting in this issue.
How was the om-db-backup database created?
Could you tell more in detail?
Thank you!
> Handle invalid OM DB path and rename FSO repair report fields for clarity
> -------------------------------------------------------------------------
>
> Key: HDDS-13825
> URL: https://issues.apache.org/jira/browse/HDDS-13825
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sarveksha Yeshavantha Raju
> Priority: Minor
>
> If the OM DB provided to the {{ozone repair om fso-tree --db=/path/to/om.db}}
> command is not named {{om.db}}, the report values are returned as null.
> Update the description or better add validation to ensure the DB name is
> correctly specified.
> Example:
> {code:java}
> ozone repair om fso-tree --db=../om-db-backup --dry-run
> [dry run] No running OM service detected. Proceeding with repair.
> [dry run] Creating database with reachable and unreachable tables at
> ../temp.db
> [dry run]
> Reachable:
> Directories: 0
> Files: 0
> Bytes: 0
> Unreachable (Pending to delete):
> Directories: 0
> Files: 0
> Bytes: 0
> Unreferenced (Orphaned):
> Directories: 0
> Files: 0
> Bytes: 0
> {code}
> Additionally, rename all method and report references of *unreachable* to
> *pendingToDelete* and *unreferenced* to *orphaned* to improve clarity and
> consistency.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
