This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1946911 - Provide a way to exclude multipath devices from being scanned
Summary: Provide a way to exclude multipath devices from being scanned
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rear
Version: 8.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: CS System Management SST QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-07 08:39 UTC by Renaud Métrich
Modified: 2024-06-14 01:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 23:40:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2597 0 None open New ONLY_INCLUDE_DISKS variable 2021-04-07 08:39:36 UTC
Red Hat Issue Tracker   RHEL-6951 0 None Migrated None 2023-09-21 23:39:18 UTC

Description Renaud Métrich 2021-04-07 08:39:37 UTC 
Description of problem:

Currently all block devices found in /sys/block are scanned, which makes the creation of the ReaR recovery be super slow when having tons of multipath devices.
I'm proposing to backport PR https://github.com/rear/rear/pull/2597 to avoid the scan.

On some systems, it saves up to 40 minutes!

Version-Release number of selected component (if applicable):

rear-2.4 / rear-2.6


How reproducible:

N/A
Comment 1 Pavel Cahyna 2021-04-07 09:36:39 UTC 
Is there any relation to the existing AUTOEXCLUDE_MULTIPATH variable ("y" by default)?
Comment 2 Renaud Métrich 2021-04-07 09:55:53 UTC 
Somehow yes.
The issue is that the code (for now) collects everything about devices, then later excludes devices.
Changing the current code to do the opposite is extremely complicated.
Comment 3 Pavel Cahyna 2021-04-08 09:25:34 UTC 
Can you please attach a log of the problematic "rear mkrescue" that shows the 40 minute slowdown? I would like to check whether the SCSI devices are detected correctly as paths of the multipath devices or not. (If not, then the slowdown might be caused by this and the best solution would be to fix the detection.)
Comment 9 RHEL Program Management 2023-09-21 23:35:29 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 10 RHEL Program Management 2023-09-21 23:40:32 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.
Note You need to log in before you can comment on or make changes to this bug.