It sounds like you are pre-defining the file vols on the NFS share. If you pre-define vols I believe TSM writes the entire vol to initialize it. That would be a very heavy write load. It sounds like maybe the NFS server is overloaded and maybe causing I/O errors to the other TSM's.
Are you seeing ANR errors in the actlog of any of the TSM servers when this problem occurs? I'd check the network stats for your TSM server and NFS server. Possibly getting lan errors under heavy load is causing problems. Are your NFS shares mounted hard? I believe they should be. Run around - don't pre-define vols, let TSM to create scratch vols as needed. That's what we do for our NFS DataDomain shares. Just some thoughts! Rick -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary Sent: Tuesday, September 08, 2015 10:38 AM To: ADSM-L@VM.MARIST.EDU Subject: nfs mounted tsm storage becoming unavailable We are trying to troubleshoot a problem with our tsm disk storage. Tsm server 6.3.4 running on RHEL 6.5. Our storage is a set of subdirectories on a file system mounted via nfs v3 to all three of our tsm servers. All goes fine until an attempt is made to define one or more volumes to a storage pool. At that time, if other tsm servers are writing to the storage, those volumes will become red-only when the volume define is in process. Other operations, such as reclamation, and normal writing do not cause problems. Our storage provider, (nexenta) is asking what tsm does when creating a storage volume. So, I am coming to the list for information. Just what does tsm do under the covers when defining a storage volume? Thanks for any help. ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.