Bug 55323 - Error messages while booting and rebooting/halting
Summary: Error messages while booting and rebooting/halting
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-29 18:25 UTC by Jordan Breeding
Modified: 2014-03-17 02:24 UTC (History)
1 user (show)

Fixed In Version: FC4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-29 19:18:55 UTC
Embargoed:


Attachments (Terms of Use)

Description Jordan Breeding 2001-10-29 18:25:07 UTC
Description of Problem:

  While booting up the swapon program reports the following errors:

== START ERROR ==
swapon: /dev/hda2: Device or resource busy
Enabling swap:          [ok]
== END ERROR ==

  Swap does get enabled correctly but while using the old mount-2.11f and
initscripts from RedHat 7.1 the errors never happend, this error has only
been visible since the upgrade to Redhat 7.2.  Another set of erors from
the mount/umount programs of the mount-2.11g package are seen during
reboot/halting they are as follows:

== START ERRORS ==
Turning off quota:    [ok]
Unmounting file systems:  umount2: Invalid argument
                      [ok]
umount2: Invalid arugment
umount: /dev/hda11: not mounted
umount: /export0: Illegal seek
umount2: Device or resource busy
umount: /dev: Device or resource busy

Remounting remaining filesystems (if any) readonly
Halting system...
== END ERRORS ==

  Here is the output of `mount` while booted up:

== OUTPUT `mount` ==
/dev/hda5 on / type ext3 (rw,data=journal)
proc on /proc type proc (rw)
devfs on /dev type devfs (rw)
/dev/hda1 on /boot type ext3 (rw,data=journal)
/dev/hda11 on /export0 type ext3 (rw,data=journal)
/dev/hda10 on /home type ext3 (rw,data=journal)
/dev/hda7 on /opt type ext3 (rw,data=journal)
/dev/hda8 on /tmp type ext3 (rw,data=journal)
/dev/hda6 on /var type ext3 (rw,data=journal)
/dev/hda9 on /root type ext3 (rw,data=journal)
/export0/downloads on /downloads type bind (rw,bind)
/export0 on /export type bind (rw,bind)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
automount(pid804) on /misc type autofs
(rw,fd=5,pgrp=804,minproto=2,maxproto=4)
== OUTPUT `mount` ==

  These are not necessarily horrible errors since the system still seems to
function perfectly but they are quite annoying, I have seen the same set of
errors on a freshly installed RedHat 7.2 Beta (Roswell2) system at my place
of business as well.  What is causing this to happen the mount package? 
Broken initscripts?  I thought it might be the actual mount-2.11g package
though since it seems the binary programs themselves are outputing most if
not all of the error messages.

Version-Release number of selected component (if applicable):
mount-2.11g-5

How Reproducible:
Always

Steps to Reproduce:
1. Run RedHat 7.2 (Enigma) or RedHat 7.2 Beta (Roswell2)
2. Reboot the system or halt the system
3. Boot the system

Actual Results:
Errors output during both reboot/halt and boot up.

Expected Results:
Clean reboot, halt and boot up expected.

Additional Information:
This machine runs SMP with a highmem kernel, dual 1 GHz Pentium III
processors and 1 GB of RAM.

Comment 1 Bernhard Rosenkraenzer 2001-10-30 11:33:54 UTC
Almost certainly not a problem with userland mount. Reassigning.


Comment 2 Jordan Breeding 2001-10-30 17:49:24 UTC
While messing around trying to fix this I figured out that in
/etc/rc.d/rc.sysinit the second time that swapon gets called it used to be
called as `swapon -a > /dev/null 2>&1` and now it was `swapon -a`, I changed it
back to the old line and that fixed my errors on boot up.  To fix the errors on
reboot/shutdown I did a lot of work to make a hybrid of the old initscripts
/etc/init.d/halt and the new /etc/init.d/halt, which still does the same work as
the new one but in the order that the old initscripts did things and now all of
those messages are gone as well.  If you would like to see a diff of each of
them I can provide it, thanks.

Comment 3 Bill Nottingham 2005-09-29 19:18:55 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of
response.

This should be more or less fixed, as we only call swapon once in current
releases, such as Fedora Core 4.


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