On Mon, 2009-09-28 at 14:18 +, Andrew Gideon wrote:
> It assumes that --inplace
> actually does what it sounds like it does: it modifies only the disk
> pages of a file that have changed, as opposed to changing the entire file
> or creating a new file or some other thing which causes the fil
On 10/5/2009, Ed W (li...@wildgooses.com) wrote:
> Ideally I would like to see a kind of half and half maildir/mbox
> format emerge for email (perhaps dbox from dovecot will get there?)
Guess I should have read your entire email before replying... ;)
Its slated for 2.0 now, so will be a bit longe
On 10/5/2009, Ed W (li...@wildgooses.com) wrote:
> If you resist using a fileformat which has some kind of implicit
> "chunking" capability (eg maildir isn't perfect, but kind of goes in
> the opposite direction and chunks your mail into lots of smaller
> files - perhaps too many in the opinion of
Andrew Gideon wrote:
I currently do incremental backups using --link-dest. Unchanged files
are hard links to the previous snapshot; changed files are new copies.
Where this "fails" is for large files that have received small changes.
The directory containing my main IMAP account, for example
On Mon 28 Sep 2009, Andrew Gideon wrote:
>
> The --update option is also useful in this regard? What would happen if
> --inplace were used but --update were not?
--update only influences what files are considered for transfer, not how
that transfer is performed; hence it is completely irrelevan
On Sun, 27 Sep 2009 17:14:42 +, Andrew Gideon wrote:
> I was thinking that an alternative to links, which do nothing to
> preserve space when small file changes have been made, would be using
> LVM snapshots. Instead of creating a new directory for a new backup,
> and specifying --link-dest t
On Sun, 27 Sep 2009 17:14:42 +, Andrew Gideon wrote:
> Where this "fails" is for large files that have received small changes.
> The directory containing my main IMAP account, for example, typically
> generates between 1 and 2 G of daily backup data as I file messages in
> my inbox. Yesterda
I currently do incremental backups using --link-dest. Unchanged files
are hard links to the previous snapshot; changed files are new copies.
Where this "fails" is for large files that have received small changes.
The directory containing my main IMAP account, for example, typically
generates
