Bug 2102806 - Persistent-cache flush related content and syntax needs to be added under PWL section in RBD guide
Summary: Persistent-cache flush related content and syntax needs to be added under PWL...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 5.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.2
Assignee: Ranjini M N
QA Contact: Preethi
Akash Raj
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-30 17:21 UTC by Preethi
Modified: 2022-08-23 06:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-23 06:37:49 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-4651 0 None None None 2022-06-30 17:41:01 UTC

Description Preethi 2022-06-30 17:21:26 UTC 
Describe the issue:Persistent-cache flush related content and syntax needs to be added under PWL section in RBD guide

Describe the task you were trying to accomplish: We need to add a separate section for the flush feature supported in PWL

Suggestions for improvement: Please add a section which defines the flush and command usage

Document URL:
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html-single/block_device_guide/index#persistent-write-log-cache_block

Chapter/Section Number and Title:

PWL

Product Version:[root@plena007 ubuntu]# ceph version
ceph version 16.2.8-63.el8cp (233bc2dd7f0b8aa7ec907d66184579e328bb2d6c) pacific (stable)
[root@plena007 ubuntu]# 


example for the command syntax
:
Syntax

rbd persistent-cache flush POOL_NAME/IMAGE_NAME

ex: rbd persistent-cache flush test/image1

Environment Details:

Any other versions of this document that also needs this update:

Additional information:
Comment 4 Preethi 2022-07-06 06:03:25 UTC 
Looks good to me. Thanks for the quick implementation.
Note You need to log in before you can comment on or make changes to this bug.