Jim, What would you like, specifically? From what I gather, you could: 1) Create a 3390-9 or -27 for the /usr partition. The problems are (a) possible I/O queueing to the physical device, (b) not have a correspondingly sized volume for D.R. purposes.
1a) True. But I think this is also true of any other UNIX system where a single I/O device services a large filesystem. I.e. a single 36 Gb SCSI drive on a PC can still only do a single I/O transfer at a time. 1b) I don't have a good idea about this. 2) Find all the "large" "second level" directories under /usr and make them their own filesystem on their own volume. /usr/local /usr/share /usr/X11 /usr/man Perhaps some more. 3) Use a "linear raid" to make multiple 3390-3 volumes into a single large filesystem. 4) Use LVM I'm not in this dilemma yet. But I, personally, like option 2. -- John McKown Senior Systems Programmer UICI Insurance Center Applications & Solutions Team +1.817.255.3225 This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. > -----Original Message----- > From: Jim Sibley [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 04, 2003 11:32 AM > To: [EMAIL PROTECTED] > Subject: size of distributions (redux) > > > Sorry for the shortened post just now. This is the > complete post: > > I've been playing with several of the new > distributions and they have one thing in common - the > size of the /usr directory is growing rapidly. In > early distributions, you could contain a zLinux system > on one 3390-3 image. Now, its taking two or three if > you need to install all the development libraries. > > I am reluctant to go to larger volume images because > larger images put more data behind a subchannel and > since zLinux does not support PAV's there is a > potential performance bottleneck for the I/O. > > So far, I have tried 3 approaches to contian the > problem: > > 1) two volume images, but /usr is 70-80% full and does > not allow for growth: > /dev/dasda1 / > /dev/dasdb1 /usr > > 2) three volumes seems to be a bit better > /dev/dasda1 / > /dev/dasdb1 /usr > /dev/dasdc1 /usr/share (uses /usr/share as a > mountpoint) > > Approaches 1 and 2, I would suspect, would grow in > complexity as the distributions grow. > > 3) a combination of raid and real partitions. This > improves performance and the size of the system volume > but does it lead to recovery problems? I have put /etc > on a "real" partition so that the systems parms can be > accessed directly for recovery, especially > /etc/raidtab. > > /dev/dasda1 /boot > /dev/dasda2 /etc > /dev/dasda3 swap > /dev/md0 / (raid0) > /dev/dasdb > /dev/dasdc > /dev/dasde > > Given that larger images beyond 3390-3 can be > performance problems w/o PAV's, what are the pros and > cons of the above 3 approaches? Are there other > approaches to setting up the system. (All three > methods, above, can be done during the initial cd-rom > install). > > ===== > Jim Sibley > Implementor of Linux on zSeries in the beautiful Silicon Valley > > "Computer are useless.They can only give answers." Pablo Picasso > > __________________________________ > Do you Yahoo!? > Yahoo! SiteBuilder - Free, easy-to-use web site design software > http://sitebuilder.yahoo.com >
