[ 
https://issues.apache.org/jira/browse/HDDS-11346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-11346:
------------------------------
    Description: 
Symptom:

>From CLI:
{code}
bash-4.2$ ozone fs -rm -skipTrash -r ofs://om/vol1/
rm: Recursive volume delete using ofs is not supported. Instead use 'ozone sh 
volume delete -r -skipTrash -id <OM_SERVICE_ID> <Volume_URI>' command
{code}

But when I follow the prompt, I get "Unknown options":

{code}
bash-4.2$ ozone sh volume delete -r -skipTrash -id om /vol1
Unknown options: '-skipTrash', '-id', '/vol1'
Usage: ozone sh volume delete [-hrVy] [-t=<threadNo>] <value>
deletes a volume
      <value>     URI of the volume.
                  Ozone URI could either be a full URI or short URI.
                  Full URI should start with o3://, in case of non-HA
                  clusters it should be followed by the host name and
                  optionally the port number. In case of HA clusters
                  the service id should be used. Service id provides a
                  logical name for multiple hosts and it is defined
                  in the property ozone.om.service.ids.
                  Example of a full URI with host name and port number
                  for a key:
                  o3://omhostname:9862/vol1/bucket1/key1
                  With a service id for a volume:
                  o3://omserviceid/vol1/
                  Short URI should start from the volume.
                  Example of a short URI for a bucket:
                  vol1/bucket1
                  Any unspecified information will be identified from
                  the config files.

  -h, --help      Show this help message and exit.
  -r              Delete volume recursively
  -t, --thread, --threads=<threadNo>
                  Number of threads used to execute recursive delete
  -V, --version   Print version information and exit.
  -y, --yes       Continue without interactive user confirmation
bash-4.2$
{code}

The correct command line to achieve the intended purpose (recursively delete 
the volume) should be this:

{code}
bash-4.2$ ozone sh volume delete -r o3://om/vol1
This command will delete volume recursively.
There is no recovery option after using this command, and no trash for FSO 
buckets.
Delay is expected running this command.
Enter 'yes' to proceed': yes
Volume vol1 is deleted
bash-4.2$
{code}

  was:
Symptom:

>From CLI:
{code}
bash-4.2$ ozone fs -rm -skipTrash -r ofs://om/vol1/
rm: Recursive volume delete using ofs is not supported. Instead use 'ozone sh 
volume delete -r -skipTrash -id <OM_SERVICE_ID> <Volume_URI>' command
{code}

But when I follow the prompt, I get error instead:

{code}
bash-4.2$ ozone sh volume delete -r -skipTrash -id om /vol1
Unknown options: '-skipTrash', '-id', '/vol1'
Usage: ozone sh volume delete [-hrVy] [-t=<threadNo>] <value>
deletes a volume
      <value>     URI of the volume.
                  Ozone URI could either be a full URI or short URI.
                  Full URI should start with o3://, in case of non-HA
                  clusters it should be followed by the host name and
                  optionally the port number. In case of HA clusters
                  the service id should be used. Service id provides a
                  logical name for multiple hosts and it is defined
                  in the property ozone.om.service.ids.
                  Example of a full URI with host name and port number
                  for a key:
                  o3://omhostname:9862/vol1/bucket1/key1
                  With a service id for a volume:
                  o3://omserviceid/vol1/
                  Short URI should start from the volume.
                  Example of a short URI for a bucket:
                  vol1/bucket1
                  Any unspecified information will be identified from
                  the config files.

  -h, --help      Show this help message and exit.
  -r              Delete volume recursively
  -t, --thread, --threads=<threadNo>
                  Number of threads used to execute recursive delete
  -V, --version   Print version information and exit.
  -y, --yes       Continue without interactive user confirmation
bash-4.2$
{code}

The correct command line to achieve the intended purpose (recursively delete 
the volume) should be this:

{code}
bash-4.2$ ozone sh volume delete -r o3://om/vol1
This command will delete volume recursively.
There is no recovery option after using this command, and no trash for FSO 
buckets.
Delay is expected running this command.
Enter 'yes' to proceed': yes
Volume vol1 is deleted
bash-4.2$
{code}


> FS CLI gives incorrect recursive volume deletion prompt
> -------------------------------------------------------
>
>                 Key: HDDS-11346
>                 URL: https://issues.apache.org/jira/browse/HDDS-11346
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone CLI
>    Affects Versions: 1.4.1
>            Reporter: Siyao Meng
>            Priority: Major
>
> Symptom:
> From CLI:
> {code}
> bash-4.2$ ozone fs -rm -skipTrash -r ofs://om/vol1/
> rm: Recursive volume delete using ofs is not supported. Instead use 'ozone sh 
> volume delete -r -skipTrash -id <OM_SERVICE_ID> <Volume_URI>' command
> {code}
> But when I follow the prompt, I get "Unknown options":
> {code}
> bash-4.2$ ozone sh volume delete -r -skipTrash -id om /vol1
> Unknown options: '-skipTrash', '-id', '/vol1'
> Usage: ozone sh volume delete [-hrVy] [-t=<threadNo>] <value>
> deletes a volume
>       <value>     URI of the volume.
>                   Ozone URI could either be a full URI or short URI.
>                   Full URI should start with o3://, in case of non-HA
>                   clusters it should be followed by the host name and
>                   optionally the port number. In case of HA clusters
>                   the service id should be used. Service id provides a
>                   logical name for multiple hosts and it is defined
>                   in the property ozone.om.service.ids.
>                   Example of a full URI with host name and port number
>                   for a key:
>                   o3://omhostname:9862/vol1/bucket1/key1
>                   With a service id for a volume:
>                   o3://omserviceid/vol1/
>                   Short URI should start from the volume.
>                   Example of a short URI for a bucket:
>                   vol1/bucket1
>                   Any unspecified information will be identified from
>                   the config files.
>   -h, --help      Show this help message and exit.
>   -r              Delete volume recursively
>   -t, --thread, --threads=<threadNo>
>                   Number of threads used to execute recursive delete
>   -V, --version   Print version information and exit.
>   -y, --yes       Continue without interactive user confirmation
> bash-4.2$
> {code}
> The correct command line to achieve the intended purpose (recursively delete 
> the volume) should be this:
> {code}
> bash-4.2$ ozone sh volume delete -r o3://om/vol1
> This command will delete volume recursively.
> There is no recovery option after using this command, and no trash for FSO 
> buckets.
> Delay is expected running this command.
> Enter 'yes' to proceed': yes
> Volume vol1 is deleted
> bash-4.2$
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to