Bug 43070

Summary:	losetup fails if /tmp is tmpfs
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <mb/redhat>
Component:	mkinitrd	Assignee:	Matt Wilson <msw>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1	CC:	edwinh, katzj
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-05-31 13:46:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2001-05-31 13:46:29 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.5-ac5 i686)

Description of problem:
mkinitrd runs losetup which fails over tmpfs. This is probably a bug in the
kernel. (I tested with 2.4.5-ac5)

How reproducible:
Always

Steps to Reproduce:
1. mount /tmp as tmpfs
2. run mkinitrd
	
	

Actual Results:  3. "all your loop devices are in use"

Additional info:

hacking the mktemp lines from /tmp to /var/tmp solved the problem for memk

Comment 1 Erik Troan 2002-01-16 20:36:28 UTC

mkinitrd looks around for a non-tmpfs directory as of 3.3.1