[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [rdiff-backup-users] [PATCH] Sparse file support

From: Dominic Raferd
Subject: Re: [rdiff-backup-users] [PATCH] Sparse file support
Date: Tue, 04 Jan 2011 15:33:14 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv: Gecko/20101207 Thunderbird/3.1.7

On 03/01/2011 20:27, Eric Wheeler wrote:
On Sun, Jan 02, 2011 at 08:11:00PM -0800, Eric Wheeler wrote:
Feedback and comments are appreciated!
----Original Message-----
From: Matthew Miller>
How will this interact with existing backups?
rdiff-backup re-writes changed destination files, so if a source file
changes, rdiff-backup will write the whole file after calculating a
reverse-diff for the increment tree.

Existing backup trees will become sparse over time, as files change.

So I guess it is forward-compatible, but not backward-compatible? Existing repositories can be read fine with rdiff-backup patched for sparse file support, but repositories created with sparse file support cannot be read by unpatched rdiff-backup. That's okay, but it might make most of us feel that we would rather not use this patch unless we specifically need it, until it is part of mainstream rdiff-backup.

Sadly, development of rdiff-backup has gone silent for a while now. I think these patches are great (as were Daniel Miller's a while ago, which provided a --verify-full option) but no one from the development side seems to be updating the code at the moment. (I would love to be proved wrong.)

- Dominic

reply via email to

[Prev in Thread] Current Thread [Next in Thread]