>> Hey gang,
>>
>> Instead of resolving this issue manually by removing older test
>> results, I thought others would might have some better ideas for
>> resolving the immediate issue of no free disk space.
>>
>> I'm checking in with infrastructure to see if there are any free
>> disks that can be assigned to our guest to alleviate matters. In
>> the meantime, any recommendations to resolve this issue in the
>> short-term (today/tomorrow) so we can get jobs processing again?
>
> Can we archive the large logs for further inspection and move it to
> another partition? That should help us going on quickly. Tomorrow I
> intend to write a cron script that will find large log files, gzip
> them and symlink the original files to them.
Great minds think alike :)
I don't think that we have another partition to move it to on that
machine since it's a VM, though. Is there another server we could move
them to?
Another qnd option would be to move large logs to another publicly
available machine and replace the logs with html saying something
like:
"This log has been moved to
http://morediskspace/autoqa/jobnum/log"
I think if there is no more space on the original machine, this idea
is sound, very much short-term of course.
Thus the Kamil's script would be used to archive the files in different
partition on the VM just after we have more space available or it would
be part of the immediate solution (moving them to different machine),
just wondering :-)
I assume that the timeline for getting more disk space is still on
the
order of next week, though?