At 02:11 PM 2/25/2008, you wrote:
>>> On Mon, Feb 25, 2008 at 1:58 PM, in message
<[EMAIL PROTECTED]>, Brian France <[EMAIL PROTECTED]>
wrote:
> Reason is that prior to today's IML, we were utilizing xstor, now we
> are not. So, I was looking for confirmation on the commands
> themselves - ( THANX!! - I figured that was the case but needed a
> sanity check ) since this was the first IML of this frame in many
> months. So now I need to investigate more closely as to what's going on.
I guess the first question that comes to mind is... What are you
using the VDISKs for? If it's Linux paging volumes, then... How big
are they?
Yes, VDISKS are for linux paging. We are mostly shared root and
use one VDISK for swap that is 200m for each image.
I never investigated who was using the expanded. I had understood
that the linux swap would use it as well as VM itself.
My real question is that after IML'ing this frame, my VM system
with it's linux images is not showing me what I'm used to seeing in
the way of allocation of xstor. SO, I figured the IML must in someway
activate the added storage even tho the q xstore command had shown me
it was added long ago. Since I've seen that a Q XSTORE does indeed
show you what is available, I must now ass/u/me that something else
changed in my linux machines or my vm system that I didn't know about.
You don't want to allocate a small number of large VDISKs to a Linux
guest for paging, since it will write all over them, chewing up a
bunch of expanded. If you allocate a number of smaller VDISKs, at
differing priorities, Linux will tend to not overflow into the
second, third, fourth, etc. VDISKs quite so easily, conserving your
expanded storage.
Mark Post
Brian W. France
Systems Administrator (Mainframe)
Pennsylvania State University
Administrative Information Services - Infrastructure/SYSARC
Rm 25 Shields Bldg., University Park, Pa. 16802
814-863-4739
[EMAIL PROTECTED]
"To make an apple pie from scratch, you must first invent the universe."
Carl Sagan
