Unfortunately btrfs failed the test. A few days ago syslog-ng startet to do weired things. At first it only stopped logging for a few seconds and then even reloaded every 30-60 seconds with no errors logged (even with verbose & debug). After switching back to a other filesystem / a clean new btrfs partition everything worked again - 2bad. Now I'm experimenting again with the newly stable ZFS for linux :P ________________________________________ Von: syslog-ng-bounces@lists.balabit.hu [syslog-ng-bounces@lists.balabit.hu]" im Auftrag von "Gergely Nagy [algernon@balabit.hu] Gesendet: Montag, 18. Februar 2013 16:14 An: Syslog-ng users' and developers' mailing list Betreff: Re: [syslog-ng] how to archive logs efficiently Daniel Neubacher <daniel.neubacher@xing.com> writes:
Thanks for your detailed responses. The external compression was my last resolution but now I've maybe found my final solution. I've installed Kernel 3.2 & Btrfs with zlib compression. The fs isn't marked as stable yet but I've heard some positive responses from fellow admins. Right now I've got a real time compression rate of 84% without any cpu problems. I hope my long term test is running fine but right now I'm pretty happy.
That's an interesting solution aswell, thanks for sharing it! I was already considering BTRFS for the next experimental servers I'll be bringing up, this adds one more point in its favour. :) -- |8] ______________________________________________________________________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product=syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq