Your message dated Mon, 4 Feb 2019 09:33:02 -0700 (MST)
with message-id <[email protected]>
and subject line closing with no action taken
has caused the Debian Bug report #448598,
regarding tar -C foo -c . | tar -C bar -x ends up with nothing on read errors
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
448598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448598
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tar
Version: 1.16-2
Severity: normal
I was hoping to save what I can from a disk which starts to show read
errors, by using the following command:
sudo tar --ignore-failed-read -C /media/data_big -cv -f - . | sudo tar -C /mnt
-x -f -
Unfortunately, after the reading tar encountered about three unreadable
files, the two processes got desynchronized somehow, and stracing the
receiver tar revealed that it did nothing but read lots of data from
standard input. As a result, nothing got to the destination disk after
the read errors were encountered.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-ovz-686
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Versions of packages tar depends on:
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
tar recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I've been unable to reproduce this in any way, and we're many versions of tar
downstream from when this bug was originally reported with no follow-up to my
request for additional information in 2008. So, I'm going to go ahead and
close this bug with no further action taken.
Bdale
--- End Message ---
