Bug 55716 - mkinitrd fails using tmpfs
mkinitrd fails using tmpfs
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-11-05 11:13 EST by Need Real Name
Modified: 2007-04-18 12:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-11-05 22:14:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2001-11-05 11:13:39 EST
Description of Problem:
If I mount /tmp using an /etc/fstab entry:
tmp           /tmp         tmpfs   defaults    0 0

Then mkinitrd fails with an error that all loop devices are in use.

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

How Reproducible:

Steps to Reproduce:
1. Mount /tmp as a tmpfs
2. Run mkinitrd (eg, mkinitrd /boot/initrd.img 2.4.13)
3. Failure

Actual Results:
Error message and no initrd.img file

Expected Results:
initrd.img file should get created.

Additional Information:
Comment 1 Bill Nottingham 2001-11-05 22:14:40 EST
tmpfs doesn't support itself being backing store for loopback. Until that
changes, don't do that. :)
Comment 2 Arjan van de Ven 2001-11-06 04:59:48 EST
shmfs (aka tmpfs) indeed doesn't support loopback and other things. using it as
/tmp is also quite risky unless you have plenty of swap.

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