Hi,
tar 1.29-1 on Arch Linux. `info tar exclude' says
* The main operating mode of 'tar' does not act on a file name
explicitly listed on the command line, if one of its file name
components is excluded. In the example above, if you create an
archive and exclude files that end
Hi Sam,
> I used the following command *tar --delete --file=ldu900x.tar modem.bin*
> but am getting the following error message
> *tar: modem.bin: Not found in archive*
tar wants the whole path of the file as it is listed in the output of
-tf. Do `tar -tf ldu900x.tar', find modem.bin, e.g. with
Hi Steffen,
> So it collects a list of files in a textfile, and then either
> $tarxcmd = "tar -c -f - | $COMPRESSOR > $ar";
> or
> $tarxcmd = "tar -r -f $ar >/dev/null";
With the second of these, $ar isn't a compressed file name, like
foo.tar.gz? Which was used for the problem tar file?
> a
Hi Steffen,
> > > $tarxcmd = "tar -c -f - | $COMPRESSOR > $ar";
...
> > > unless (open XARGS, "| xargs -0 $tarxcmd 2>>$MFFN") {
> >
> > So xargs may run tar more than once, and if $#{$listref} has been
> > growing then perhaps it's tipped over from one invocation to two
> > recently?
>
> I
Hi Jörg,
> If you like to create working incremental backups that are able to
> handle file renames, you need to backup any filesystem with exactly
> one command run, so xargs is a really bad idea.
Agreed. I was just trying to help Steffen out of the hole he'd already
dug. :-) Instead of xargs
Hi Rob,
> This report is for tar-1.29, compiled and installed on Mac El Capitan.
> When the environment variable "LANG" is not set, tar cannot handle a
> compressed archive--the error is "broken pipe". For example:
>
> m3rgma0371carn - T tar tvzf archive.tgz
> gnutar: Child died with sign
Hi Rob,
> > > This report is for tar-1.29, compiled and installed on Mac El Capitan.
...
> m3rgma0371carn - T $ unset LANG
> m3rgma0371carn - T $ gnutar -tvf archive.tgz
> gnutar: Child died with signal 11
> gnutar: Error is not recoverable: exiting now
> m3rgma0371carn - T $ l
Hi Rob,
> Does your Mac have libiconv, gettext, and libintl installed and used
> by gtar?
iconv yes, the other two no AFAICS.
$ DYLD_PRINT_LIBRARIES= /usr/local/Cellar/gnu-tar/1.29/bin/gtar
dyld: loaded: /usr/local/Cellar/gnu-tar/1.29/bin/gtar
dyld: loaded: /usr/lib/libiconv.2.dylib
Hi Rob,
> Incidentally, running "gdb" on the latest Mac OS is a pain--Apple
> thought for some reason that it was a security risk. Running "lldb,"
> the default debugger, told me nothing.--Rob
I haven't tried this, but something like `lldb /path/to/tar' to get
going, then `run tvzf archive.tgz'
Hi Jack,
> > gnutar: Child died with signal 11
...
> stop reason = signal SIGPIPE
SIGPIPE is 13. We want 11, SIGSEGV. Perhaps a "c" or two for continue
will have the debugger carry on until the SEGV bites.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Dawid,
> To my surprise it worked the first time, but on subsequent attempts it
> just hangs. After some investigation, it turned out that if one uses
> `--xattrs --skip-old-files` together, and `tar x ...` encouter
> existing file, it just hangs.
...
> I've tested with tar 1.27.1 on Ubuntu 14.
> Could do with a test case that fails.
Sorry, ignore me. I thought I'd read to the end of this list's emails
before reply.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Chris,
> Has anyone seen this email?
Yes, according to
http://lists.gnu.org/archive/html/bug-tar/2016-11/threads.html mentioned
in the headers of emails from the list.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Paul,
> > I think it would be a good idea to add an option to tell tar whether
> > to use POSIX_FADV_NOREUSE, POSIX_FADV_DONTNEED, or neither, since
> > there may be cases where any of the three possibilities is best.
>
> Might make sense, yes.
I often want to run tar, sha1sum, grep, etc., on
Hi Marius,
> the new command line options -y and --brotli are added to tar.
I suggest not adding -y. Single-letter options are in short supply and
over the next twenty years another twenty compressors worthy of addition
will appear.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Marius,
> @@ -1285,7 +1289,8 @@
> .BR rmt (8),
> .BR symlink (7),
> .BR tar (5),
> -.BR xz (1).
> +.BR xz (1),
> +.BR brotli (1).
> .PP
> Complete \fBtar\fR manual: run
> .B info tar
SEE ALSO in man pages is normally in sorted by section number, then page
name. See man-pages(7). The ab
Hi,
> Its customary file extension is ".zst", while some tools use ".tzst"
> as a shorthand for ".tar.zst".
This shortening should die, just like DOS 8.3 filenames.
If it's .tar.foo then eyeballs and scripts stand a chance of realising
it's a tar file that's had another transformation applied, a
Hi Adam,
> Shawn wrote:
> > + ct_xz,
> > + ct_zstd
> >
> > there should be a comma after ct_zstd. compilers can accept this
> > now.
>
> Yeah, that's much nicer for diffs. I wanted to follow the old code,
> but you're right here.
Only if you assume GNU tar doesn't intend to be compiled by old
Hi Peng,
> GZIP=-n tar czf name.tar.gz name
The -I option might help; give it gzip and its -n option.
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Peng,
Tristan's right, -I, ninth letter of the alphabet, not -l.
I find this works as expected.
tar cvf foo.tar.gz -I 'gzip -n' foo
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Jim,
> filename='C:\nppdf32Log\debuglog.txt'
> ...
> tar cvf test.tar "$filename"
This is behaving as documented. See `--no-unquote'.
info tar | sed -n '/6.2 Selecting Archive Members/,/^File/p'
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi,
I wonder if http://austingroupbugs.net/main_page.php would be a better
place to discuss this because it could involve more people that have
worked on POSIX's wording that just Jörg, and thus may either have a
different opinion, or be able to phrase it in a more persuasive manner.
It doesn't se
Hi,
Paul wrote:
> Nothing in the POSIX standard clearly disallows the behavior in
> question, and the arguments you're making about what POSIX requires
> are based on a long chain of indirect inferences that are
> unconvincing.
I'll make the point again. Raise the issue with the POSIX authors.
B
Hi Mark,
> Andreas Dilger wrote:
> > We considered it a bug in ext4 and Lustre on the basis that it broke
> > existing tools (tar, and AFAIR cp) that were working fine when
> > delayed allocation and inline data features were not enabled. Since
> > we were in a position to fix the filesystems fas
Hi Jörg,
> Well, the name of the mailing list is "bug-tar" and not "bug-gtar", so
> people would assume that it is a general tar list and not just a gtar
> specific list.
But you omitted the address of the mailing list is bug-tar@gnu.org and
thus most would expect it to be centred on GNU's tar an
Hi Brian,
> I have trouble getting the --directory=dir to work when dir include
> white-space(s)
Using tar 1.30 here,
$ mkdir 'foo bar'
$ >'foo bar'/xyzzy
$ tar --directory='foo bar' -cvf brian.tar xyzzy
xyzzy
$ find | sort -V
.
./brian.tar
./foo bar
./foo bar
Hi Peter,
> What if I change the kernel and prevent ctime-changes if only st_nlink
> was changed?
Wouldn't it be easier, and have less unknown impact, to change the
program making the hard links to read-link-write ctime, preserving it?
--
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy
Hi Christian,
> $ stat -c %o data/blob
> 2097152
...
> **tar** does not explicitly use the block size of the file system
> where the files are located, but, for a reason I don't know (feel free
> to educate me), 10 KiB:
Historic, that being 20 blocks where a block is 512 B. See `Blocking
Factor'
Hi J.R.,
> I was trying to make some processes faster which use tar a bit on
> large archives. I was able to use the command line options
> --use-compress-program pbzip2 and that helped a lot.
I think analysis of where the remaining delay is would be needed before
investing effort in removing it
Hello David,
> Source code is
>if (mode == O_RDONLY
> || (new_fd = open ("/dev/full", mode) != fd))
>
> Maybe better code
>if (mode == O_RDONLY
> || ((new_fd = open ("/dev/full", mode)) != fd))
That's changing the written meaning. The original
Hi,
> ## -- ##
> ## testsuite.log was created. ##
> ## -- ##
>
> Please send `tests/testsuite.log' and all information you think might
> help:
Can that guidance to the user please be altered to say they should
compress the log file. Some of us pay
Hi,
After creating a tar file with a volume label, `tar -V everything -cf
foo.tar .', I can use --delete to remove items, e.g. to create a delta
against an earlier tar file, but how do I modify the volume label to
reflect the tar file no longer contains everything?
Doing `--delete -V something'
Hi Helmut,
> Ralph Corderoy <[EMAIL PROTECTED]> writes:
> > tar -V something -cf bar.tar dummyfile
> >
> > And is there any way to create a tar file with nothing but the
> > volume label, i.e. remove the need for dummyfile above?
>
> You could give
>
Hi,
I use tar with -g to create incremental backups from some home-grown
scripts. Recently, I've moved to Ubuntu.
$ tar --version
tar (GNU tar) 1.14
Copyright (C) 2004 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may
Hi again,
I wrote:
> $ tar xf small.tar home/ralph/pysloc
> tar: home/ralph/.mozilla/firefox/mc0oqdco.default/cert8.db: \
> invalid sparse archive member
> tar: Skipping to next header
> tar: Error exit delayed from previous errors
> $ echo $?
> 2
> $ test -f h
Hi,
I've tried the problem tar files with the latest 1.15.1.
> $ tar xRvf big.tar nonexistentfile
> block 1: level 0 backup of blake on 20050807-225123
> Reading `level 0 backup of blake on 20050807-225123'
> block 521103: tar: Skipping to next header
> block 1075261: ** Bloc
Hi,
An extra line of output, including some NUL bytes, appears in the output
of `tar -tvf'.
$ find d -ls
12919394 drwxr-xr-x 2 ralphralph4096 Aug 21 14:52 d
12919380 lrwxrwxrwx 1 ralphralph 3 Aug 21 14:51 d/bar
-> foo
$ for tar in /bin/tar ~
Hi,
I think 1.15.1's broken where 1.14 wasn't.
#! /bin/bash
set -ex
$TAR --version
rm -rf d d.orig db
mkdir d
>d/foo
ln -s 1.2.3.4:80 d/lock
find d -ls
$TAR -cvf d.l0.tar -g db d
rm d/lock
$TAR -cvf d.l1.tar -g db d
mv d d.orig
$TAR -xvf
Hi Sergey,
> Ralph Corderoy <[EMAIL PROTECTED]> wrote:
> > An extra line of output, including some NUL bytes, appears in the
> > output of `tar -tvf'.
>
> When used with -g or -G, -t option historically implies displaying
> some internal data from GNU tar h
Hi,
> 1.15.1 is trying to stat d/lock when it knows it's a symlink and
> there's no reason why the symlink's destination should exist. diff
> shows that d/lock has been left behind so my restore of my incremental
> backups is incorrect.
Can others reproduce this? I'd like to know that it's an
Hi Jim,
> The bug is that tar assumed open/creat would never return 2. The
> patch I supplied shows that this bug in GNU tar can be fixed with
> minimal effort.
Here's a simpler test case.
$ tar cf >(od -c) missingfile 2>&-
000 t a r : m i s s i n g f
Hi Joerg,
> > The bug is that tar assumed open/creat would never return 2. The
> > patch I supplied shows that this bug in GNU tar can be fixed with
> > minimal effort.
>
> I see nothing in your patch that could change the behavior.
http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/gnulib/gnu
Hi David,
> During incremental restore, before removing entities that have gone
> away, tar performs a 'stat' call. However, this stat call is
> dereferencing. If the previously existing entity is a symlink that
> does not resolve correctly, this causes tar to print a warning, and
> not remove
Hi Wouter,
> Unfortunately, the only non-destructive actions that I've found that
> will make tar read out the label and/or exit with a status code if the
> label isn't what I'm giving it, involve reading out the entire archive
> from tape. Since these tapes are rather large and I'm not sure I'll
> And in case you call "star -x -symlinks
> Hardlinks will be extraced as symlinks :-)
>
> ftp://ftp.berlios.de/pub/star/alpha/
Have I joined the `star ad-a-day' list by mistake? I thought this was
bug-tar.
Grumpily,
Ralph.
___
Bug-tar ma
Hi Sergey,
> Ah, forgotten to tell: on some systems sort produces spurious verbose
> diagnostics on stderr (we have some reports on the list)
Strange. Could that be because the user's locale means the bytes in the
files can't be interpreted? Locales do funny things to sort anyway so I
often fi
Hi Sergey,
> EST 01:30:26 PM Monday, December 20 2004 Prog: SORT User: ldm
> InputSize: 51
> Blocksize: 81920 MemoryArea: 94333952 RecsInMemory: 4087228
> processes: 0 IPC_buf_size: 0
> EST 01:30:26 PM Monday, December 20 2004 - DONE
>
> Host system was AIX. I don't know what kind of sort u
Hi Sergey,
> Ralph Corderoy <[EMAIL PROTECTED]> wrote:
> > The PATH shows the commercial product CoSort is installed. This can
> > replace AIX's normal sort. It's intended to be faster.
>
> Ah, thanks for the explanation.
>
> > I suspect it sp
Hi Martin,
> My pwd is anywhere but /backup and i do:
>
> # tar -C /backup -cf /backup/tmp.tar tmp-*.txt
>
> I then get the following error:
>
> tar: tmp-*.txt: Cannot stat: No such file or directory
> tar: Error exit delayed from previous errors
>
> But it works fine if i do any of the follo
Hi Helmut,
> Ralph Corderoy <[EMAIL PROTECTED]> writes:
> > Another alternative is
> >
> > cd /not/backup
> > tar -C /backup -cf /backup/tmp.tar $(cd /backup && ls tmp-*.txt)
> >
> > The shell first runs 'cd /backup && l
50 matches
Mail list logo
