I had one big filesystem mounted on /storage which was backed up by a
DLE using comp-user-tar dumptype. Yesterday I split out one
subdirectory, /storage/lists, into separate partition and added
another DLE for /storage/lists, also using comp-user-tar dumptype.
Tonight's amdump run seems to have backed up the contents of
/storage/lists twice, once as /storage/lists DLE and once as part of
/storage DLE.
I thought that '--one-file-system' flag passed by Amanda to gtar is
supposed to prevent that, but in my case it doesn't seem to have an
effect.
It's easy enough to just add an appropriate "exclude" statement to
/storage DLE, but I'm curious whether someone else has seen such
thing, and what might be the cause. It can't be very common, otherwise
I would remember someone else reporting this.
Relevant software versions:
Client: amanda-client-2.6.1p2, gtar-1.22, FreeBSD 7.4
Server: amanda-server-3.2.2, FreeBSD 8.2
Contents of relevant runtar.debug file for DLE /storage:
1337197794.412932: runtar: pid 34403 ruid 1010 euid 0 version 2.6.1p2:
start at Wed May 16 22:49:54 2012
1337197794.413066: runtar: version 2.6.1p2
1337197794.437903: runtar: /usr/local/bin/gtar version: tar (GNU tar) 1.22
1337197794.438480: runtar: config: BACKUP
1337197794.439032: runtar: pid 34403 ruid 0 euid 0 version 2.6.1p2:
rename at Wed May 16 22:49:54 2012
1337197794.439334: runtar: running: /usr/local/bin/gtar --create
--file - --directory /storage --one-file-system --listed-incremental
/var/amanda/client/gnutar-lists/kuller.raad.tartu.ee_storage_1.new
--sparse --ignore-failed-read --totals .
1337197794.439383: runtar: pid 34403 finish time Wed May 16 22:49:54 2012
--
Toomas Aas
