Package: tar Version: 1.15.91-1 Severity: important
Hello, since a few days, the backup software "amanda" fails on two of our Debian Unstable machines. A deeper analyse shows, that the GNU tar have problems with the (correct) way, amanda uses it. This results in a try to backup all mounted NFS shares of our company. Which will ultimately fail... To reproduce simply create a directory (/tmp/foo/) with a few files. Create a directory and mount something via NFS into it. (mount computer:/someshare /tmp/foo/bla) Now try this: /bin/tar -v --create --file /dev/null \ --one-file-system \ --numeric-owner --listed-incremental /tmp/someemptyfile --sparse --ignore-failed-read --totals /tmp/foo (this is the syntax, amanda uses when calculating the backup size. Unusual, but nothing wrong with ist) As you can see after a try, the tar DOES NOT ignore the NFS directory. Without the --listed-incremental is does ignore it correctly. Cheers, Felix -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages tar depends on: ii libc6 2.3.6-15 GNU C Library: Shared libraries tar recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
