Hi Adam,
On Thu, Mar 24, 2011 at 12:02:26PM +0000, Adam Spiers wrote:
By metadata presumably you mean inode updates? So I
can search for
churn via find -ctime? In that case, could I expect remounting
partitions with the noatime or relatime options to drastically reduce
the size of incrementals?
Not sure. It's rsync's:
--link-dest=DIR hardlink to files in DIR when unchanged
behaviour, so whatever rsync considers "changed".
atime is not going to matter (otherwise everything would be backed
up, always), but mtime I expect will, as will owner and group.
Ahah. I think I may have located the culprits: huge
log files.
Likely.
# ls -lah
hourly.*/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
-rw-r--r-- 1 root root 858M Mar 24 11:32
hourly.0/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
-rw-r--r-- 1 root root 858M Mar 24 07:32
hourly.1/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
-rw-r--r-- 1 root root 858M Mar 24 03:32
hourly.2/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
-rw-r--r-- 1 root root 858M Mar 23 23:31
hourly.3/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
# md5sum
hourly.*/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
97aa1c123852249a4de71093ce464344
hourly.0/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
4872edc880f7b857849ff494fc92cb5a
hourly.1/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
f55356dd1fd454034ed2c909ecdf4cce
hourly.2/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
d70420c630746991df150a99e9de09c6
hourly.3/212.13.194.176/home/adam/web/adamspiers.org/logs/access.log
There 4x858MiB of changed files there alone.
If I start rotating these regularly, then I could
expect the
incrementals to significantly shrink, right?
Yes, because far fewer of the files would change.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
"I remember the first time I made love. Perhaps it was not love exactly but I
made it and it still works." -- The League Against Tedium