Package: tar
Version: 1.16.1-1
Severity: important
Hi,
I use a backup system where in a cron job on one machine a tar file
is created and moved to another host that is backed up to tape. The
plain tarball is about 4-6 GB. Basically it concerns one home dirctory
(mine) and about 20 other users with nearly no data. This worked
sufficiently until my last update to recent testing (I update the
machine in question about once a month to testing). The backup
job did not finish any more. So I added some debugging code:
for user in $USERS ; do
echo "TRAP 5 ($user): `date`" >> $LOG || RET=$?
time tar -rf $TMPFILE -X $EXCLUDELIST \
--exclude /home/$user/.netscape/cache \
--exclude Cache \
$user/$file 2>&1 >> $LOG || RET=$?
done
Here is the output (sorry for the German locale which means
"removing leading »/« ..." - so this is nothing unnormal):
TRAP 5 (/home/claush): Mo 30. Jul 06:30:11 CEST 2007
tar: Entferne führende »/« von Elementnamen
8.94user 0.64system 59:57.42elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+630minor)pagefaults 0swaps
TRAP 5 (/home/eitzed): Mo 30. Jul 07:30:09 CEST 2007
tar: Entferne führende »/« von Elementnamen
0.39user 0.99system 49:42.35elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (6major+616minor)pagefaults 0swaps
TRAP 5 (/home/voigtm): Mo 30. Jul 08:19:52 CEST 2007
tar: Entferne führende »/« von Elementnamen
0.36user 0.92system 38:40.76elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (32major+762minor)pagefaults 0swaps
TRAP 5 (/home/strommengerb): Mo 30. Jul 11:49:07 CEST 2007
tar: Entferne führende »/« von Elementnamen
0.22user 1.27system 48:06.89elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5major+612minor)pagefaults 0swaps
TRAP 5 (/home/reinhardtb): Mo 30. Jul 12:37:15 CEST 2007
tar: Entferne führende »/« von Elementnamen
0.18user 1.05system 54:22.82elapsed 0%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (5major+618minor)pagefaults 0swaps
To estimate the size of the home directories here is a "du -s /home/*"
output:
5152 claush
1372 eitzed
44 reinhardtb
12 strommengerb
104 voigtm
So there is no reason at all to expect times between 30 and 60 minutes
to add this small amount of data. I suspect that size of the tar archive
that reached 5GB at this time might cause some trouble - but as I said
I did not observed this before the latest update of testing.
I know that these pieces of information are probably not sufficient
to track down the problem and I would happily providing more information
at request.
Kind regards and thanks for maintaining tar
Andreas.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.17-1-686 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages tar depends on:
ii libc6 2.6-2 GNU C Library: Shared libraries
tar recommends no packages.
-- no debconf information
