Bug 136199
Summary: | rhgb-0.11.2-8 complains bad umount | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | H.J. Lu <hongjiu.lu> |
Component: | rhgb | Assignee: | Daniel Veillard <veillard> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-30 15:01:21 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
H.J. Lu
2004-10-18 18:01:11 UTC
This code hasn't changed at all recently. Is something mounted on /initrd after you boot? Did you boot with an initrd? Old initrd: fil[hjl@gnu-20 tmp]$ file foo foo: Linux rev 1.0 ext2 filesystem data New initrd: [hjl@gnu-64 tmp]$ file foo foo: ASCII cpio archive (SVR4 with no CRC) I am not sure if the new /initrd is mounted at all during the boot. It doesn't look like it is. If it is true, umount /initrd will lead to those messages. No, it should be mounted. Hm, the umount is wrapped in a check that it's actually mounted. So presumably there is something mounted there. It may come from mkinitrd-4.1.18-1. It puts umount /initrd/dev in init in initrd. The problem is rhgb-0.11.2-8 in RHEL 4 B2: [root@gnu-5 log]# rpm -q rhgb rhgb-0.11.2-8 [root@gnu-5 log]# /usr/bin/rhgb umount2: Invalid argument umount: /initrd: not mounted /usr/bin/rhgb is used by /etc/rc.d/rc.sysinit. An update rhgb-0.14.1-5 fixing the bug has been pushed to RHEL-4. It should fix this problem, thanks, Daniel |