Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!wyse!bob
From: bob@wyse.wyse.com (Bob McGowen x4312 dept208)
Newsgroups: comp.os.minix
Subject: Re: problem with tar or Minix kernel
Message-ID: <3136@wyse.wyse.com>
Date: 21 Mar 91 21:23:11 GMT
References: <1991Mar21.183604.25451@cunixf.cc.columbia.edu>
Sender: news@wyse.wyse.com
Reply-To: bob@wyse.UUCP (Bob McGowen x4312 dept208)
Organization: Wyse Technology
Lines: 31

In article <1991Mar21.183604.25451@cunixf.cc.columbia.edu> cy5@cunixa.cc.columbia.edu writes:
>
---
>residing on my harddisk.  The tar command was humming along quite happily
>when I got a read error.   The block in which this error was a bad block
>on my hard drive.  It was allocated to the .BADxxxx files when I installed

I am assuming that the tar under minix works like UNIX, I am new to minix
and have no experience with its version of tar yet.  But I think this is
a valid assumption.  So, the question is, how did you invoke tar?

If you give it the name of a directory, it will recursively descend the
directory reading all files, including those beginning with a dot.  This
would include all the .BADxxxx names as well as .profile, .mailrc or
others.

If the above is true, the simplest way to get around the problem is to
make a subdirectory for bad block files under root (I do not know of the
top of my head where these are put by default) and run tar with a list
of directory names that do not include the one with the bad block files:

	tar cf /dev/XXX dirA dirB dirC ...

would be the basic command line format.

I hope this is useful.

Bob McGowan  (standard disclaimer, these are my own ...)
Product Support, Wyse Technology, San Jose, CA
..!uunet!wyse!bob
bob@wyse.com