I just installed LAMPd and I have disk space problems.
I did a "df -h" to get these results.
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 965M 965M 0 100% /
varrun 252M 72K 252M 1% /var/run
varlock 252M 0 252M 0% /var/lock
udev 252M 44K 252M 1% /dev
devshm 252M 0 252M 0% /dev/shm
/dev/sdb1 9.9G 169M 9.2G 2% /storage
If I try and move something from the /tmp directory to say ~/opt because I'm trying to install additional things on this instance of the jumpbox I get errors similar to can't copy no space on disk although I'm paraphrasing since I lost the exact error because of a reboot. It did say low disk space or no disk space.
It does say there is 9.2 gig available on /dev/sdb1 but I'm thinking I'm only using the 965 meg on /dev/sda1, if I'm guessing correctly by default the file system directories:
bin dev home initrd.img lib mnt proc sbin storage tmp var
boot etc initrd jumpbox media opt root srv sys usr vmlinuz
...are all on /dev/sda1? This seems to be a difficulty if anyone wants to add additional components to these boxes if I can't even use the space on /dev/sdb1. The /var/data/public folder IS ON THE 965 meg partition...that makes no sense because I'll quickly run out of real estate.
Am I correct in my assumptions or is there something else wrong? I will have to use GParted to move stuff around I guess. If it blows up no big deal for now, I might have to dump the JumpBox LAMPd and roll my own.
Any thoughts?
Thanks!
I had the same issues
I had the exact same issues. When connecting via ftp to upload website files I was not setting the initial path which would bring me to /home/admin and any time I dumped files to that directory it would eat up 965M partition.
I looked further at the documentation and it mentioned /var/data/public so when I set the initial path to this and uploaded files it took open space away from the proper data 10GB partition. All works for me now.
LAMPd Disk Space Problem
We have also concluded that the free disk space on all of the JumpBoxes is inconvenient at best or insufficient at worst. The upcoming Lucid base JumpBoxes (any recent JumpBox with a 0.9 version or the upcoming 1.5 version JumpBoxes) will have an expanded root disk and may include a dedicated disk for the /usr directory. So, at least in the future, disk space won't be so tight.
At this point, on every JumpBox, the majority of the free space is in the /storage disk, this is a 10GB disk by default. Each JumpBox is designed so that the application data (database and files) end up in that /storage disk. If you are using a LAMP or LAPP JumpBox then you need to be aware that this is where you should put things. Use the "mount" command to see which directories are mounted under /storage.
Also, it is up to the user to decide if the default 10GB /storage disk is sufficient. If it is not, then the supported mechanism for increasing that disk space is documented here:
http://wiki.jumpbox.com/doc/runtime/faq/larger_storage_disk
Austin
LAMPd Disk Space Problem
Type 'mount' and you will see that a number of the directories that appear to be in /dev/sda1 are actually bind mounted onto /dev/sdb1.
If you have apt-get installed stuff it will mostly go into /dev/sda1, but the expectation is that you will only need to install maybe 100MB of dependencies for whatever app you are installing ... then the app, and its data, are supposed to end up on the 10GB data disk /dev/sdb1.
One thing to be aware of, if you apt-get install something, the downloaded packages are stored and will occasionally need clearing out, use 'sudo apt-get clean'.
Austin