Hi Rick!
Formatting the whole volume was the case in the TSM 5.5 era, but not anymore.
Formatting a diskpool or filepool volume took ages back then because it was
filed with a text string (my name backwards :-), but with version 6 this has
changed and it just pre-allocates the requested space without formatting.
Creating a volume is now a matter of seconds, no matter how large it is.
Kind regards,
Eric van Loon
AF/KLM Storage Engineering
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Rhodes, Richard L.
Sent: dinsdag 8 september 2015 18:49
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: nfs mounted tsm storage becoming unavailable
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 AT VM.MARIST DOT EDU] On Behalf Of
Lee, Gary
Sent: Tuesday, September 08, 2015 10:38 AM
To: ADSM-L AT VM.MARIST DOT 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.
********************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain confidential and
privileged material intended for the addressee only. If you are not the
addressee, you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to this
e-mail or attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by return
e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
employees shall not be liable for the incorrect or incomplete transmission of
this e-mail or any attachments, nor responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered number
33014286
********************************************************
|
