Re: VDISK strangeness

[Dennis G. Wicks]

Greetings;

That is what I do. (I _am_ the "VM guy"!)

I have a routine in the PROFILE EXEC that detects,
formats and reserves any (VDSK) and when I defined
the "real" mdisks for swap I formatted and reserved them.

I just completed another experiment that indicates that
ECKD disks aren't "working" at 2.. addresses. I can't
dasdfmt or mke2fs either.

Here is some config info:

     0106(ECKD) at ( 94: 24) is   dasdg:active at blocksize: 4096, 90000
blocks, 351 MB
     0201(DIAG) at ( 94: 68) is   dasdr:active at blocksize: 4096, 90000
blocks, 351 MB
          ^^^^
     (Could this be the problem? Why doesn't it config 106 the same way?)

     Both are 500 cyl mdisks, formatted and reserved.

But when I try to mkswap and swapon:

     [root@krypton linux]# mkswap /dev/dasdg1
     Setting up swapspace version 1, size = 368214016 bytes
     [root@krypton linux]# swapon /dev/dasdg1

     and then

     [root@krypton linux]# mkswap /dev/dasdr1
     /dev/dasdr1: Illegal seek

     Of course, no sense in trying swapon for this one!

This is TurboLinux 7.0, kernel 2.4.7 and I can do anything
to it I want, whenever I want. So, if there is anything I can
try to isolate the problem, lety me know!

Thanks,
Dennis






                    "Post, Mark K"
                    <mark.post@eds.       To:     [EMAIL PROTECTED]
                    com>                  cc:
                    Sent by: Linux        Subject:     Re: VDISK strangeness
                    on 390 Port
                    <[EMAIL PROTECTED]
                    ARIST.EDU>


                    05/02/02 09:37
                    AM
                    Please respond
                    to Linux on 390
                    Port






When my VM guy set up my Vdisk for me, he put commands in the guest's
profile exec to CMS format and reserve the disk before IPLing Linux.  The
format takes about (10ms from hat I can tell.)  I've not had any problems
with them so far, using them at virtual address 400, /dev/dasdq.

Mark Post

-----Original Message-----
From: Dennis G. Wicks [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 01, 2002 5:48 PM
To: [EMAIL PROTECTED]
Subject: VDISK strangeness


Greetings;

While experimenting with swap on vdisk I have encountered
a strange problem.

When my vdisk is on x'201' it doesn't work. When I try
to do a mkswap I get "/dev/dasdr1: Illegal seek".

When I move the vdisk to x'104' everything works
as designed. It is now /dev/dasde.

Any clues? Doesn't FBA work with addresses like x'200'?
Is /dev/dasdr too "high" a letter?

Now complicated procedures. I use HCP to change the address
of the vdisk and do a shutdown -r. I have both /dev/dasde
and /dev/dasdr in /etc/fstab.x

Many TIA!
Dennis