RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2095492 - request for memory usage warning when setting up dm-writecache
Summary: request for memory usage warning when setting up dm-writecache
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: lvm2
Version: 8.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Teigland
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On: 2059644
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-09 18:58 UTC by David Teigland
Modified: 2022-11-08 12:52 UTC (History)
12 users (show)

Fixed In Version: lvm2-2.03.14-4.el8
Doc Type: Enhancement
Doc Text:
Clone Of: 2059644
Environment:
Last Closed: 2022-11-08 10:55:29 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CLUSTERQE-5816 0 None None None 2022-07-28 03:01:25 UTC
Red Hat Issue Tracker RHELPLAN-124913 0 None None None 2022-06-09 19:02:19 UTC
Red Hat Product Errata RHBA-2022:7792 0 None None None 2022-11-08 10:55:45 UTC

Comment 3 David Teigland 2022-06-09 18:59:56 UTC 
backporting this to 8.7
Comment 7 Corey Marthaler 2022-07-15 02:24:12 UTC 
Marking verified in the latest rpms.

# RHEL8.7 

kernel-4.18.0-398.g366e.el8.kpq1    BUILT: Tue Jun  7 04:56:38 CDT 2022
lvm2-2.03.14-4.el8    BUILT: Wed Jun 15 17:14:34 CDT 2022
lvm2-libs-2.03.14-4.el8    BUILT: Wed Jun 15 17:14:34 CDT 2022


   dm-writecache memory usage
       The amount of main system memory used by dm-writecache can be a factor when selecting the writecache cachevol size and the writecache block size.

       · writecache block size 4096: each 100 GiB of writecache cachevol uses slighly over 2 GiB of system memory.

       · writecache block size 512: each 100 GiB of writecache cachevol uses a little over 16 GiB of system memory.


[root@hayes-01 ~]# cat /proc/meminfo
MemTotal:       263626796 kB

[root@hayes-01 ~]# lvcreate --yes --type linear -n write  -L 6T vdo_sanity
  Logical volume "write" created.
[root@hayes-01 ~]# lvchange --yes -an  vdo_sanity/write

[root@hayes-01 ~]# lvcreate --yes -L 4T -n wc_lv  vdo_sanity
  Logical volume "wc_lv" created.


[root@hayes-01 ~]# lvconvert --yes --type writecache --cachevol vdo_sanity/write vdo_sanity/wc_lv
  Using writecache block size 4096 for unknown file system block size, logical block size 512, physical block size 512.
  WARNING: unable to detect a file system block size on vdo_sanity/wc_lv
  WARNING: using a writecache block size larger than the file system block size may corrupt the file system.
  WARNING: writecache size 6.00 TiB will use 132 GiB of system memory (251 GiB).
  Logical volume vdo_sanity/wc_lv now has writecache.
Comment 10 Corey Marthaler 2022-07-28 15:02:48 UTC 
Verified in the latest kernel/lvm2 rpms as well.

kernel-4.18.0-411.el8    BUILT: Wed Jul 20 18:42:42 CDT 2022
lvm2-2.03.14-5.el8    BUILT: Thu Jul 14 09:23:13 CDT 2022
lvm2-libs-2.03.14-5.el8    BUILT: Thu Jul 14 09:23:13 CDT 2022


[root@hayes-02 ~]# lvconvert --yes --type writecache --cachevol vdo_sanity/write vdo_sanity/wc_lv
  Using writecache block size 4096 for unknown file system block size, logical block size 512, physical block size 512.
  WARNING: unable to detect a file system block size on vdo_sanity/wc_lv
  WARNING: using a writecache block size larger than the file system block size may corrupt the file system.
  WARNING: writecache size 6.00 TiB will use 132 GiB of system memory (251 GiB).
  Logical volume vdo_sanity/wc_lv now has writecache.
Comment 13 errata-xmlrpc 2022-11-08 10:55:29 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 (lvm2 bug fix and enhancement update), 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-2022:7792
Note You need to log in before you can comment on or make changes to this bug.