Bug 5042 - filesystem not unmounted cleanly
Summary: filesystem not unmounted cleanly
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: filesystem
Version: 1.0
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-09-10 11:32 UTC by fouri_s
Modified: 2014-03-17 02:09 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 1999-09-25 03:27:15 UTC


Attachments (Terms of Use)

Description fouri_s 1999-09-10 11:32:01 UTC
hi
i am not sure how to use this page proper.

bug 1751 about fsck and not umount proper.
this is happening on 3 different systems that i have.
after using x-windows (kde or gnome) [normly after a long
session [[lots of mem useage.]]] and exiting x-session there
is an empty core in pwd. at shutdown (doesn't matter what
method) umount doesn't umount proper. / busy. i tried sync
but doesn't work but problem still there. at reboot fsck.
when using only command prompt (no x-win) i can't emulate
problem. systems stable.

sp
fouri_s@mtn.co.za

Comment 1 Bill Nottingham 1999-09-25 03:27:59 UTC
This should be fixed in the latest initscripts in Raw Hide.
Anything using filesystems should be terminated.


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