Bug 99521
| Summary: | mkinitrd fails when /tmp is a tempfs | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 2.1 | Reporter: | James White <jsw> |
| Component: | mkinitrd | Assignee: | Jeremy Katz <katzj> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.1 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 3.3.9-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2003-07-21 17:19:03 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: | |||
Fixed in at least 3.3.9-1 and later. On pulling updates via RHN up2date, mkinitrd at rev. 3.2.6-1 is the latest offered. When will mkinitrd-3.3.9-1 be made available via up2date? Also, where might I obtain it in the interim? |
Description of problem: On a kernel upgrade, mkinitrd fails when /tmp is a tempfs leaving the system without an initrd for the new kernel. The error message given is: All loopback devices are in use! How reproducible: Take a kernel upgrade with /tmp as a tempfs. Steps to Reproduce: 1. Setup /tmp as a tempfs. 2. Take a kernel upgrade or manually invoke mkinitrd. Additional info: Workaround -- change /tmp references to /var/tmp (not a tempfs) in the mkinitrd script.