On 2 November 2010 15:52, Jeroen Demeyer <[email protected]> wrote: > On 2010-11-02 16:44, Willem Jan Palenstijn wrote: >> At a guess I'd say /sagenb is causing this? At least a 'find | wc -l' there >> took longer to complete than I cared to keep it running... > > Could this also explain the recent slowness of http://www.sagenb.org/ ?
I would personally doubt it - I would expect errors, not slowness if there are no inodes left. ext3 file systems are not immune to fragmentation issues. Certainly running low on disk space could cause the file system to become very fragmented, which would reduce speed. Systems like trac failing due to lack of disk space seem quite a common occurrence. It might be worth investigating some tools which will send an email if a system is unreachable, or disk space is getting too close to the maximum. I'm sure there are tools for this, but if not a cron job with a few lines of code cooud send an email when disk usage gets close to ithe limits. -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
