> touch 1
> tar cz 1 > file.tgz
> ls -al file.tgz
-rw-rw-r-- 1 martinea martinea 10240 Nov 23 07:32 file.tgz
> dd if=file.tgz count=1 bs=108 > a.tgz
> gunzip -t -v a.tgz
a.tgz: OK
Why the file is 10k in size? Why tar pad with zeros a compressed output?
The first 108 bytes are the compressed ta
Hi,
Incremental of nfs directory do full every times because device number
change.
Attached patch fix a bug because DIR_IS_NFS return 2 if it is NFS.
The biggest problem is the NFS_FILE_STAT which fail to detect if it is NFS.
I read that the device should not be used for other filesystem, eg.
Sergey,
First test is successful, I will do more test and let you know if i
still have problem.
Thanks
Jean-Louis
Sergey Poznyakoff wrote:
Hi Jean-Louis,
My apologies for being slow with replying.
Attached patch fix a bug because DIR_IS_NFS return 2 if it is NFS.
Thank you, I ha
A user get this error when doing incremental backup:
/bin/tar: ./opt/novell/nss/mnt/.pools/DATA: Cannot savedir: Not a
directory
He is using '--ignore-failed-read', why tar exit with code 2?
This directory is strange, a size of 0 and 1 link:
$ stat /opt/novell/nss/mnt/.pools/DATA
File: `/op
Hi Sergey,
I don't know what GNU tar version he is using.
The problem is the exit code of 2, amanda think the backup is a failure
in this case. Maybe calling savedir_diag instead of savedir_error should
ifx it.
It's probably an opendir failure, ls report the same "Not a directory"
error.
I wil
I sent a patch a few days for the same problem. But my user user was not
able to test it.
The patch call savedir only if needed.
If you can give it a try.
Jean-Louis
Solar Designer wrote:
Sergey,
On Tue, Aug 25, 2009 at 10:37:13AM +0300, Sergey Poznyakoff wrote:
Solar Designer ha escri
Sergey Poznyakoff wrote:
Hi Bdale,
When creating incremental backups using snapshot filesystems, tar fails
to include files in a level 1 backup (presumably any level > 0) if they
were modified in the original filesystem between the time the snapshot
was created and the time the level 0 backu
:
Jean-Louis Martineau ha escrit:
It is a major bug for all users that use filesystem snapshot to make backup.
I did not argue whether this could be considered a bug or not. I only
described the way tar works.
What is the reference timestamp stored in the snapshot file? Is it
- the
Hi,
I have a tar file with many files, I want to extract everything except
the file 't*s', I used to do:
$ tar xf file.tar --wildcards --exclude 't\*s'
It worked for all tar version up to 1.22
With tar-1.23, it extract everything except the file 't\*s.
I can extract that file with:
$ tar xf fi
Hi Paul,
This attached test case succeed with tar-1.23 but fail with tar-1.25
Jean-Louis
Paul Eggert wrote:
On 11/21/2010 10:40 PM, gene heskett wrote:
Aren't the modes amanda uses for incremental ever tested?
Apparently not. Could you contribute some test cases along those lines?
Hi,
--files-from do not recursively extract since tar-1.27
In tar-1.26, i could put a directory name in a 'list' file and run ' tar
-xvf archive.tar --files-from list' to extract the directory recursively.
In tar-1.27 and tar-1.28 it extract only the directory, nothing inside it.
How to repro
Hi Sergey,
The patch fix the first issue I reported, but not the second.
mkdir dir1
touch dir1/file1.1 dir1/file1.2
tar cf archive.tar dir1
echo dir1/ > list ## NOTE the /
rm -rf dir1
tar xvf archive.tar --files-from list
$ ../tar-1.26/src/tar xvf archive.tar --files-from list
dir1/
dir1/file-1
See the
+# GNU General Public License for more details.
+
+# You should have received a copy of the GNU General Public License
+# along with this program. If not, see <http://www.gnu.org/licenses/>.
+
+# Tar 1.27 and 1.28 did not extract files under directory memberes listed
+# in the file
Remi,
--keep-old-files and --no-overwrite-dr can't be used at the same time.
tar should print a warning when mutually exclusive options are used
instead of ignoring some of them,
Jean-Louis
On 06/08/15 05:42 PM, Remi Broemeling wrote:
Re-send, as my "send" hotkey was trigger-happy on the las
example:
---
mkdir dirA
echo 'a' > dirA/a
echo 'a' > dirA/b
tar -vcf test.0.tar -incremental --newer '2150-02-08 21:50:00' dirA
tar: dirA: Directory is new
dirA/
dirA/a
dirA/b
---
It should not archive dirA/a and dirA/b
In src/create.c:
This check
Hi,
I have 2 problems extracting incremental archive.
I have no problem restoring my level 0 because I start from an empty dir.
But if the level 0 contain a symlink, the extraction of the level 1 will
happily follow that symlink.
I tried the -U option, it remove the symlink, but I get a lot of
Paul Eggert wrote:
Matthias Koenig <[EMAIL PROTECTED]> writes:
Is this behaviour correct? The documentation isn't that clear about
overwriting of links to a target directory.
I think it's correct, since "--no-overwrite-dir" is supposed
to keep the metadata of existing directories, and
17 matches
Mail list logo
