DEC engineering has created a new version of vrestore which correctly
handles directories with ACL entries. I have been testing the new version
over the past few days and am no longer receiving errors or having any
trouble recovering files from tape backup. To get a copy of the new
vrestore using anonymous ftp, connect to atlanta.service.digital.com then
cd private/outgoing
type binary
get washuniv_vres.tar
bye
Replace /sbin/vrestore with the new one (keep a copy of the old one).
Many thanks to Dr. Tom Blinn for his initial help, Meyyazhagan S.
Gangadaran at DEC for researching the problem and handling my requests for
help, and to DEC engineering for taking the time to fix vrestore.
__/__/__/__/__/__/__/__/__/__/___\__\__\__\__\__\__\__\__\__\__
__/__/ \__\__
/\ __/__/ Donald Bovee (206)543-0908 \__\__ /\
\/ __/__/ Unix System Administrator \__\__ \/
\__/ __/__/ Dept of Applied Mathematics \__\__ \__/
__/__/ bovee_at_amath.washington.edu \__\__
On Mon, 28 Apr 1997, Donald Bovee wrote:
> Hello Managers,
>
> I have been getting an increasing number of errors when running vrestore
> of the form below:
> ---------------------------------------------
> RECORD HEADER (unknown/unexpected)
> record type : 14
> data offset : 0
> record size : 312
> flags : <none>
> ----------------------------------------------
This problem does not cause data corruption per se. Piping vdump to
vrestore generates numerous errors, but the files come through OK. The
situation with a tape backup is not so good. Perhaps depending on the
number of errors generated on the way to a particular file, individual
files may or may not be recoverable. My own experience, with over 200
directories having ACL entries set, is that interactive vrestore fails
more than 50% of the time.
Received on Mon Jun 09 1997 - 23:53:30 NZST