Depends on the filesystem - for ext2/3, the number of inodes are fixed at fs creation time, while some (like reiserfs, I believe) don't have a fixed number of inodes. Not a BSD guy, but the same issues apply.
Either way, it would require the filesystem be reformatted. Of course, you could just delete some files =) You are deleting old session files, right? jcontonio wrote: > > Actually FreeBSD but you're exactly right. What's the best way to > solve this? > > On Mar 26, 1:30 pm, Jeff Abbott <[EMAIL PROTECTED]> wrote: >> jcontonio wrote, circa 2007-03-26 1:23 PM: >> >>> Every week or couple weeks, my application goes haywire, and in my >>> production.log I get, >>> No space left on device - /tmp/ruby_sess.938af5ba9b9a02ed >>> Visiting the site, it looks like it refreshes every second. >>> Any ideas? I am not running out of physical HD space, so this is >>> confusing. >> I'm assuming this is on Linux, and that you're running with the ext3 >> file system, but feel free to correct me if I'm wrong. It's possible >> that you've run out of inodes -- using the file system for session >> storage results in the creation of mind-boggling numbers of files, and >> that can exhaust the file systems inode resources quickly. Check the >> output of: >> >> df -i /tmp >> >> and see what it says under "IFree". >> >> Hope that helps, >> Jeff > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
