Rick,
Take the system down to single user mode (telinit 1).
Remount the root file system read-only (you may have to unmount the other
file systems first)
mount /dev/dasdb1 / -r -o remount
Run e2fsck on it (you'll have to respond to the message about being _sure_
you want to do this against a mounted file system)
Remount the root file system read-write
mount /dev/dasdb1 / -w -o remount
Bring the system back up to the correct runlevel (telinit 2? telinit 3?
check /etc/inittab)
Mark Post
-----Original Message-----
From: Rick Truett [mailto:rtruett@;paonline.com]
Sent: Tuesday, October 22, 2002 2:56 PM
To: [EMAIL PROTECTED]
Subject: Root file system question
I had a situation where /dev/dasdb1 the root file system was 100% full.
There were logs in /var/log that were huge, so I deleted them and rebooted
(shutdown -r now) Upon restart a df command still reports the file system
100% full.
I ran a 'e2fsck /dev/dasdb1 -f -v -n' and received a few errors (of course
not fixed thanks to -n). The errors are: 'block bit map differences',
'Inode 80135, i_blocks is 64, should be 8.'.
I would like to run fsck against the root file system, how do I do it?
Thank you....
