Delete some old kernels?

On 07/09/2013 10:17 PM, Sumant Raykar wrote:
> Hello,
>
> I am new to Debian. I have Wheezy installed on my Thinkpad x230
> laptop. My kernel is 3.2.0-4-amd64.
> The problem I am getting is that my "/" directory is 100% full.
> Because of this, I am unable to update my kernel as I get an
> insufficient space error. However, my hard disk has almost 300 GiB free.
>
> When I tried to run lvxtend to expand the / directory, I get an
> "Insufficient free space: 256 extents needed, but only 0 available"
> error. The filesystem is ext4 and I am using an encrypted LVM.
> Some more detail can be found in these outputs:
>
> The problem:
>
> root@debian:/# lvextend -L +1G /dev/mapper/debian-root
>   Incorrect metadata area header checksum on /dev/sda1 at offset 4096
>   Extending logical volume root to 1.32 GiB
>   Insufficient free space: 256 extents needed, but only 0 available
>
> Some tests:
>
> root@debian:/# df -h
> Filesystem               Size  Used Avail Use% Mounted on
> rootfs                   322M  321M     0 100% /
> udev                      10M     0   10M   0% /dev
> tmpfs                    367M  816K  366M   1% /run
> /dev/mapper/debian-root  322M  321M     0 100% /
> tmpfs                    5.0M     0  5.0M   0% /run/lock
> tmpfs                    734M   84K  734M   1% /run/shm
> /dev/sda1                228M   19M  197M   9% /boot
> /dev/mapper/debian-home  275G   59G  203G  23% /home
> /dev/mapper/debian-tmp   368M   11M  339M   3% /tmp
> /dev/mapper/debian-usr   8.3G  5.3G  2.6G  68% /usr
> /dev/mapper/debian-var   2.8G  679M  2.0G  26% /var
>
>
> root@debian:/# pvdisplay
>   Incorrect metadata area header checksum on /dev/sda1 at offset 4096
>   --- Physical volume ---
>   PV Name               /dev/dm-0
>   VG Name               debian
>   PV Size               297.85 GiB / not usable 2.00 MiB
>   Allocatable           yes (but full)
>   PE Size               4.00 MiB
>   Total PE              76249
>   Free PE               0
>   Allocated PE          76249
>   PV UUID               NKMEex-9pcW-QMSi-dKEX-5XOI-nBXc-glrtNz
>   
>   "/dev/sda1" is a new physical volume of "243.00 MiB"
>   --- NEW Physical volume ---
>   PV Name               /dev/sda1
>   VG Name              
>   PV Size               243.00 MiB
>   Allocatable           NO
>   PE Size               0  
>   Total PE              0
>   Free PE               0
>   Allocated PE          0
>   PV UUID               a1KkXm-XB4C-o5SH-jnHz-BdZJ-u8v3-LscZ7W
>
>
> root@debian:/# mount
> sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
> proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
> udev on /dev type devtmpfs
> (rw,relatime,size=10240k,nr_inodes=467547,mode=755)
> devpts on /dev/pts type devpts
> (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=375388k,mode=755)
> /dev/mapper/debian-root on / type ext4
> (rw,relatime,errors=remount-ro,user_xattr,barrier=1,stripe=4,data=ordered)
> tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
> tmpfs on /run/shm type tmpfs
> (rw,nosuid,nodev,noexec,relatime,size=750760k)
> /dev/sda1 on /boot type ext2 (rw,relatime,errors=continue)
> /dev/mapper/debian-home on /home type ext4
> (rw,relatime,user_xattr,barrier=1,data=ordered)
> /dev/mapper/debian-tmp on /tmp type ext4
> (rw,relatime,user_xattr,barrier=1,stripe=4,data=ordered)
> /dev/mapper/debian-usr on /usr type ext4
> (rw,relatime,user_xattr,barrier=1,data=ordered)
> /dev/mapper/debian-var on /var type ext4
> (rw,relatime,user_xattr,barrier=1,data=ordered)
> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
> (rw,nosuid,nodev,noexec,relatime)
>
> The problem appears to be the "Free PE     0" from some research that
> I did online. I want to know how I can fix this issue so that I can
> then use lvextend to increase the size of the root directory. What is
> a recommended value for the size of this directory? I used the
> defaults suggested by the partition manager during installation, but
> it is clearly insufficient as seen above. Any help would be appreciated.
>
> Thanks,
> Sumant

Reply via email to