Bug 29691 - filesystems not umounted cleanly after install completes
filesystems not umounted cleanly after install completes
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.1
i386 Linux
high Severity medium
: ---
: ---
Assigned To: Erik Troan
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-26 21:15 EST by Ben Levenson
Modified: 2007-03-26 23:41 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-03-05 15:18:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Ben Levenson 2001-02-26 21:15:28 EST
build: qa0226.0
GUI-NFS-Workstation

hardware: HP Eagle (in lab)
PIII 600/256M RAM
adaptec (aic78xx) present, but cdrom and hard drive
are on IDE.

filesystems are not cleanly unmounted at the end of the installation.
check forced during system reboot.

steps to reproduce:
1- NFS-GUI install
2- complete a default installation
3- type <enter> at final install screen (or click on appropriate button).
4- system reboots immediately -- none of the expected messages
regarding unmounting filesystems are flashed on the screen.
5- filesystem check forced during next boot.

I can only reproduce this failure on the above system.
Text HTTP (custom-minimal) and NFS (custom-minimal, workstation)
completed successfully.
Comment 1 Glen Foster 2001-02-27 16:50:05 EST
See Preston about how to proceed troubleshooting/investingating this ASAP.
Comment 2 Glen Foster 2001-03-02 13:02:55 EST
This defect determined (by Michael Fulbright) to be MUST-FIX for Florence Gold
release.
Comment 3 Erik Troan 2001-03-05 13:21:15 EST
Unless we can reproduce this, we can't fix it. Brock, have you seen this?

Ben's report suggests that this exit path is bypassing init; I don't know why
this would happen.
Comment 4 Michael Fulbright 2001-03-05 14:44:28 EST
I have not seen this issue myself.  We should close it NOTABUG if it does not
turn up by the Gold date.
Comment 5 Ben Levenson 2001-03-05 15:14:07 EST
the problem was nearly 100% reproducible with the HP Eagle in the lab,
but it appears to have fixed itself in the qa0301.0.  
I'll update the bug if it happens again.
Comment 6 Matt Wilson 2001-03-05 15:18:20 EST
yes, I worked on this one for hours - I could never catch the offending bit that
cause the whole machine to reboot when you hit OK.  No output on console (oops)
or anything.  It seems to have gone away now, though.
Comment 7 Ben Levenson 2001-04-05 19:38:30 EDT
as I said above, this failure has only occured on a specific
system in the test lab.  It hasn't been misbehaving since
early March and the system has been tested with about every
tree since then....
closing.

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