Bug 1728357

Summary:	[RFE] BlueStore tool to check fragmentation
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vikhyat Umrao <vumrao>
Component:	RADOS	Assignee:	Adam Kupczyk <akupczyk>
Status:	CLOSED ERRATA	QA Contact:	Manohar Murthy <mmurthy>
Severity:	high	Docs Contact:	Bara Ancincova <bancinco>
Priority:	high
Version:	3.2	CC:	agunn, akupczyk, alhandy, assingh, ceph-eng-bugs, ceph-qe-bugs, dzafman, gsitlani, jdurgin, kchai, mmuench, nojha, tchandra, tserlin
Target Milestone:	z1	Keywords:	FutureFeature
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-58.el7cp Ubuntu: ceph_12.2.12-52redhat1xenial	Doc Type:	Enhancement
Doc Text:	.The ability to inspect BlueStore fragmentation This update adds the ability to inspect fragmentation of the BlueStore back end. To do so, use the `ceph daemon` command or the `ceph-bluestore-tool` utility. For details see the {product} {release} link:{admin-guide}#the-blustore-fragmentation-tool[_Administration Guide_].	Story Points:	---
Clone Of:
Clones:	1773757 (view as bug list)		Environment:
Last Closed:	2019-10-22 13:29:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1725227, 1726135, 1733598, 1773757

Description Vikhyat Umrao 2019-07-09 18:52:25 UTC

Description of problem:
[RFE] BlueStore tool to check fragmentation

Comment 4 Giridhar Ramaraju 2019-08-05 13:11:37 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 5 Giridhar Ramaraju 2019-08-05 13:12:35 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Vikhyat Umrao 2019-08-05 16:05:45 UTC

Doc bug - https://bugzilla.redhat.com/show_bug.cgi?id=1737546

Comment 29 errata-xmlrpc 2019-10-22 13:29:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3173