Bug 2232836

Summary: No software RAID scrub/check scheduled by default
Product: Red Hat Enterprise Linux 9 Reporter: g.danti
Component: mdadmAssignee: XiaoNi <xni>
Status: CLOSED MIGRATED QA Contact: Storage QE <storage-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 9.2CC: ncroxon
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-23 19:23:34 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:

Description g.danti 2023-08-19 10:17:22 UTC
Description of problem:
In previous RHEL version, a cron entry existed for automatic scrub of software RAID arrays. In current RHEL 9.x two services called mdcheck_start.service and mdcheck_continue.service are provided, and they can be triggered by the respective systemd timers. However they call a non-existing script at path /usr/share/mdadm/mdcheck. The mdcheck script really lives at /usr/share/doc/mdadm/mdcheck. 

Indeed, checking which packages provides the mdcheck script shows:

# yum whatprovides */mdcheck
Last metadata expiration check: 2:21:21 ago on Sat 19 Aug 2023 09:40:01 AM CEST.
mdadm-4.2-8.el9.x86_64 : The mdadm program controls Linux md devices (software RAID arrays)
Repo        : @System
Matched from:
Filename    : /usr/share/doc/mdadm/mdcheck

As things stand now, one has to create a custom cron entry or softlink the /usr/share/doc/mdadm/mdcheck at the path expected by the systemd services (ie: ln -s /usr/share/doc/mdadm/mdcheck /usr/share/mdadm/mdcheck)

Version-Release number of selected component (if applicable):
mdadm-4.2-8.el9.x86_64

How reproducible:
Try starting mdcheck_start.service and see how it fails due to a non-existent ExecStart path.

Steps to Reproduce:
1. systemctl start mdcheck_start.service
2. systemctl status mdcheck_start.service
3. the service is in failed state

Actual results:
mdcheck_start.service and mdcheck_continue.service do not start, nor classical cron entry is provided for software RAID scrub/check

Expected results:
Automatic software RAID scrub/check should be provided out of the box.

Additional info:
None.

Comment 1 RHEL Program Management 2023-09-23 19:21:54 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-23 19:23:34 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.