On Fri, Apr 04, 2003 at 08:37:31PM -0500, Seay, Paul wrote:
>> > So, using 24GB volumes is probably the best way to go. Also, JFS
>> > formatted volumes is the way to go.
>> Why would you prefer JFS volumes? I use raw and find it a bit better since
>> the VM want cache anything.
> Ever tried maxpg
Ever tried maxpgahead? That is why you want JFS. Causes things to fly.
-Original Message-
From: Emil S. Hansen [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2003 4:54 AM
To: [EMAIL PROTECTED]
Subject: Re: Defining TSM Disk pools on ESS wisdom wanted
On Thu, Mar 27, 2003 at 10:25
Message-
From: Daniel Sparrman [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 27, 2003 1:25 AM
To: [EMAIL PROTECTED]
Subject: Re: Defining TSM Disk pools on ESS wisdom wanted
Hi
I would suggest having as much volumes as possible. This is because AIX
treats every volume as a PV, and one PV can onl
; 183 62 TÄBY
> Växel: 08 - 754 98 00
> Mobil: 070 - 399 27 51
>
>
>
>
> "Anthonijsz, Marcel M SITI-ITDGE13" <[EMAIL PROTECTED]>
> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> 2003-03-27 10:18
> Please respond to "ADS
On Thu, Mar 27, 2003 at 10:25:15AM +0100, Daniel Sparrman wrote:
> So, using 24GB volumes is probably the best way to go. Also, JFS
> formatted volumes is the way to go.
Why would you prefer JFS volumes? I use raw and find it a bit better
since the VM want cache anything.
--
Best Regards
Emil S.
27 10:18
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Defining TSM Disk pools on ESS wisdom wanted
Hi,
We are redefining our TSM disk pools on IBM ESS storage. We got 39 x 24 GB
LUNs from our storage collegues. Tot
Hi,
We are redefining our TSM disk pools on IBM ESS storage. We got 39 x 24 GB
LUNs from our storage collegues. Total 936GB.
LUNs are spread across the whole ESS. Now what is the best way, TSM wise and
performance wise to define these disks to TSM?
Make the volumes as large as possible?
or define
