Description of problem: we have taken daily backup of our system with the below command tar -zcvf /backup/filename.tar.gz --exclude=somefiles filename the backup was completed around 22:45 with filesize of 19GB, however when we decided to copy the backup to disc, we noticed that the size is now 0 bytes and has a timestamp of 00:48 when no human changes have been done to the file. this has happened a couple of times and we want to understand what exactly happened. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -rw-r--r-- 1 root root 0 May 12 00:48 2012MAY11BCOB.tar.gz
Thanks for filing the bugzilla. Tar version in RHEL-5 is 1.15.1 - could you still specify the exact version of tar and gzip (rpm -q tar gzip)? Are you able to reproduce the issue somehow? What do you mean by "backup was completed around 22:45 with filesize of 19GB" ? So tar process ended and tarball size was 19GB ? What do you use for backup to disc ? If so, then this is probably not an issue of tar. Is there some special filesystem on the /backup/ location ? Is it possible that someone else accidently run the tar process again? As you are using tar "c" option, new archive is always created, I would recommend to use some tar backup (--backup option) control method, with deleting backups once archived. Still, if you want to increase the chances to have this analyzed (and fixed, if the behaviour is a bug) in RHEL-5, please report it to RHEL support ( https://access.redhat.com/support/ ) - Bugzilla is bug tracking, not support tool.
As the NEEDINFO is almost 10 months old, I'm closing this bugreport with "INSUFFICIENT DATA". Reporter: Really, feel free to reopen this bugreport once you are able to give us more info for this issue. Thanks for your report, Pavel