cpio handling of read errors

Thread View: comp.bugs.sys5

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Chris Bertin Tue, 27 Sep 1988 14:52

#863

Author: Chris Bertin
Date: Tue, 27 Sep 1988 14:52

15 lines
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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads