Article View: comp.bugs.sys5
Article #863cpio handling of read errors
From: Chris Bertin
Date: Tue, 27 Sep 1988 14:52
Date: Tue, 27 Sep 1988 14:52
15 lines
920 bytes
920 bytes
There is a problem in the way 'cpio' handles read errors. If it encounters such an error, it just continues, which causes the end of the archive to be out of sync. This can happen if a disk has a bad block, or, much more commonly if you are cpio'ing across NFS (if you have NFS on your SYSV) and if you hit non-readable files. The way to handle this problem is probably to replace the 'continue' by a 'memset(..., 0, ...);', or, simply to give up. Chris -- Chris Bertin | CETIA | 150, Av Marcelin Berthelot, Z.I. Toulon-Est +33(94)212005 | 83088 Toulon Cedex, France Ext: 239 | inria!cetia
Technical Details
Message-ID:
<132@cetia.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!inria!gouldfr!cetia!chrisShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!mcvax!inria!gouldfr!cetia!chris From: chris@cetia.UUCP (Chris Bertin) Newsgroups: comp.bugs.sys5 Subject: cpio handling of read errors Keywords: read error, out of phase Message-ID: <132@cetia.UUCP> Date: 27 Sep 88 14:52:26 GMT Organization: Cetia, Toulon, France Lines: 15