This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
closing since no additional info provided
Trying again:
With multiple directories, there is not a size restriction relating to use of one directory or another. If there were such a restriction it would have been documented.
The algorithm for choosing is not documented, but is currently loosely round-robin. IBM doesn't recommend using multiple directories in the same file system because it makes space checks unreliable ( aside from the possibility of I/O contention depending upon the underlying physical space layout ).
If there is a problem with multiple sessions and allocation within multiple directories, a service call is advisable or please append additional information as to why it's thought
that this restriction exists. Please ensure that the client is configured for multiple sessions with multiple mountpoints -- Check the client resourceutilization option as well
as the node's maxnnump value, along the mountlimit parameter on the device class.
An out-of-band observation:
Assuming that the NFS mounts are for output directories, please be aware that NFS must be configured in a manner which ensures that I/O results in data being written in a non-volatile manner - it is not acceptable to have I/O fail on the NFS server after TSM has been notified that data was successfully written. NFS can be configured for maximum performance at the expense of reliability.
File system requirements are covered in the Administration guide.