As the subject says.
I even cannot attach a 5 KB file.
==
Oops…
Trac detected an internal error:
IOError: [Errno 28] No space left on device
There was an internal error in Trac. It is recommended that you inform
your local Trac administrator
On 2 November 2010 17:35, Jeroen Demeyer 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...
> 3667802
>
> real 25m9.316s
> user 0m10.780s
> sys
There are definitely tools to do this sort of automated checking, but if
you're only concerned with inode usage then a simple shell script run as a
periodic cronjob is the most straightforward solution imho.
On Tue, Nov 2, 2010 at 1:20 PM, David Kirkby wrote:
> On 2 November 2010 15:52, Jeroen De
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...
3667802
real25m9.316s
user0m10.780s
sys 1m41.000s
That's 3.6 million files in /sagenb
--
To po
On 2 November 2010 15:52, Jeroen Demeyer 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:/
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/ ?
--
To post to this group, send an e
On Tue, Nov 02, 2010 at 04:24:41PM +0100, Jeroen Demeyer wrote:
> On 2010-11-02 16:18, Willem Jan Palenstijn wrote:
> > Possible options I can think of:
> >
> > * the filesystem could be out of inodes rather than out of space. (Use 'df
> > -i')
>
> That's the issue, on boxen:
> $ df -i
> Filesys
On 2010-11-02 16:18, Willem Jan Palenstijn wrote:
> Possible options I can think of:
>
> * the filesystem could be out of inodes rather than out of space. (Use 'df
> -i')
That's the issue, on boxen:
$ df -i
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/sda1448102
On Tue, Nov 02, 2010 at 07:42:51AM -0700, William Stein wrote:
> On Tuesday, November 2, 2010, David Kirkby wrote:
> > On 2 November 2010 00:10, William Stein wrote:
> >> On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer
> >> wrote:
> >>> Hi, I just got the following error on Trac:
> >>>
> >>> Oop
On Tuesday, November 2, 2010, David Kirkby wrote:
> On 2 November 2010 00:10, William Stein wrote:
>> On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer
>> wrote:
>>> Hi, I just got the following error on Trac:
>>>
>>> Oops…
>>> Trac detected an internal error:
>>>
>>> OSError: [Errno 28] No space
On 2 November 2010 00:10, William Stein wrote:
> On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer wrote:
>> Hi, I just got the following error on Trac:
>>
>> Oops…
>> Trac detected an internal error:
>>
>> OSError: [Errno 28] No space left on device:
>> '/var/trac/sage_trac/attachments/ticket/7513'
On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer wrote:
> Hi, I just got the following error on Trac:
>
> Oops…
> Trac detected an internal error:
>
> OSError: [Errno 28] No space left on device:
> '/var/trac/sage_trac/attachments/ticket/7513'
That's annoying. This was caused by me working on upg
Hi, I just got the following error on Trac:
Oops…
Trac detected an internal error:
OSError: [Errno 28] No space left on device:
'/var/trac/sage_trac/attachments/ticket/7513'
There was an internal error in Trac. It is recommended that you inform
your local Trac administrator and give him all the
13 matches
Mail list logo
