8
2
I have a 200GB HD and have just installed Linux Mint (12 - KDE) as the only OS (I formatted and wiped my previous Windows 7 installation). I am in the process of installing my "sandbox" and because I'm new to Linux am installing all of the stuff that can't be found with package managers under my /home/<username>
directory, stuff like:
- Jenkins CI
- Artifactory
- Eclipse and all of its plugins
- AppDynamics Lite
- WebCastellum
And others. While trying to install an Eclipse plugin (Google's GAE/GWT plugin) I got a notification that I was about to run out of space under my /home
directory, and sure enough, the Eclipse plugin failed to finish installing because it ran out of available disk space.
When I run df
from the terminal I get this output:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda5 13783792 12133900 958336 93% /
udev 4016004 4 4016000 1% /dev
tmpfs 1611136 1056 1610080 1% /run
none 5120 0 5120 0% /run/lock
none 4027832 84 4027748 1% /run/shm
Again, new to Linux, so this doesn't mean much to me, but it looks like I am currently using up 93% of my disk (which I assume is /dev/sda5
)?
That's crazy!?! This is 200GB and all I've done is install a few relatively-tiny apps. I don't even think I have any media (photos, videos, etc.) on this machine yet! I literally installed the OS and started setting up my sandbox!
A few things:
- Am I reading this
df
output correctly? - Do I need to "mount" or do something special with my
/home
directory that I failed to do? - Is it common to get this out-of-disk-space error under
/home
if you're an inexperienced Linux user (and did not do any mounting or other Linux magic as prescribed above)? - How could I possibly be at 93%?!?! Could I have a virus?!?
Thanks in advance for any help here!
Edit: although it currently reads 93% now, last night (which is when I got these errors) it was at 99%.
Output from lsblk
:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 232.9G 0 disk
├─sda1 8:1 0 211.8G 0 part
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 13.2G 0 part /
└─sda6 8:6 0 7.9G 0 part [SWAP]
sr0 11:0 1 1024M 0 rom
sdb 8:16 1 1.9G 0 disk
└─sdb1 8:17 1 1.9G 0 part /media/PKBACK# 001
sr1 11:1 1 7M 0 rom
Thanks @grawity - if I did this then it was certainly not by intention! I just used all the defaults that the Mint installer offered me because this was my very first Mint install and the only other experience I've had was with Ubuntu. Question: does
gparted
simply give me more space or does it wipe the 13 - 14 GB I have in addition to giving me space? I'd like to try it out but would have to blow out all the installs I've done so far. Thanks again! – pnongrata – 2012-08-31T13:18:47.337@zharvey: I don't know what actual partitions you have, and what exactly are you telling
gparted
to do, when you are saying "give more space". Are you using it to create a new partition, or resize an existing one? Where did you find the other 190 GB – as a separate partition, or as "unallocated" space? – user1686 – 2012-08-31T13:21:41.883Please see my edit and the output for
lsblk
- looks like I actually have more than 200GB (surprise!). I only knew that because when this was a Windows machine I knew it had 200GB (and apparently, more) on it. Again, I certainly didn't request Mint to do this explicitly (the 13GB partition). I just used the defaults it offered and this was the result. – pnongrata – 2012-08-31T13:25:32.193Ultimately, I'd like to end up merging
sda1
andsda5
together, as there is no purpose for them to be separate. – pnongrata – 2012-08-31T13:30:44.6172@zharvey: So like I guessed, there is another partition,
/dev/sda1
, created specifically for/home
... It is actually more convenient for/home
to be separate, it makes OS reinstalls much easier. If you want to merge them, you will have usegparted
from a LiveCD. – user1686 – 2012-08-31T13:33:00.790OK thanks again (+1) - last followup: I'm not understanding something here. You say that
sda1
was created for/home
, but it seems like/home
is included in this 13GB mini-partition?! That certainly seems to be the case since that is where I'm getting the disk space errors. So: is it thatsda1
was originally created for/home
, but I just never mounted it there? Otherwise please help me understand the relationship betweensda1
and/home
, and why I am getting these errors. Thanks again! – pnongrata – 2012-08-31T13:36:27.870Also, if it is just possible for me to mount
/home
tosda1
right now, I'd rather do that and do all the merging stuff later. I don't really care that much about the 13GB onsda5
. – pnongrata – 2012-08-31T13:39:26.383@zharvey:
/home
exists on the root mini-partition because it was intended to be used as the mountpoint – a normal, empty directory on top of which another partition (the large one) was supposed to be mounted. (The installer created a small "root" partition and a large "home" partition, but forgot to actually have the "home" partition mounted.) As for how to mount it, see the updated post. – user1686 – 2012-08-31T13:49:51.173