At 06:55 AM 10/5/00 -0400, Ben Logan wrote:
>this is possible. What I don't understand is why that wasn't a
>problem before--seems like that would be a problem regardless of
>where the /usr/lib directory is mounted. I.e., it has to be
>unmounted regardless of where it is.
Actually it doesn't strictly speaking need to be unmounted in order to shut
down cleanly. I have no clue why you would have this problem (I don't), but
you should be able to solve it by re-mounting your /usr (or /usr/lib, I
forget which was the mountpoint) as read-only during your shutdown phase. A
read-only filesystem is considered clean even if it is mounted when the
system shuts down (for good reason).
Also, I have had a vaguely similar problem with shutting down when I had
write-caching (-W1) enabled with hdparm. This can be gotten around by
disabling write caching as part of your shutdown/reboot scripts (in RH7 I
think they even provide a /etc/rc.d/init.d/something service script to
handle this).
>> was and move something else with a symlink, like /usr/share. That one
>> shouldn't give you such a problem (unless umount2 is the problem) and it's
>> generally huge, which would free up a lot of space.
In terms of freeing up space (particularly when you neither have more disks
available nor want to delete stuff) I've had great results with e2compr
(see http://opensource.captech.com/e2compr/index.html for info & dl) which
allows you to apply selective transparent compression within an ext2
filesystem.
--
Who is this General Failure, and why is he reading my hard disk?
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
