Bug 232849 – Multipath devices not created in time

Bug 232849 - Multipath devices not created in time

Summary:	Multipath devices not created in time

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Red Hat Enterprise Linux 4
Classification:	Red Hat
Component:	device-mapper-multipath (Show other bugs)
Sub Component:
Version:	4.4
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ben Marzinski
QA Contact:	Corey Marthaler
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-03-18 17:46 EDT by Joseph Shraibman
Modified:	2010-01-11 21:28 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-01-12 16:17:17 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Joseph Shraibman 2007-03-18 17:46:15 EDT

Description of problem:
When booting I get dropped into singe user mode when init reads fstab to mount
directories because the multipath entries in /dev don't exist.  Once I enter the
root password I can mount the directories because at that point the devices to
exist.

Version-Release number of selected component (if applicable):
device-mapper-multipath-0.4.5-16.1.RHEL4

How reproducible:
All the time

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
To work around I added _netdev to the options in fstab

Comment 1 Ben Marzinski 2007-04-04 18:11:09 EDT

Which multipath entries are you using?

/dev/dm-* names are not guaranteed to be unique across reboots and should never
be used. They are also created by udev and not guaranteed to exist immediately
after device creation.

/dev/mpath/* names are unique, but are also created by udev and not guaranteed
to exist immediately after device creation. They should not be used in things
like /etc/fstab

/dev/mapper/* names are created by device-mapper, and exist immediately after
the device is created.

If you are not using /dev/mapper/* names in /etc/fstab, try switching to them
and let me know if this fixes the problem for you.

Comment 2 Joseph Shraibman 2007-04-04 21:17:58 EDT

I was using /dev/dm-*.  I can't reboot this system anytime soon just to test if
the /dev/mapper entries work.

Comment 3 Ben Marzinski 2007-05-31 20:29:55 EDT

Please let me know if this fixed the problem.

Comment 4 Joseph Shraibman 2007-05-31 21:47:33 EDT

I'm sorry, this system might not be rebooted for months.

Note You need to log in before you can comment on or make changes to this bug.