On Sun Jul 16 2000 at 11:18, Fenglou Mao wrote:
> Here is output of "ls, df, du", who can tell me why my "/" is full?
It isn't full, there's just over 100Mb still available.
> [root@hunter /]# ls
> bin disk1 disk5 dog1 dog4 home linux2 lost+found o2 root usr
> boot disk3 disk8 dog2 dog5 lib linux2_old mnt opt sbin var
> dev disk4 dog0 dog3 etc linux1 linux3 o1 proc tmp
>
> [root@hunter /]# df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/hda1 2016016 1912896 708 100% /
> /dev/hda3 17322592 10424 16432208 0% /dog0
By default, 5% of disk space is reserved for root - it looks like
what's going on here (I haven't done the maths here, too lazy I
guess:) [Oh hell... ok, 102412 "hidden" Mb, that's ~5% of 2Gb, so
that confirms it.]
To "reclaim" some of that extra "hidden" space, use the tune2fs
utility. But DO leave at least some reserved space, even if it's
only 1 or 2%....
tune2fs -m1 /dev/hda1
BTW, just a warning... if you have a boot kernel on that partition,
bad news if it is ever put into an area above the 1024 cylinder mark
(unless your bios knows how to handle it). If so, then the bios
will never be able to find it, and you won't be able to boot your
system (unless you do it from a floppy or another disk). What you
should do is create a small 8-16Mb hda1 (or a logical hda5 in an
extended hda1 partition) that is mounted as /boot so that you are
guaranteed to have the kernel (in initrd etc) boot images below the
1024 cylinder point.
Cheers
Tony
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
Tony Nugent <[EMAIL PROTECTED]> Systems Administrator, RHCE
GrowZone OnLine (a project of) GrowZone Development Network
POBox 475 Toowoomba Oueensland Australia 4350 Ph: 07 4637 8322
-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-=*#*=-
