Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Tue, 20 Mar 2007 13:56:40 -0400
We are seeing the following pair of messages occasionally: ANR9999D icvolhst.c(5267): ThreadId <47> Error Writing to output File. ANR4510E Server could not write sequential volume history information
Author: Mark Stapleton <mark.s AT EVOLVINGSOL DOT COM>
Date: Tue, 20 Mar 2007 13:10:37 -0500
ANR9999D icvolhst.c(5267): ThreadId <47> Error Writing to output File. ANR4510E Server could not write sequential volume history information to /var/tsm_automation/volumehistory. Does the directory e
Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Tue, 20 Mar 2007 14:43:44 -0400
--Mark Stapleton wrote: -- Yes. The file system has about 240 megabytes of free space. Our volume history file is a little under one megabyte. The server code runs as root, which can write to any fil
Is it not possible that the /var filesystem *sometimes* has too little space available? After all, didn't you say that this only fails roughly every one to two weeks? Perhaps the failures coincide wi
We are seeing the following pair of messages occasionally: ANR9999D icvolhst.c(5267): ThreadId <47> Error Writing to output File. ANR4510E Server could not write sequential volume history informatio
Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Tue, 20 Mar 2007 16:05:58 -0400
--Richard Sims wrote: -- The volume history file is around one megabyte. We create and fill one gigabyte scratch volumes in file device classes every night. I su'ed to root and executed a ulimit comm
Author: "Kauffman, Tom" <KauffmanT AT NIBCO DOT COM>
Date: Tue, 20 Mar 2007 15:16:04 -0400
What filesystem type? (reiser, ext3, etc.) Could you be running out of inodes at times? Tom Kauffman NIBCO, Inc We are seeing the following pair of messages occasionally: ANR9999D icvolhst.c(5267): T
Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Tue, 20 Mar 2007 16:26:56 -0400
--Bill Kelly wrote: -- That scenario is essentially impossible to disprove conclusively, but it doesn't look very promising as an explanation. The Linux system is dedicated to running the TSM server
Author: Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG>
Date: Tue, 20 Mar 2007 16:30:23 -0400
--Tom Kauffman wrote: -- It is an ext3 file system. We are using about 20,000 out of 300,960 inodes. I can't think of anything running on the system that would create several hundred thousand files i
Author: John Monahan <John.Monahan AT US.LOGICALIS DOT COM>
Date: Tue, 20 Mar 2007 15:37:25 -0500
You could also try more extensive testing using the "backup volhist" command on your own instead of waiting every one-two weeks for it to fail. ______________________________ John Monahan Consultant
Some time ago (years), that error message would appear when a deadlock of some kind prevented the volume history table from being accessed during the write attempt. One GB scratch volumes? At what ra
Author: Henrik Wahlstedt <SHWL AT STATOIL DOT COM>
Date: Wed, 21 Mar 2007 09:20:05 +0100
Hi, Cowen is probably right. The problem might be "At what rate do you create/delete these during the night?" TSM (5.3.4.2) have a timing issue regarding a fast update rate of volhist.out. And will g
Author: Steven Harris <steve AT STEVENHARRIS DOT INFO>
Date: Wed, 21 Mar 2007 19:54:58 +1000
Two possibilities Thomas. Is /tmp symlinked to /var/tmp? The problem may not be where you think it is. I have known for AIX filesystems to fill up but there be no file or files big enough to cause th