I tried them all again: PAGE, SPOL, TDSK is protected:
Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:08
link * 1 1 MR cse
Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:13
link * 2 2 MR DRCT
Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:18
link * 3 3 MR PAGE
HCPLNM1152E KRIS 0003 has not been linked because
it would overlap system paging space.
Ready KRIS at VMKBCT01 (01152); T=0.01/0.01 08:33:22
link * 4 4 MR Spool
HCPLNM1152E KRIS 0004 has not been linked because
it would overlap system spool space.
Ready KRIS at VMKBCT01 (01152); T=0.01/0.01 08:33:27
link * 5 5 MR ckpt
Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:31
link * 6 6 MR Warm
Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:35
link * 7 7 MR Tdsk
HCPLNM1152E KRIS 0007 has not been linked because
it would overlap system temporary disk space.
Ready KRIS at VMKBCT01 (01152); T=0.01/0.01 08:33:38
So the problem is probably caused by that the page area was never
properly formatted.
2008/1/7, Alan Ackerman <[EMAIL PROTECTED]>:
> On Fri, 4 Jan 2008 14:09:05 +0100, Fritz, Wilhelm <[EMAIL PROTECTED]> wr
> ote:
>
> Sounds like you have some other minidisk defined overlaying your page spa
> ce. When one of your
> virtual machines writes to it, it causes paging errors.
>
> Take a look at your directory. You should have NO other minidisks defined
> in the range 0-3338
> on device 520PG1 02D5. (Or overlaying the other page pack, either.)
>
> Alan Ackerman
> Alan (dot) Ackerman (at) Bank of America (dot) com
>
--
Kris Buelens,
IBM Belgium, VM customer support
