My Kubuntu install, upgraded to 12.04 from 10.04, was running out of disk space on root. It was installed on a root.disk file on Windows NTFS partition. First tried googling and found this post, so did
Booted into Ubuntu 13.10 Live DVD, navigated to the root.disk file.
sudo dd if=/dev/zero bs=1MiB of=root.disk conv=notrunc oflag=append count=1000
(where count is the number of MiB to add)
Then mounted it with
sudo losetup /dev/loop1 root.disk
and resized with
sudo losetup -c /dev/loop1
sudo resize2fs /dev/loop1
At this point, the system alerts me to
Please run e2fsck -f /dev/loop1
So I do a
sudo e2fsck -f /dev/loop1
and then repeat the
sudo resize2fs /dev/loop1
Et voila! Done.
Only now did I see the official Wubi guide, which gives a solution to this very problem, in a "safe" way.
sudo apt-get clean
sudo apt-get autoclean
sudo apt-get autoremove
sudo apt-get install localepurge
Also tried listing packages withdpkg-query -W --showformat='${Installed- Size} ${Package}\n' | sort -nr | less
and removing those which I did not need. But still, free space on disk was only less than a GB, compiling was eating up space too. So, tried googling increase size of Linux loop drive, and found this forum thread. That had a lot of "dangerous" warnings. Lost track of it since it was on the Mac, saw the Mac Safari history as given at this post - the History.plist file was a binary file, opened using PsPad's Hex editor.... Then found this solution by googling increase size of /dev/loop0Booted into Ubuntu 13.10 Live DVD, navigated to the root.disk file.
sudo dd if=/dev/zero bs=1MiB of=root.disk conv=notrunc oflag=append count=1000
(where count is the number of MiB to add)
Then mounted it with
sudo losetup /dev/loop1 root.disk
and resized with
sudo losetup -c /dev/loop1
sudo resize2fs /dev/loop1
At this point, the system alerts me to
Please run e2fsck -f /dev/loop1
So I do a
sudo e2fsck -f /dev/loop1
and then repeat the
sudo resize2fs /dev/loop1
Et voila! Done.
Only now did I see the official Wubi guide, which gives a solution to this very problem, in a "safe" way.
No comments:
Post a Comment