Bug 16081 - extra partitions NOT cleanly unmounted
Summary: extra partitions NOT cleanly unmounted
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.1
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard: Winston gold
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-12 21:07 UTC by Gene Czarcinski
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-08-15 18:58:36 UTC
Embargoed:


Attachments (Terms of Use)

Description Gene Czarcinski 2000-08-12 21:07:31 UTC
The first boot after an install, "extra" partitions are not cleanly
unmounted.  For example, I have a partition that I specified as
/home/vmware -- it had to be fsck on reboot because not cleanly unmounted.

As far as I can tell, the only partitions cleanly unmounted were / and
/usr.  The rest (/home, /home/vmware, /usr/src, and /usr/local) needed
fsck.

Comment 1 Glen Foster 2000-08-13 20:13:32 UTC
This defect is considered MUST-FIX for Winston Gold-release

Comment 2 Michael Fulbright 2000-08-14 17:01:55 UTC
How were these extra partitions created?


Comment 3 Gene Czarcinski 2000-08-14 21:02:38 UTC
Everything had been precreated.  Three out of six partitions were formated. 
Only / and /usr were unmounted.  /home, /home/vmware, /usr/local, and /usr/src
(formated) wee not unmounted cleanly.

Comment 4 Erik Troan 2000-08-15 18:58:34 UTC
We've tried 3-4 installs w/ prexisting partitions mounted. They all mounted and
unmounted fine, and gave a clean reboot. If you can give more details on this,
please reopen the bug.


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