Bug 1831398 - Add a note about block_size of SSD compatibility with volume group
Summary: Add a note about block_size of SSD compatibility with volume group
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Deploying_RHHI
Version: rhhiv-1.8
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: RHHI-V 1.8
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: RHHI-V-1.8-Documentation-Inflight-BZs
TreeView+ depends on / blocked
 
Reported: 2020-05-05 04:46 UTC by SATHEESARAN
Modified: 2020-08-11 13:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-11 13:15:31 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2020-05-05 04:46:19 UTC
Description of problem:
-------------------------
LVM cache uses the mechanism to add fast device(SSD) to slow device (HDD) in the same Volume Group(VG), to make fast device(SSD) to act as a cache for slow device.

In this case, fast device(SSD)'s disk block size should be same as that of the disks in that VG. 

Also VDO volume is now created with disk block size as 4K. In this case, SSD that gets attached to thinpool created with VDO devices, should have its block size as 4K.

If the above compatibility is not present, RHHI-V deployment will fail

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHHI-V deployment guides 1.8

How reproducible:
-----------------
Always

Expected results:
-----------------
Deployment guide of single node, 3 node, RHEL based guides, should add this to requirements for 'Disk'
1. If there is plan to make use of LVM cache for VDO devices, then the block size of that fast device(SSD) should be 4K
2. If LVM cache is used for non-VDO devices, make sure that the disk block size of slow device(HDD) and fast device(SSD) matches.

Comment 1 SATHEESARAN 2020-05-05 04:47:29 UTC
We also need to include this info in the bricks tab section, where we describe about LVM cache


Note You need to log in before you can comment on or make changes to this bug.