Hard Drive Very Full - Alocating disk space

Discussion in 'Installation/Configuration' started by sheshes, Jun 15, 2011.

  1. sheshes

    sheshes Member

    Hi after a couple of years my Ispconfig3 server shows a critical warning that my hard drive is very full.

    Filesystem Type Size Used Available Use% Mounted on
    /dev/mapper/server-root
    ext3 398G 72G 306G 20% /
    none devtmpfs 1002M 184K 1002M 1% /dev
    none tmpfs 1007M 116K 1007M 1% /dev/shm
    none tmpfs 1007M 120K 1007M 1% /var/run
    none tmpfs 1007M 0 1007M 0% /var/lock
    none tmpfs 1007M 0 1007M 0% /lib/init/rw
    /dev/cciss/c0d1p5
    ext2 228M 203M 14M 94% /boot

    I am pretty sure I have a lot of unused space yet, but I'm still getting this warning.

    Any help is much appreciated.

    Thanks
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You get the warning beacuse the /boot partition is 94% full.
     
  3. sheshes

    sheshes Member

    I 've realised that but how can I fix it? Boot is supposed to stay the same even after updates right?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    No, /boot partition can fill up with updates, e.g. when a new kernel or bootloader update gets installed.
     
  5. sheshes

    sheshes Member

    so what can I do?
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    There is not much that you can do, hopefully the next kernel and grub updates fit into the partition. The only other option is to repartition the system, but that may cause data loss.
     
  7. sheshes

    sheshes Member

    i see. Thanks a lot till

    I have all these


    abi-2.6.28-19-server initrd.img-2.6.28-19-server System.map-2.6.32-32-generic-pae
    abi-2.6.31-22-generic-pae initrd.img-2.6.31-22-generic-pae vmcoreinfo-2.6.28-19-server
    abi-2.6.32-27-generic initrd.img-2.6.32-27-generic vmcoreinfo-2.6.31-22-generic-pae
    abi-2.6.32-27-generic-pae initrd.img-2.6.32-27-generic-pae vmcoreinfo-2.6.32-27-generic
    abi-2.6.32-28-generic initrd.img-2.6.32-28-generic vmcoreinfo-2.6.32-27-generic-pae
    abi-2.6.32-28-generic-pae initrd.img-2.6.32-28-generic-pae vmcoreinfo-2.6.32-28-generic
    abi-2.6.32-29-generic initrd.img-2.6.32-29-generic vmcoreinfo-2.6.32-28-generic-pae
    abi-2.6.32-29-generic-pae initrd.img-2.6.32-29-generic-pae vmcoreinfo-2.6.32-29-generic
    abi-2.6.32-30-generic initrd.img-2.6.32-30-generic vmcoreinfo-2.6.32-29-generic-pae
    abi-2.6.32-30-generic-pae initrd.img-2.6.32-30-generic-pae vmcoreinfo-2.6.32-30-generic
    abi-2.6.32-31-generic initrd.img-2.6.32-31-generic vmcoreinfo-2.6.32-30-generic-pae
    abi-2.6.32-31-generic-pae initrd.img-2.6.32-31-generic-pae vmcoreinfo-2.6.32-31-generic
    abi-2.6.32-32-generic initrd.img-2.6.32-32-generic vmcoreinfo-2.6.32-31-generic-pae
    abi-2.6.32-32-generic-pae initrd.img-2.6.32-32-generic-pae vmcoreinfo-2.6.32-32-generic
    config-2.6.28-19-server lost+found vmcoreinfo-2.6.32-32-generic-pae
    config-2.6.31-22-generic-pae memtest86+.bin vmlinuz-2.6.28-19-server
    config-2.6.32-27-generic System.map-2.6.28-19-server vmlinuz-2.6.31-22-generic-pae
    config-2.6.32-27-generic-pae System.map-2.6.31-22-generic-pae vmlinuz-2.6.32-27-generic
    config-2.6.32-28-generic System.map-2.6.32-27-generic vmlinuz-2.6.32-27-generic-pae
    config-2.6.32-28-generic-pae System.map-2.6.32-27-generic-pae vmlinuz-2.6.32-28-generic
    config-2.6.32-29-generic System.map-2.6.32-28-generic vmlinuz-2.6.32-28-generic-pae
    config-2.6.32-29-generic-pae System.map-2.6.32-28-generic-pae vmlinuz-2.6.32-29-generic
    config-2.6.32-30-generic System.map-2.6.32-29-generic vmlinuz-2.6.32-29-generic-pae
    config-2.6.32-30-generic-pae System.map-2.6.32-29-generic-pae vmlinuz-2.6.32-30-generic
    config-2.6.32-31-generic System.map-2.6.32-30-generic vmlinuz-2.6.32-30-generic-pae
    config-2.6.32-31-generic-pae System.map-2.6.32-30-generic-pae vmlinuz-2.6.32-31-generic
    config-2.6.32-32-generic System.map-2.6.32-31-generic vmlinuz-2.6.32-31-generic-pae
    config-2.6.32-32-generic-pae System.map-2.6.32-31-generic-pae vmlinuz-2.6.32-32-generic
    grub System.map-2.6.32-32-generic vmlinuz-2.6.32-32-generic-pae


    my system is using only 2.6.32-32-generic-pae so is it safe to remove the old ones to make space?
     
    Last edited: Jun 15, 2011
  8. falko

    falko Super Moderator Howtoforge Staff

    Yes, you can remove the old ones, but instead of using rm, please check if thisan be done with your distribution's package manager.
     
  9. sheshes

    sheshes Member

    That's great. I am using Ubuntu server and as I saw is only by rm.
     

Share This Page