Bug 85283 - Upgrade stopped due to misconfiguration of /etc/fstab
Summary: Upgrade stopped due to misconfiguration of /etc/fstab
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: phoebe
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-27 14:00 UTC by Roman Szarowski
Modified: 2007-04-18 16:51 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2003-02-27 22:48:47 UTC


Attachments (Terms of Use)

Description Roman Szarowski 2003-02-27 14:00:19 UTC
Description of problem:

When I was trying to upgrade my redhat from 8.0.93 to 8.0.94, installation process
did not let me upgrade due to changes in a partition not related to linux (vfat).
Installator has just looked probably to /etc/fstab and allow only "Cancel" or
"Reboot".
When I changed fstab, installation proceeded.

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

8.0.93

How reproducible:


Steps to Reproduce:
1. Boot installation
2. Upgrade
3. Choose packages and install
    
Actual results: Installation stopped due to misconfiguration in fstab


Expected results: To check root partition and to allow installation no matter if
there are
changes in other partitions.


Additional info:

Comment 1 Jeremy Katz 2003-02-27 17:21:12 UTC
Determining what's an "essential" filesystem to be mounted vs not is virtually
impossible considering you could have symlinks wherever you want on one
filesystem pointing to another, so we require that all filesytems in the fstab
be mounted for an upgrade to continue.

Comment 2 Roman Szarowski 2003-02-27 22:20:50 UTC
And what about to ask the user in a separate dialog whether he is going 
to change fstab ? It would be exactly the same what I had to do. 
I changed the fstab and launched the installation again (just wasting 
of time). 

Comment 3 Jeremy Katz 2003-02-27 22:48:47 UTC
anaconda assumes that you have a well-formed system on an upgrade.  Having your
fstab be correct is one part of this.


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