Hi,

I don't know why, but since 2 days the tar commands segfaults. I'd like to debug why, but I don't know how to launch it, BM doesn't give enough info:

[root@awak:~]$ LANG=C backup-manager -v
When validating the configuration file /etc/backup-manager.conf, 1 warnings were found.
/mnt/backup/awak-boot.20101123.tar.gz: ok (0M, 262209eb997126fd42acc214edefc581)
/usr/share/backup-manager/backup-methods.sh: line 605: 29229 Segmentation fault      $command $file_to_create "$target" > $logfile 2>&1
Unable to create "/mnt/backup/awak.20101123.tar.gz", check /tmp/bm-tarball.log.KZlLhk
/mnt/backup/awak-home.20101123.tar.gz: ok (319M, fafbbe5d97116877f92221591619b1f4)
Unable to find the md5 hash of file "/mnt/backup/awak-home.20101101.master.tar.gz" in file "/mnt/backup/awak-20101101.md5".
Unable to find the md5 hash of file "/mnt/backup/awak-home.20101102.tar.gz" in file "/mnt/backup/awak-20101102.md5".
1 error occurred during the tarball generation.
[root@awak:~]$ cat /tmp/bm-tarball.log.KZlLhk
/bin/tar: Removing leading `//' from member names
[root@awak:~]$

Is there an easy way to debug it ?

Thanks,
        Xav

You could set BM_LOGGER_LEVEL to "debug", maybe that helps.  There is
also an undocumented "-d|--debug" option for backup-manager.  Otherwise,
insert a "set -x" at the beginning of /usr/bin/backup-manager and you
will be overwhelmed by its verbosity. ;-)

BTW, what are your tar and libc6 versions?

Cheers,
       Sven

libc6 is 2.11.2-7
tar was 1.23-3, and I tried 1.25-2 with not much success.

	Xav

I guess there's a reason why this option is not documented.  But I think
setting BM_LOGGER_LEVEL="debug" would log the actual commands being run
to syslog.

Yes, but this is not under backup-manager's control.  The command is
only printed because it segfaults, and apparently bash does not expand
variables in such a situation.

Cheers,
       Sven