A colleague just sent me this link:

See DCF 1497567:
Allocation and use of scratch and predefined FILE storage pool volumes
http://www-01.ibm.com/support/docview.wss?uid=swg21497567

By the way, keep in mind that at least on some appliances, the NFS-mounted 
filespace "used/remaining space" attributes apply to the entire appliance 
filesystem, no matter which directory you query.  As the platforms improve, 
some sort of quota system will probably be provided.  Although whether it apply 
to pre-compressed/deduped or post-compressed/deduped numbers is a good question.

How to allocate directories among devclasses is becoming a more interesting 
topic as NFS-mounted dedup appliances become more prevalent.  Some resources 
are tied to devclasses, such as mountpoints, that would require some 
consideration.

Richard

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Rhodes
Sent: Friday, November 11, 2011 3:00 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Dev Class type FILE with multiple directories

If you have a dev class of type FILE with multiple directories, how does
TSM determine which dir to create a new volumes in?

I've checked everywhere I can think of and the most I can find is comments
that TSM is free to  pick any dir to create a new scratch vol in. Assuming
lots of free space in multiple directories specified for one dev class
type file,  how does TSM pick which dir to create a file dev in?

What I'm interested in is one of those "what if" questions.  If you have a
file dev class (NFS) on a dedup box and its getting full.  So you purchase
a new box, set it up, and add it to the devclass as an extra directory.
You now have two directories.  If one is full TSM will use the other, but
if both have freespace I'm curious how TSM decides which to use.

Just curious . . .

Rick


-----------------------------------------
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.