2012/10/11 Jiri B <ji...@devio.us> > On Thu, Oct 11, 2012 at 09:29:50PM +0600, �л�� Шипи�ин wrote: > > > > there are http access logs for half an year. > > it's easier to rotate them on a single filesystem from many points of > view, > > we also share it via samba (very tricky to share many chunks). > > > > and it is bad idea to mount access logs R/O. difficult to rotate. > > Bad design totally! I remember struggling with backup/restore times > to satisfy SLA with huge filesystems having many files... And those > were logs. > > One of proposals we did was to split filesystem into smaller ones and > keep old logs on filesystems with read-only. Backup would be skipped, > and restore (in this it was TSM) would be much faster if image would > be used. > > j. > >
they are not "old" logs. generally, today's log is access.log, yesterday's log is "access.log.0" and so on. every rotate renames all the logs. older logs are removed. too many tricks with r/o filesystems. also, when dealing with rotating logs within single filesystem, it's cheap, data is not moved. and what if I want to move/rotate many-many-gigabytes logs in case of "better design" when there're many chunks ? I guess it is hard (and pretty useless) operation from filesystem point of view. ok, I can change configs of web-server to store logs in different location every day. you call it "better design" ??
