I've been doing backups with listed-incremental for many years. When
I try to upgrade from a tar with dump format 0 (version 1.15.1) to
format 2 (version 1.17, Fedora 8 packaging) it tries to do a complete
backup.
Simple example to illustrate:
22:55 mimmi> mkdir tmp
22:55 mimmi> touch tmp/apa
22
I'm using tar to create backups. According to the documentation,
listed-incremental mode should consider all NFS file systems as equal,
but that doesn't work for me. If an NFS filesystem gets a new device
number than last time, tar wants to rebackup the whole tree.
I took a look in the code, and
The documentation claims it should be possible to extract files from a
volume of a multi-volume archive without first reading all the
previous volumes:
You can read each individual volume of a multi-volume archive as if
it were an archive by itself. For example, to list the contents of
Sergey Poznyakoff:
> Note, however, that
> in order to extract a split member (i.e. the one contained in several
> volumes), you will always have to start from the volume that contains
> its beginning,
Oh, yes, I understand that. In my test case I only expected "c" to be
extracted, not "b".
I'll
I've tried your patch now, and it seems to work just fine. Thanks
again! :-)
The issue: a large backup was made on the 3rd of June. After that, two
more backups have been made which should include only changes since
the large one. But the smaller backups includes a few file trees that
have not been changed. The output says they have been changed.
In some detail:
I'm doing
