Last edited by jocko; September 2nd, 2009 at 09:36 PM.
you are clearly getting much better advice from Bucky Ball and jocko, so I will bow out, but to answer your question, there is nothing wrong with swap being on sda5 and /home being on sda7. That is exactly what I would expect, however, your fstab clearly has these partitions the other way around.
UUID=488e312f-dd1e-40fb-b90b-24265e70c98f /home ext3 relatime 0 2
UUID=de7a43f2-41b6-42ad-a6c0-e759096b3075 /tmp ext3 relatime 0 2
UUID=af56cc8b-a392-4589-bbc2-3a1054187a02 none swap sw 0 0
if you got some RAM to spare you should just through /tmp on a ramdisk.. add this line to /etc/fstab
Code:tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
Wow, thanks for all the advice everyone! This is a lot to go thru for me and I'm just about to head out of town for an extended labour-day weekend. I won't have a chance to try out your suggestions until I get back but I'll post my results as soon as I have some to report.
talk to you next week.
Have a good one! rbc's post #11 looks promising.
type this in a terminal, and post the output
this will give us some more drive info.Code:sudo blkid
"Free software is a matter of liberty, not price." -- Richard Stallman
So don't forget to tip your software authors!
I ran into the same problem as freeicetime, a program requiring more tmp space than I had on my tmp partition. (Using Ubuntu 10.04, 1GB tmp partition with 3% usage before I run the program)
Simply commenting the /tmp mount line in /etc/fstab resulted in
/usr/lib/libgconf2-4/gconf-sanity-check-2 exit code 256
when X was trying to start.
Turns out permissions on /tmp changed from
drwxrwxrwt /tmp (when my tmp partition was mounted)
drwxr-xr-w /tmp (when no longer mounting anything on /tmp)
I fixed this doing
Code:sudo chmod 777 /tmp
and rebooting once more
/tmp is now no longer a seperate partition, but part of my / partition
Hope it helps anyone else running into this.