Your message dated Mon, 29 Oct 2007 11:27:57 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#448500: cp documentation does not state behaviour on I/O
errors
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: coreutils
Version: 5.97-5.3
Severity: normal
I'm trying to save what I can from a rather large disk which is failing
(ocasional read errors). I already wasted some time trying two tar
processes connected with a pipe - tar has an option to ignore I/O
errors, but unfortunately it causes the other process to desync and it
all ends up copying data to /dev/null.
I was hoping to get an idea what cp would do on read errors, before I
give it a try, but neither the man page nor the info manual say anything
about I/O errors.
-- 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 coreutils depends on:
ii libacl1 2.2.41-1 Access control list shared library
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii libselinux1 1.32-3 SELinux shared libraries
coreutils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Oct 29, 2007 at 03:02:47PM +0000, Marcin Owsiany wrote:
I was hoping to get an idea what cp would do on read errors, before I
give it a try, but neither the man page nor the info manual say anything
about I/O errors.
It should fail. In general, if a utility doesn't specify a particular
handling for I/O errors, you should assume that it will fail with a an
I/O error-related message.
dd has an option to skip errors, you can use it like
dd if=something of=somethingelse conv=noerror,sync
It will be horribly slow, and won't work in certain failure modes (e.g.,
the kernel might kill a device entirely, so further reads are
impossible).
Mike Stone
--- End Message ---
