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.
# of jobs scheduled per day ...
20110502 - 38 # small since this is when we fixed the
tmpwatch arg
20110503 - 536
20110504 - 223
20110505 - 0 # out of disk space
Size of results directory (18G available on system)
14G /usr/share/autotest/results
Jobs with *obscenely* large logs ...
1.2G /usr/share/autotest/results/91523-autotest
3.0G /usr/share/autotest/results/91524-autotest
1.9G /usr/share/autotest/results/91550-autotest
1.5G /usr/share/autotest/results/91604-autotest
2.0G /usr/share/autotest/results/91605-autotest
967M /usr/share/autotest/results/91549-autotest
252M /usr/share/autotest/results/91705-autotest
933M /usr/share/autotest/results/91635-autotest
685M /usr/share/autotest/results/91634-autotest
536M /usr/share/autotest/results/92318-autotest
200M /usr/share/autotest/results/92317-autotest
Thanks,
James
_______________________________________________
autoqa-devel mailing list
autoqa-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/autoqa-devel