ypcat
ADSM.ORG Member
Hello Folks,
I have a question so I'm going to just come right out and ask. In a large TSM instance there used to be a bug. If you string filesystems together in the devclass definition and delimit them by comma it would work as a single storage pool until one of the file systems filled up. After that it would no longer create scratch volumes in the new (second) file system - based on the maxscratch parameter. You would have to create new volumes manually. Has that been fixed?
I was forced to create a string of very large pools to accommodate things based on JFS2 - my only choice currently so allocating resources, reporting, etc becomes a pain.
I was wondering if anyone here was stringing 32TB max JFS2's together in a single devclass (type=file) and if you have a full JFS2, does it automatically create scratch in the second file system? I'd like to consolidate my TSM storage pools.
Thanks in advance.
I have a question so I'm going to just come right out and ask. In a large TSM instance there used to be a bug. If you string filesystems together in the devclass definition and delimit them by comma it would work as a single storage pool until one of the file systems filled up. After that it would no longer create scratch volumes in the new (second) file system - based on the maxscratch parameter. You would have to create new volumes manually. Has that been fixed?
I was forced to create a string of very large pools to accommodate things based on JFS2 - my only choice currently so allocating resources, reporting, etc becomes a pain.
I was wondering if anyone here was stringing 32TB max JFS2's together in a single devclass (type=file) and if you have a full JFS2, does it automatically create scratch in the second file system? I'd like to consolidate my TSM storage pools.
Thanks in advance.