Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
John,
Could you elaborate on why you believe a raid5 array needs to report discard
zeroes data?
Whether or not data is zeroed has nothing to do with whether or not was
discarded. All discard does is to tell the underlying drives that they discard
of the data, and knowing it is zeroed makes it faster for the raid stack to
do the resync work. The fact that an array does not zero data on discard does
not imply that discard doesn't work.
Jes
Hi Jes,
Thanks a lot for the explanation, I was not aware of that. I suppose then if the discard_zeroes_data parameter exists for the md device in /sys it should inherit or be set to the same value as the underlying disks, assuming all the underlying disks have the same discard_zeroes_data value.
John
John,
There is no requirement for this parameter to be inherited in this case. For
raid456 in particular the RAID stack has the freedom to write whatever it
finds the most optimal to the device when it is being discarded. So while it
might be nice for it to zero data, I don't see the current behavior being a
bug.
I am going to close this as notabug, if you feel this is wrong please reopen
with a case for it.
Thanks,
Jes