Add minidisk to active Linux instance

[Kinnear, Mike]

Sorry, my mistake. The volume I was trying to link had not been attached
to the system. Surprisingly, it worked a lot better after I attached the
device. 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Add minidisk to active Linux instance

[Kinnear, Mike]

How can I add a new minidisk to an active Linux instance without IPL'ing
that instance? 
 
I've created a full pack minidisk (minus cyl 0) and formatted it.
I've added the MDISK statement to that user's directory entry.
I've issued the DIRECTXA.
 
I can't get a '#cp link' or '#cp att' command to work.
 
 
Thank you for any help.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

LVM - maximum PV's?

[Kinnear, Mike]

 
Thank you. However, I had already resolved the issue (and it was an
issue)  of needing to define the 6-character devices. Here is my current
/proc/dasd/devices. It is the dasdan and dasdao that I cannot get
attached to my LVM.  
 
0200(ECKD) at ( 94:  0) is dasda  : active at blocksize: 4096,
600840 blocks, 2347 MB
0201(ECKD) at ( 94:  4) is dasdb  : active at blocksize: 4096,
597240 blocks, 2332 MB
0205(ECKD) at ( 94:  8) is dasdc  : active at blocksize: 4096,
600840 blocks, 2347 MB
0206(ECKD) at ( 94: 12) is dasdd  : active at blocksize: 4096,
600840 blocks, 2347 MB
0210(ECKD) at ( 94: 16) is dasde  : active at blocksize: 4096,
600840 blocks, 2347 MB
0211(ECKD) at ( 94: 20) is dasdf  : active at blocksize: 4096,
600840 blocks, 2347 MB
0212(ECKD) at ( 94: 24) is dasdg  : active at blocksize: 4096,
600840 blocks, 2347 MB
0213(ECKD) at ( 94: 28) is dasdh  : active at blocksize: 4096,
600840 blocks, 2347 MB
0214(ECKD) at ( 94: 32) is dasdi  : active at blocksize: 4096,
600840 blocks, 2347 MB
0215(ECKD) at ( 94: 36) is dasdj  : active at blocksize: 4096,
600840 blocks, 2347 MB
0216(ECKD) at ( 94: 40) is dasdk  : active at blocksize: 4096,
600840 blocks, 2347 MB
0217(ECKD) at ( 94: 44) is dasdl  : active at blocksize: 4096,
600840 blocks, 2347 MB
0218(ECKD) at ( 94: 48) is dasdm  : active at blocksize: 4096,
600840 blocks, 2347 MB
0219(ECKD) at ( 94: 52) is dasdn  : active at blocksize: 4096,
600840 blocks, 2347 MB
021a(none) at ( 94: 56) is dasdo  : unknown
021b(none) at ( 94: 60) is dasdp  : unknown
021c(none) at ( 94: 64) is dasdq  : unknown
021d(none) at ( 94: 68) is dasdr  : unknown
021e(none) at ( 94: 72) is dasds  : unknown
021f(none) at ( 94: 76) is dasdt  : unknown
0220(ECKD) at ( 94: 80) is dasdu  : active at blocksize: 4096,
600840 blocks, 2347 MB
0221(ECKD) at ( 94: 84) is dasdv  : active at blocksize: 4096,
600840 blocks, 2347 MB
0222(ECKD) at ( 94: 88) is dasdw  : active at blocksize: 4096,
600840 blocks, 2347 MB
0223(ECKD) at ( 94: 92) is dasdx  : active at blocksize: 4096,
600840 blocks, 2347 MB
0224(ECKD) at ( 94: 96) is dasdy  : active at blocksize: 4096,
600840 blocks, 2347 MB
0225(ECKD) at ( 94:100) is dasdz  : active at blocksize: 4096,
1802880 blocks, 7042 MB
0226(ECKD) at ( 94:104) is dasdaa : active at blocksize: 4096,
1802880 blocks, 7042 MB
0227(ECKD) at ( 94:108) is dasdab : active at blocksize: 4096,
1802880 blocks, 7042 MB
0228(ECKD) at ( 94:112) is dasdac : active at blocksize: 4096,
1802880 blocks, 7042 MB
0229(ECKD) at ( 94:116) is dasdad : active at blocksize: 4096,
1802880 blocks, 7042 MB
022a(none) at ( 94:120) is dasdae : unknown
022b(none) at ( 94:124) is dasdaf : unknown
022c(none) at ( 94:128) is dasdag : unknown
022d(none) at ( 94:132) is dasdah : unknown
022e(none) at ( 94:136) is dasdai : unknown
022f(none) at ( 94:140) is dasdaj : unknown
0230(ECKD) at ( 94:144) is dasdak : active at blocksize: 4096,
1802880 blocks, 7042 MB
0231(ECKD) at ( 94:148) is dasdal : active at blocksize: 4096,
1802880 blocks, 7042 MB
0232(ECKD) at ( 94:152) is dasdam : active at blocksize: 4096,
1802880 blocks, 7042 MB
0233(ECKD) at ( 94:156) is dasdan : active at blocksize: 4096,
1802880 blocks, 7042 MB
0234(ECKD) at ( 94:160) is dasdao : active at blocksize: 4096,
1802880 blocks, 7042 MB
 



From: Carsten Otte [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, March 16, 2005 6:25 PM
To: Linux on 390 Port
Cc: Kinnear, Mike
Subject: Re: LVM - maximum PV's?



>On a SUSE SLES8 system I've created an LVM with 15 full mod-3 3390's
and
>8 mod-9's. I cannot get the 9th mod-9 to become a member of LVM. the
>pvcreate appears to work OK, but the volume is not on the pvscan list,
>nor included in the vgdisplay total. Any ideas? 
Check /proc/devices. If dasd shows up multiple times (not only major 94)
you are most probably running 
out of device nodes. In this case you can create new ones using mknod,
the major/minor numbers of the 
dasds can be found in /proc/dasd/devices. 
like this: 
mknod /dev/dasdabc b   
mknod /dev/dasdabc1 b   
mknod /dev/dasdabc2 b   
mknod /dev/dasdabc3 b   
(no more, we only have 3 partitions and minor+4 belongs to a different
volume) 

with kind regards
Carsten Otte
IBM Linux Technology Center / Boeblingen lab
-- 
omnis enim res, quae dando non deficit, dum habetur et non datur, nondum
habetur, quomodo habenda est 



"Kinnear, Mike" <[EMAIL PROTECTED]> 
Sent by: Linux on 390 Port  

16/03/2005 08:47 PM 
Please respond to Linux on 390 Port 



To:LINUX-390@VM.MARIST.EDU 
cc: 
Subject:LVM - maximum PV's? 




On a SUSE SLES8 system I've created an LVM with 15 full mod-3 3390's and
8 mod-9's. I cannot get the 9th mod-9 to becoem a member of LVM. 

LVM - maximum PV's?

[Kinnear, Mike]

On a SUSE SLES8 system I've created an LVM with 15 full mod-3 3390's and
8 mod-9's. I cannot get the 9th mod-9 to becoem a member of LVM. the
pvcreate appears to work OK, but the volume is not on the pvscan list,
nor included in the vgdisplay total. Any ideas? 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

VSWITCH and HIPERSOCKETS

[Kinnear, Mike]

I've researched the archives and redbooks. I think I've come across every 
combination of implementation except the one I'm trying to do. We have a number 
of VSWITCH LINUX instances running under one z/VM LPAR. We have a production VM 
TCP/IP stack that we use for 'older' VCTC connections until we get them 
switched over to VSWITCH. I would like to communicate from the LINUX instances 
on the VSWITCH with an z/OS LPAR using HIPERSOCKETS. I don't want to 
'experiment' with the production TCP/IP stack, so I am configuring a second 
stack to do the HIPERSOCKETS links. What I've tried complains that a virtual 
LAN is not present, but if I'm reading the guides correctly, I shouldn't need 
one. How do I get the second stack to be a HIPERSOCKETS pipe for the VSWITCH 
network? Any help is greatly appreciated.

Mike Kinnear
Systems Programmer
GuideOne Insurance

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Real/virtual memory ratio

[Kinnear, Mike]

We use z/VM for a Linux environment. A Redbook,
http://www.redbooks.ibm.com/redpapers/pdfs/redp3661.pdf
   on page 7 says
you should have a 1.5/1 virtual to real ratio for Linux environments running
Websphere applications. We've been running fine at about a 4/1 ratio for a
few months. Recently we have put a couple of new instances up with 768M
virtual memory each and we are seeing some high paging periods as well as a
couple of loops in Linux paging modules. Has anyone experienced any pain in
this area? 

   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Accessing DASD on a Shark from Linux under z/VM

[Kinnear, Mike]

What is the VM level required? 

-Original Message-
From:   David Boyes [mailto:[EMAIL PROTECTED]
Sent:   Friday, February 20, 2004 12:48 PM
To: [EMAIL PROTECTED]
Subject:Re: Accessing DASD on a Shark from Linux under z/VM

> Interesting idea...   I need to look into this.   Is there a
> way for z/OS to
> see those volumes?

No. z/OS has no support for FCP yet.

> If not, we couldn't use OFFLINDR running
> on z/OS to
> backup the volumes.

But you can use my nifty Amanda/DFHSM combination, and you get file-level
restore as a freebie. See http://www.sinenomine.net/ for a pointer to the
presentation.


> Are many shark shops using open system formatted DASD for z/Linux?

If you have the prereqs (FICON adapter and right ucode levels, plus the SCSI
support in your Linux distribution), it's a real win, especially for
databases.

-- db
   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.

Memory displays on Linux

[Kinnear, Mike]

We recently encountered an application loop with a Linux Websphere instance.
I was able to get a VM PER Branch trace, but I cannot find any command
within Linux to display those memory locations or to determine where modules
are actually loaded. The code does not have any 'eyecatchers' either, so
doing VM displays with translate are not helpful either. I'm having trouble
determining what modules are being executed.

ESALPS vs. VMRTM/VMPRF

[Kinnear, Mike]

Has anyone running Linux under VM attempted to compare or evaluate the
differences between the Velocity Software's ESALPS and IBM's VMRTM/VMPRF?
What were your conclusions as far as function and value?

Thank you for your help.

Communication between Linux and z/VM

[Kinnear, Mike]

I am trying to develop an exec that will shut down a Linux instance from VM
user MAINT. I have figured out how to become a secondary user and log on as
root and provide a password using CPSEND mechanism. The problem I'm having
is being able to code a routine that can parse a response sent from the
Linux instance. I want to know if an "application" shutdown within the
instance has completed before I issue a "shutdown -h now" to the instance. I
have it working just using some "sleep" commands, but I need more control
than that. Does anyone have any ideas? Thanks.

software sharing and management

[Kinnear, Mike]

We are in the process of creating a production LINUX world within a z/VM
environment on an IFL. We are planning to create 20-30 instances for various
test and production application reasons. Is there any way for these various
guests to share the kernel or any other software? I have read a Marist doc.
on using DCSS to use for the IPL code, but not for any operating system
software. We are concerned about redundant data storage and more
importantly, software maintenance and management of the basic operating
system and key utilities. We already are experiencing a management nightmare
due to various application needs to install patches and updates and trying
to determine what fixes we should put where and when.