From jimo@eskimo.com Sat Jan 2 06:07:57 1999
From: jimo@eskimo.com
To: users@lists.opensuse.org
Subject: [SuSE Linux] tar compressed blocking
Date: Fri, 01 Jan 1999 22:07:57 -0800
Message-ID: <199901020607.WAA01394@eskimo.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6828185096648765497=="
--===============6828185096648765497==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Hi folks,
The tar info docs that came with my SuSE 5.3 say:
"If you are writing a compressed archive to tape with `--compress'
(`-Z') or `--gzip' (`-z') (
FIXME: pxref Input and Output
), `tar' will not block the archive correctly. This doesn't matter
if you are writing the archive to a normal file or through a pipe, but
if you are writing it to a tape drive, then this causes problems. Use
`--compress-blocks' or `--gzip-block' instead, to cause `tar' to
arrange to have blocking work correctly."
But when I tried my customary backup script, altered from `-b' to:
tar -czv\
-f /dev/st0\
--gzip-block 128\
...
I get:
"tar: unrecognized option `--gzip-block'"
What's going on? Are the SuSE 5.3 tar docs hosed? Is my tar
compiled without this option somehow? I guess I'll fall back to
the simple `-b 128' option I've been using, which the 5.3 tar
accepts cheerfully.
However, I did have to extract a few things from backup tapes after
installing 5.3, and every time I got error messages complaining about
"child exited with status 2" or something close to that. The
extracted files seem ok, but I don't like errors. Anybody know what
might be going on there?=20
Thanks in advance for any ideas.
jimo(a)eskimo.com
-
To get out of this list, please send email to majordomo(a)suse.com with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at <=
A HREF=3D"http://www.suse.com/Support/Doku/FAQ/http://www.suse.com/Suppo=
rt/Doku/FAQ/> and the
archiv at htt=
p://www.suse.com/Mailinglists/suse-linux-e/index.html>
--===============6828185096648765497==--