Bug 43070 – losetup fails if /tmp is tmpfs

Bug 43070 - losetup fails if /tmp is tmpfs

Summary:	losetup fails if /tmp is tmpfs

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	mkinitrd (Show other bugs)
Sub Component:
Version:	7.1
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-05-31 09:46 EDT by Need Real Name
Modified:	2007-04-18 12:33 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-05-31 09:46:34 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Need Real Name 2001-05-31 09:46:29 EDT

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 15:36:28 EST

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

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