From: John Rouillard <rouilj-backuppc@re...> - 2009-04-01 17:39:07
I am backing up a system using rsync and it has a (source) file that
is 40GB in size. Dring th ebackup it grows to 200GB in size.
A partial ls listing of the source file is:
40532271104 Mar 31 22:47 /data/bak/fedora-ds/current/userRoot/id2entry.db4
When I run an incremental backup of the system and look at the copy:
ls -l shows:
-rw-r----- 1 backup dev 61832351744 Apr 1 15:24 ffedora-ds/fcurrent/fuserRoot/fid2entry.db4
During the backup, this file keeps growing to fill the disk
/dev/md2 688G 653G 224M 100% /backup-pc
and it appears to hang forever (although it may time out after the
client timeout), but it does not seem to fail with a write failure or
As soon as I kill the backup (via the web interface), the disk space is
freed and I get back to:
/dev/md2 688G 445G 209G 69% /backup-pc
so a 40GB file is taking up 200+GB.
I am currently using BackupPC_zcat to try to figure out if it is just
adding junk onto the end of the fully transferred file or if some
really wierd is going on when it tries to compress the file and it is
expanding it somehow.
If I run:
sudo sh -c 'gzip -6 < current/userRoot/id2entry.db4 | wc -c'
on the source file I get a size of
so about 1/4 size reduction not a 5x increase.
I am using BackupPC-3.1.0 with self built perl-File-RsyncP-0.68-1
(using cpan2rpm) on a 32 bit i686 system (athelon processor) running
kernel 2.6.18-53.1.19.el5PAE #1 with centos 5.1.
Also I am using:
with perl 5.8.8.
Anybody have an idea how to get more info on this?
603-643-9300 x 111
Get latest updates about Open Source Projects, Conferences and News.