hoi :)
On Fri, Jan 13, 2006 at 12:08:52PM +1300, Robert Krawczyk wrote:
> Apparently fauback uses the inode number as the primary criterion for
> finding out, if a file has changed. This is bad if you change the
> filesystem, resize it, etc. Maybe using the same algorithm as rsync
> would help?
y
Package: faubackup
Version: 0.5.8
My backup is stored on logical volumes. After I resized the logical
volume, fauback did not do an incremental backup, but copied everything.
The filesystem used is ext3.
I tracked down the problem to changed inode numbers (of course), e.g.:
Before resize:
50012
2 matches
Mail list logo
