Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 156799 - Bogus errors when --to-stdout is used
Summary: Bogus errors when --to-stdout is used
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: tar
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Peter Vrabec
QA Contact: Ben Levenson
Whiteboard: RHEL4U3NAK
Depends On: 146225
Blocks: 187538
TreeView+ depends on / blocked
Reported: 2005-05-04 11:16 UTC by Peter Vrabec
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version: RHBA-2006-0336
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-05-03 21:45:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0336 normal SHIPPED_LIVE tar bug fix update 2006-05-03 04:00:00 UTC

Description Peter Vrabec 2005-05-04 11:16:58 UTC
+++ This bug was initially created as a clone of Bug #146225 +++

When I use tar -xvzf /dev/nosst0 --to-stdout >/dev/null 2>&1, I get a
bunch of errors that look like this:

tar: /d/home/jik/.spam-db: Warning: Cannot truncate: Invalid argument

Why's it trying to truncate something on my disk when I'm running in
--to-stdout mode?

I believe that what all the files which show this error have in common
is that they're all sparse.  Note that the archive I'm trying to
extract was created with --sparse.

When I specify on the command line above a single file I want to
extract, I get a bunch of messages like this while tar is reading the

tar: Skipping to next header

I suspect that these messages, too, are related to sparse files in the

Comment 9 Red Hat Bugzilla 2006-05-03 21:45:04 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.