Greetings! We run a TSM server on a virtual RHEL6 system hosted by z/VM. The TSM databases are stored on a logical volume group that's getting close to running out of space. An obvious solution would be to add more DASD to the LVG. But because we're also running low on device numbers I've been tasked with exploring the possibility of expanding the physical drives currently used by the LVG. I've been studying a message thread from June of last year titled "Extending a DASD partition" which seems to suggest that this approach is possible. The approach I'm thinking of is to
* Allocate a single new drive much larger than the existing LVG physical drives. * Copy physical drive #1 to the new drive. * Redefine drive #1 to be larger * Copy physical drive #2 to the expanded drive #1 * Repeat with drives #3 through #n * Delete drive #n With this approach we only need to allocate one additional device number, and only for a limited period of time. Does this approach sound reasonable? There's one issue that I can think of, though: I'll be starting out with a set of devices allocated to the LVG: /dev/dasdc through /dev/dasdj. When I'm finished, I'll have dasdd through dasdk. It's not clear to me where the assignment of devices to the LVG is kept and whether it could easily be hand-edited. I'm open to any comments or suggestions you folks might have! Eric ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
