What filesystem type? (reiser, ext3, etc.) Could you be running out of inodes at times?
Tom Kauffman NIBCO, Inc -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Denier Sent: Tuesday, March 20, 2007 1:57 PM To: [email protected] Subject: Error writing volume history file 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 to /var/tsm_automation/volumehistory. Successive occurances of this pair of messages are typically a week to two weeks apart. We have a 5.3.4.0 server running under mainframe Linux. There is plenty of disk space available in the /var file system. The Linux error logs do not report any I/O errors when these TSM messages occur. The path at the end of the second message is the one specified for the sequential volume history file in our server options file. I have already contacted IBM, but I am not optimistic about getting a resolution; the last e-mail I got from IBM requested 'ls' command output needed to check the possibility of root not having write access to the volume history file. Has anyone else seen this and found a way to stop it? CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
