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 1287316 - volumes not mounted fast enough resulting in system boot to emergency mode.
Summary: volumes not mounted fast enough resulting in system boot to emergency mode.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.2
Hardware: Unspecified
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1385242
TreeView+ depends on / blocked
 
Reported: 2015-12-01 23:27 UTC by Joe Wright
Modified: 2021-09-08 20:50 UTC (History)
24 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-30 11:07:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Lukáš Nykrýn 2016-01-11 13:14:04 UTC 
Can you boot the machine with debug on kernel cmdline, reproduce the issue and send us output of journalctl?
Comment 8 ajit mote 2016-02-04 07:26:12 UTC 
Logs with debug are attached so removing needinfo ..... Customer is active so we can collect or try out things.
Comment 9 Lukáš Nykrýn 2016-02-04 09:31:25 UTC 
To me this looks like a dm/lvm bug. The system was not able to assemble the raid. 

But anyway, even if this is a systemd bug, we will need some help from storage guys, so reassigning to lvm.
Comment 10 Peter Rajnoha 2016-02-04 10:58:55 UTC 
Are those failing mount points on LVM and then on multipath stack?
Comment 11 ajit mote 2016-02-04 11:46:57 UTC 
(In reply to Peter Rajnoha from comment #10)
> Are those failing mount points on LVM and then on multipath stack?

Yes, In my case mount points are on LVM which are using multipath device.

I have latest sosreport from customer, I can upload here.
Comment 13 Peter Rajnoha 2016-02-04 12:36:27 UTC 
(In reply to ajit mote from comment #11)
> (In reply to Peter Rajnoha from comment #10)
> > Are those failing mount points on LVM and then on multipath stack?
> 
> Yes, In my case mount points are on LVM which are using multipath device.
> 
> I have latest sosreport from customer, I can upload here.

If the customer uses lvmetad (use_lvmetad=1 set in lvm.conf), if possible, it would be great if he could try suggestion from bug #1287106 comment #47.

If he doesn't use lvmetad (use_lvmetad=0), then bug #1287106 comment #42 and bug #1287106 comment #43.

I think bug #1287106 and this bug may be about the same.
Comment 16 Ben Marzinski 2016-02-12 00:19:48 UTC 
There are device-mapper-multipath test packages that avoid reloading a multipath device until multipathd has received the uevent from creating it. You can download them here:

http://people.redhat.com/~bmarzins/device-mapper-multipath/rpms/RHEL7/bz1304687/

These packages, along with the change to pvscan that Peter posted in bug #1287106 comment #48, should hopefully fix this (assuming that this is the same issue as bug #1287106)
Comment 46 LENHOF 2016-04-05 08:56:10 UTC 
Is this bug report linked with this solution (I've access to this one) ?
https://access.redhat.com/solutions/2147731

I've tried this solution in our environment and it seems to be a good workaround for this problem. But we don't want to put in production (Oracle RAC on RH Linux, so definitively a high availability platform ) something which has not a definitive fix, is following this bug report the right thing to do ?

I did'nt have access to bug report #1287106...

Regards,

JYL
Comment 47 Alasdair Kergon 2016-04-05 09:55:31 UTC 
(In reply to LENHOF from comment #46)
> I did'nt have access to bug report #1287106...

There's customer data scattered through that bug so I cannot easily open it up unfortunately.

We'll see if the information is somewhere else or if we need to copy it across here.
Comment 48 Peter Rajnoha 2016-04-05 11:39:41 UTC 
I've opened a new BZ with summary of the problem which is public:
https://bugzilla.redhat.com/show_bug.cgi?id=1324028
Comment 61 Zdenek Kabelac 2017-01-30 11:07:50 UTC 
So the original case is closely related to broken installation procedure provided by  'openstack undercloud install'.

It should not mess with 'auto_activation_volume_list'

As for the comment 58 - from provided report - it looks unrelated to this bz, as logs shows evidence of 'qla2xxx [0000:44:00.0]-8038:0: Cable is unplugged...' - so it's more or less likely a hardware issue with multipath configuration.

If there is still any problem - please open new case.

Closing the BZ as the original case is closed.
Note You need to log in before you can comment on or make changes to this bug.