Hello Managers:
Thanks for the fast responses from:
V.S. Glukhov" <glukhov_at_sequence.Stanford.EDU(who also helped correct
the original posting).
alan_at_nabeth.cxo.dec.com (Alan Rollow)
Tom Ozanich <txo_at_esca.com>
C.Ruhnke <i769646_at_smrs013a.mdc.com>
The original question is at the end. The general consensus is that
NSR 4.2A has bugs in it that can be fixed by upgrading. That seems
the way to go except that I cannot obtain the money to do so at this time.
I have talked to DEC, and they looked for patches for 4.2A. However,
I was told that no patches were available.
Alan suggested it might be caused by an I/O error while reading the file.
I used uerf -o full, and the last entry was for April 1, so that was not the
problem(possibly).
Looking into the manuals I found something about changing the status of
the "client retries"(under customize, groups) from 0 to 1 or 2. However,
since we are using single server mode, this entry must remain at 0.
As it stands, I guess I will hope that the disk does not decide to crash for now.
I have had to recover some files and directories, and that has not been
a problem so far.
Thanks,
Ron Bowman
Techno-Sciences, Inc.
rdbowma_at_tsi.clemson.edu
864-646-4028
Alpha EB 21164, 333MHz, 1 CPU
DU 4.0B (564) Patch #6 installed
Original question(revised):
Hello Managers-
Occasionally during a full back up we get the
following error:
--- Unsuccessful Save Sets ---
* tsi:index nsrindexasm: save failed on /usr/var/nsr/index/tsi/db
* tsi:index save: external ASM `nsrindexasm' exited with code 1
* tsi:index save: /usr/var/nsr/index/tsi/db was not successfully saved
* tsi:index save: SYSTEM error, I/O error
* tsi:index save: save of /usr/var/nsr/index/tsi to tsi.clemson.edu failed
Can anyone provide a solution or information about what the
cause of this problem is. It does not occur everytime a full
back up is made; however it has only occurred during full backups.
We are running NSR 4.2A in single server mode.
Thanks in Advance.
Received on Tue Apr 28 1998 - 19:05:32 NZST