<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 4: Unneccessary md5sum calls</title><link>https://sourceforge.net/p/storebackup/bugs/4/</link><description>Recent changes to 4: Unneccessary md5sum calls</description><atom:link href="https://sourceforge.net/p/storebackup/bugs/4/feed.rss" rel="self"/><language>en</language><lastBuildDate>Tue, 18 Oct 2005 20:44:55 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/storebackup/bugs/4/feed.rss" rel="self" type="application/rss+xml"/><item><title>Unneccessary md5sum calls</title><link>https://sourceforge.net/p/storebackup/bugs/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;After the last backup run, I discovered that the md5sum&lt;br /&gt;
was calculated for almost all files. Some random&lt;br /&gt;
samples using ps proved that storebackup calculates the&lt;br /&gt;
md5sum of files whose mtime lies far behind the last&lt;br /&gt;
backup.&lt;/p&gt;
&lt;p&gt;Unfortunetaly, the debug mode didn't tell me why the&lt;br /&gt;
md5sum was calculated.&lt;/p&gt;
&lt;p&gt;This phenomena enhances the backup time significantly,&lt;br /&gt;
because almost all data is read and only a minor&lt;br /&gt;
percentage actually written.&lt;/p&gt;
&lt;p&gt;How is that to explain and how can I avoid it?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;br /&gt;
Nikolaus&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nikolaus Rath</dc:creator><pubDate>Tue, 18 Oct 2005 20:44:55 -0000</pubDate><guid>https://sourceforge.netd2dd9a3f68374205cbe71ad902c0ec072f23d817</guid></item></channel></rss>