Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm using Mandrake 10.0 installed on a single disk with 2 partitions. A half gig swap and a 12 GB root.
Whenever I try to copy anything to the /tmp directory of any size like when I use KaudioCreator to rip a cd, I get an error message "Disk full". The disk has 9 GB free.
I've since moved to slackware and I'm using the same partitions made by mandrake. I have not tried to rip a cd yet but that command returns. 1 partition named /dev/hda5 of 13 GB. 2.2GB used, 11GB Free mounted on /.
It would have said about the same while using Mandrake.
That command is much faster then du though. Thanks.
When your ripping this cd, what are your configurations when ripping? Like have you set it to a limit in size... cause something it sounds from that program is using up all available space but when it errors out probably removes whatever is taking up space cause it can't finish the rip, etc.
Next time your ripping, run the df -h or try doing a:
du -h /tmp | sort -n
And it will list all the files and such and you can see which one is taking up the most space, etc.
Distribution: Mdk. 10 Powerpack Plus, Mdv. 2006-09, RHEL 4-6, Fedora 9-15, Mint (Ver?), and more
Posts: 22
Rep:
tmp folder in /var, as expansion
i'd rather not do this, considering a very cluttered file-tree, already! it's a good idea, to just symlink (ln -s), but isn't there a way to change the reported available space, for the current /tmp folder in the root partition?
Distribution: Mdk. 10 Powerpack Plus, Mdv. 2006-09, RHEL 4-6, Fedora 9-15, Mint (Ver?), and more
Posts: 22
Rep:
more kaudiocreator hell..
hmm.. i still get:
"Could not write file /tmp/kde-chris/kaudiocreatorJwjZMb.tmp Disk full."
I'm very interrested in just making the os show more available space, in the folder. i found a link to what i'm talking about, but i'm scared to do it, considering the file it references, is not present:
Don't make a link from /tmp to /var/tmp. Use /var/tmp in the program setup, such as k3b's setup. Some people have a ~/tmp directory that they use instead. The /home partition usually is quite large, plus a user has full access rights to ~/tmp/ as well. Another reason may be for privacy.
Distribution: Mdk. 10 Powerpack Plus, Mdv. 2006-09, RHEL 4-6, Fedora 9-15, Mint (Ver?), and more
Posts: 22
Rep:
kaudiocreator setup
in the setup for kaudiocreator, there is only one user-defined save path--the one for the encoded rips. this folder isn't even touched: before the application encodes them, it first saves them in /tmp. the output of df -h shows the /tmp folder is allowing 188mb of space, whereas the parent, root, shows far more space. i tried the /etc/vfstab file entry, from my previous post, rebooted, and the o.s. still reported the 188mb available. i've since deleted the /etc/vfstab file i created, citing no change. i even tried making a new /tmp, but this only affirmed that there is a file elsewhere, dictating the reported availability within /tmp. i really don't want to link to another location. i want the single /tmp folder, and an unlimited allocation. though maybe my frustration stems from incorrectly creating the link to my alternate temporary folder. who knows!?
as you see it, and confused,
Chris Rion
Last edited by eightysixme; 01-21-2005 at 03:54 PM.
Distribution: Mdk. 10 Powerpack Plus, Mdv. 2006-09, RHEL 4-6, Fedora 9-15, Mint (Ver?), and more
Posts: 22
Rep:
Why It's Called, "Linux Newbie"
well, as a typically straightforward and illuminating solution, i decided to use a spare unmounted partition as my mount for /tmp. the o.s. asked me if i wanted to move the contents of the current /tmp folder, into it; to which i chose 'yes'. just to be sure, i restarted--everything went well! also, i verified the available space:
aah! sweet satisfaction.. now, kaudiocreator is churning away. i'm very happy! this lends stock to the saying about learning more from mistakes, than success, eh? inspiration for this, came from another post @ LQ.org. gods bless this forum!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.