bug-tar
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-tar] tar v1.26 - Folder has been renamed problem


From: address@hidden
Subject: Re: [Bug-tar] tar v1.26 - Folder has been renamed problem
Date: Wed, 29 Aug 2012 11:01:41 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0

Hi all,

So maybe I did jump the gun. I've done some more testing:

All using EXT4 filesystems
I used VirtualBox to install the different Ubuntu flavours

The tar command being used to back-up the home directory on each operating system is:

tar --exclude '*gvfs'  -cvpPWf  /mnt/backup/daily_backup.tar --listed-incremental=/var/log/backup/backup_snapshot   /home

Ubuntu 11.10
Kernel: 3.0.0-17-generic
Tar version: 1.25
Message on full backup of home directory:
Verify /home/
/home: Mode differs
/bin/tar: VERIFY FAILURE: 1 invalid header detected

Xubuntu 12.04
Kernel: 3.2.0-26-generic
Tar version: 1.26
Message on full backup of home directory:
Verify /home/
/bin/tar: /home/: Cannot savedir: Not a directory
/bin/tar: /home: Directory has been renamed

Kubuntu 11.04
Kernel: 2.6.38-8-generic
Tar version: 1.25
Message on full backup of home directory:
Verify /home/
/home: Mode differs
/bin/tar: VERIFY FAILURE: 1 invalid header detected

Lubuntu 10.10
Kernel: 2.6.35-30-generic
Tar version: 1.23
Message on full backup of home directory:
Verify /home/
/home: Contents differ

Ubuntu 10.04
Kernel: 2.6.32-35-generic
Tar version: 1.22
Verifies /home/ without any errors

Regards,

Tim

On 28/08/12 18:47, Paul Eggert wrote:
On 08/28/2012 08:11 AM, address@hidden wrote:
So I installed Ubuntu 10.04 on another machine and copied the tar v1.22 from that machine to my Xubuntu 12.04. It works with out any issues.

So its looks like an issue with tar 1.26 that is distributed with Ubuntu/Xubuntu 12.04 rather than a filesystem issue.
Sorry, but from the symptoms you described earlier, it very
much looks like a file system issue.  It's true that you
are observing the bug only when you use tar 1.26, but it's
not a bug in tar 1.26 itself -- it's a file system (or
kernel) bug that tar 1.26 happens to be running into but
that earlier versions of tar do not.

You will get the same bug with other programs, eventually,
if you keep using that file system.  So my suggestion is
to get that file system bug fixed.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]