how to increase /root space
Mike Reinehr
cmr
Mon May 17 11:51:52 PDT 2004
There's your trouble. You have the files associated with five (5) different
kernels in your boot partition:
2.4.9
2.4.7-10
2.4.18-19.7.x
2.4.18-24.7.x
2.4.18-26.7.x
2.4.18-27.7.x
It appears that 2.4.18-27.7.x is the last and current kernel, the one you are
booting. It that's the case you can free up a lot of space by deleting the
unused kernel image files. (Just make sure that your lilo or grub
configurations reflect the correct kernel image or you won't be able to
reboot.)
cmr
PS These lists would be a lot easier to read if you would set your margins a
little wider to minimize the line wrapping.
On Saturday 30 August 2003 12:06 pm, you wrote:
> Hi
>
> Thanks again.
>
> >>Swapana,
> >>Each time you upgrade with up2date and the kernal is
>
> updated you add files to
>
> >>boot. Clean up the old kernals and you will once
>
> again have the space you
>
> >>need. Remember to make lilo or grub relect the
>
> changes.
>
> Ok , i did not know that thanks...here is the
> directory listing of the /boot
>
> [root at server boot]# ls -l
> total 20574
> -rw-r--r-- 1 root root 5824 Jun 24
> 2001 boot.b
> -rw-r--r-- 1 root root 612 Jun 24
> 2001 chain.b
> -rw-r--r-- 1 root root 42257 Dec 12
> 2002 config-2.4.18-19.7.x
> -rw-r--r-- 1 root root 42257 Jan 31
> 2003 config-2.4.18-24.7.x
> -rw-r--r-- 1 root root 42257 Feb 24
> 2003 config-2.4.18-26.7.x
> -rw-r--r-- 1 root root 42257 Mar 14
> 03:56 config-2.4.18-27.7.x
> drwxr-xr-x 2 root root 1024 Mar 17
> 21:27 grub
> -rw-r--r-- 1 root root 196914 Dec 21
> 2002 initrd-2.4.18-19.7.x.img
> -rw-r--r-- 1 root root 198824 Feb 13
> 2003 initrd-2.4.18-24.7.x.img
> -rw-r--r-- 1 root root 197466 Mar 8
> 19:57 initrd-2.4.18-26.7.x.img
> -rw-r--r-- 1 root root 197055 Mar 17
> 21:26 initrd-2.4.18-27.7.x.img
> -rw-r--r-- 1 root root 427637 Apr 19
> 2002 initrd-2.4.7-10.img
> lrwxrwxrwx 1 root root 14 Dec 21
> 2002 kernel.h -> kernel.h-2.4.9
> -rw-r--r-- 1 root root 405 Dec 21
> 2002 kernel.h-2.4.9
> drwxr-xr-x 2 root root 12288 Apr 19
> 2002 lost+found
> -rw-r--r-- 1 root root 23108 Jun 24
> 2001 message
> -rw-r--r-- 1 root root 21282 Jun 24
> 2001 message.ja
> lrwxrwxrwx 1 root root 25 Mar 17
> 21:26 module-info -> module-in
> fo-2.4.18-27.7.x
> -rw-r--r-- 1 root root 15436 Dec 12
> 2002 module-info-2.4.18-19.7.x
> -rw-r--r-- 1 root root 15436 Jan 31
> 2003 module-info-2.4.18-24.7.x
> -rw-r--r-- 1 root root 15436 Feb 24
> 2003 module-info-2.4.18-26.7.x
> -rw-r--r-- 1 root root 15436 Mar 14
> 03:56 module-info-2.4.18-27.7.x
> -rw-r--r-- 1 root root 13598 Sep 6
> 2001 module-info-2.4.7-10
> -rw-r--r-- 1 root root 640 Jun 24
> 2001 os2_d.b
> lrwxrwxrwx 1 root root 24 Mar 17
> 21:26 System.map -> System.map-2.4.18-27.7.x
> -rw-r--r-- 1 root root 490515 Dec 12
> 2002 System.map-2.4.18-19.7.x
> -rw-r--r-- 1 root root 490643 Jan 31
> 2003 System.map-2.4.18-24.7.x
> -rw-r--r-- 1 root root 490643 Feb 24
> 2003 System.map-2.4.18-26.7.x
> -rw-r--r-- 1 root root 490673 Mar 14
> 03:56 System.map-2.4.18-27.7.x
> -rw-r--r-- 1 root root 435039 Sep 6
> 2001 System.map-2.4.7-10
> -rwxr-xr-x 1 root root 2984033 Dec 12
> 2002 vmlinux-2.4.18-19.7.x
> -rwxr-xr-x 1 root root 2986554 Jan 31
> 2003 vmlinux-2.4.18-24.7.x
> -rwxr-xr-x 1 root root 2986554 Feb 24
> 2003 vmlinux-2.4.18-26.7.x
> -rwxr-xr-x 1 root root 2986589 Mar 14
> 03:56 vmlinux-2.4.18-27.7.x
> lrwxrwxrwx 1 root root 21 Mar 17
> 21:26 vmlinuz -> vmlinuz-2.4.18-27.7.x
> -rw-r--r-- 1 root root 1064322 Dec 12
> 2002 vmlinuz-2.4.18-19.7.x
> -rw-r--r-- 1 root root 1064546 Jan 31
> 2003 vmlinuz-2.4.18-24.7.x
> -rw-r--r-- 1 root root 1064547 Feb 24
> 2003 vmlinuz-2.4.18-26.7.x
> -rw-r--r-- 1 root root 1065261 Mar 14
> 03:56 vmlinuz-2.4.18-27.7.x
> -rw-r--r-- 1 root root 802068 Sep 6
> 2001 vmlinuz-2.4.7-10
> [root at server boot]#
>
> >>Is this the same network that you had the earlier
>
> possible security
>
> >>problems on?
>
> No it is our servers' network. Previously was of our
> client's that is under different network...
>
> >>Boot shouldn't change much and certainly the size of
>
> boot shouldn't be
>
> >>changing unless there are some very strange things
>
> going on.I'd be very
>
> >>concerned about why boot was growing, who was
>
> causing it to grow (if
>
> >>it's not you) and what the additional bulk consists
>
> of.
>
> We are only upgrading the kernel occassionally with
> up2date . I have given above the /boot directory
> listing,,,
>
> pl. guide me where i am making mistakes....Moreover
> also suggest me how we can increase its disk space ,
> it is only 21mb..
>
>
> Best regards.
> -Swapna
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> Linux-users mailing list
> Linux-users at linux-sxs.org
> Unsubscribe/Suspend/Etc ->
> http://www.linux-sxs.org/mailman/listinfo/linux-users
--
Debian 'Sarge': Registered Linux User #241964
----
"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC
--------
More information about the Linux-users
mailing list