Re: SHARE LVM dinner and Velocity event in San Jose

[Ron Foster]

Ray,
I may have sent you this already.

Thanks for the stuff you sent me via Quincy.
Ron

On Thu, Feb 23, 2017 at 6:33 AM, Rick Barlow  wrote:

> Last Chance... You must *respond today.*
>
> This is being posted to both IBMVM and LINUX-VM.
>
> If you are planning to attend SHARE in San Jose, please note the update to
> the traditional LVM Program Dinner event.
>
> Greetings from the SHARE LVM Program volunteer team!
>
> It is a tradition at SHARE conferences to plan a trip to a local dining
> establishment for the LVM Program Dinner on Wednesday at each event. The
> goal of the event is for anyone who may be interested in learning more
> about the Linux and VM Program at SHARE to join us for an informal,
> individual check dinner.
>
> While we are in San Jose in March, the Velocity Software team has planned a
> celebration of their company anniversary. In lieu of a separate LVM Dinner
> event, we are planning to join in the activity being planned by Velocity.
> The capacity of the event is limited and each person attending will require
> a wrist band that will be available from the Velocity booth at the SHARE
> Expo. You can find more information about the event at
> http://velocitysoftware.com/anniv.html.
>
> If you are interested in joining us for the event, please notify the LVM
> Dinner coordinator brian.ja...@ca.com.
>
> Looking forward to seeing you in San Jose,
>
> Rick Barlow
> SHARE LVM Program Manager
>
> Office: (614) 249-5213
>
> mailto: rrhbar...@gmail.com
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Moving on

[Ron Foster]

I started in the business in 1972.  Our local college had an 8k IBM 1130  
Almost immediately,  I wanted to find out move about it. After graduation, I 
went to work at my present employer(Baldor).  After 40 years here, I have 
accepted an early retirement.


I enjoyed the people on the mailing list. They almost always had the answer to 
whatever problem. I was having at the moment.


It was always nice to put a face with a name at SHARE.


Thanks mailing list.  Keep helping people.


(Anyone happen to have the instructions on haw to move  to  a different email 
address.

I am using a work email  address that will be killed in the next day or two.)

Ron Foster

ABB - Fort Smith

Large Systems Analyst

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-648-5985

Email: ron.fos...@us.abb.com<mailto:ron.fos...@baldor.abb.com>

IM Address:ron.fos...@us.abb.com

www.baldor.com<http://www.baldor.com/>



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SLES 11 SP4 - Kernel locking up

[Ron Foster]

>From the mailing list and share. 

Sent from my iPhone

> On Aug 3, 2016, at 4:32 PM, Marcy Cortes  
> wrote:
> 
> Yes, we saw it and someone else here did last week too.
> SUSE has a test fix for it.
> 
> Has to do with running 32bit programs.  ILMT was the one that we discovered 
> it with.
> 
> 
> 
> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Jorge 
> Fábregas
> Sent: Wednesday, August 03, 2016 2:23 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: [LINUX-390] SLES 11 SP4 - Kernel locking up
> 
> Hi everyone,
> 
> We're having some kernel locking issues after installing the latest kernel 
> for SLES 11 SP4 (kernel-default-3.0.101-77.1).  This is on two separate Linux 
> guests and it happens - right away- after starting some network applications: 
> Linux completely freezes.  If we go back to the previous kernel everything 
> runs fine.
> 
> I've opened a case with SUSE & we'll be uploading a z/VM dump of the guests 
> but wondered if anyone else has seen this before (recently)?
> 
> Thanks!
> 
> --
> Jorge
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send email 
> to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Change DNS part of the host name without rebooting

[Ron Foster]

Hello,


We are being tasked with changing the dns domain name portion of a machine's 
host name.

That is, change foo.baldor.com to foo.baldor.abb.com.


Is this possible without scheduling an outage of our Linux farm?


Thanks,

Ron


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com<mailto:ron.fos...@baldor.abb.com>

IM Address:ron.fos...@baldor.abb.com

www.baldor.com<http://www.baldor.com/>



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Change dns name without re-ipling

[Ron Foster]

Hello,

We have a situation where we are being tasked with changing the dns domain 
portion of a machine's hostname.


For example,  we need to change foo.baldor.com to foo.baldor.abb.com.


Is this possible without a re-ipl?


Thanks.

Ron


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com<mailto:ron.fos...@baldor.abb.com>

IM Address:ron.fos...@baldor.abb.com

www.baldor.com<http://www.baldor.com/>



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Change DNS domain name

[Ron Foster]

Hello listers,


Surely someone has had to do this.


We use the baldor.com dns domain.


We got bought out sometime back.  And for the most part kept the baldor.com 
domain name.  Although we did have to change some addresses to baldor.abb.com.


The time has come to change all baldor.com addresses to baldor.abb.com 
everywhere.


What do I need to do to change this besides changing /etc/resolv.conf and 
having the DNS folks make their changes.


Ron


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com<mailto:ron.fos...@baldor.abb.com>

IM Address:ron.fos...@baldor.abb.com

www.baldor.com<http://www.baldor.com/>



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

[no subject]

[Ron Foster]

review LINUX-390


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

review linux-S390

[Ron Foster]

review Linux-S390


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Where should we have been watching to find out about the leap second problem?

[Ron Foster]

Everyone,


Where should we have been watching so the we would not let the leap second

problem sneak up on us?


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

What might happen if our sles11 sp3 systems are not at the level to handle the leap second.

[Ron Foster]

Everyone,


When our SLES11 SP3 maintenance package was put together, it was put together at

the  3.0.101-0.40-default kernel instead of the kernel level that was current.

According to to tid 7016150 this is vulnerable to bug 915335.  Any ideas on 
what we

might be letting ourselves in for?


Ron

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Monitoring / logging for compliance purposes

[Ron Foster]

Everyone,



Today we have been visited by the compliance folks from our parent company.



We are now looking for logging/monitoring software for compliance purposes.



Anyone care to share what you all do to satisfy your compliance folks?



Ron

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Multiple migration products visible to zypper prior to SP2 upgrade to SP3

[Ron Foster]

Hello listers,



We are still in midst of upgrading our last SLES11SP2 system.



We have made several attempts on this system.  We have tried Suse Manager.  We 
have tried SMT.  We have tried wagon.  And we have tried various repositories.  
SMT and Suse Manager.



We are investigating using the zypper method this time.  I am examining the 
zypper method as outline in Suse Knowledge base article 7102368.  And the 
active repositories belong to suse manager.



The system is at SLES11SP2.  But the repositories may not exactly reflect that. 
 For example, when I issue a



zypper se -t product | grep -h -- -migration | cut -d\| -f2



I get

 SUSE_SLES-SP2-migration
 SUSE_SLES-SP3-migration



Is this going to cause problems later on when I issue I start the actual 
migration and I issue the commands for real.  Will the SP2 migration product be 
gone, or should I install it, or should I just leave it be.



Thanks,



Ron

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

failed dependencies on zlib-devel during upgrade from SLES11sp2 to SLES11sp3

[Ron Foster]

Hello all,

My cohort is trying to convert our last SLES11SP2 system to SLES11SP3.  So far, 
we have made two attempts, but keep running into a dependency problem.

Early on, we get the following :
zlib-devel-1.2.3-15.2.s390xrequires zlib 1.2.3 but this requirement cannot 
be provided.

deleted providers zlib-1.2.3-106.34.s390x

Possible solutions
Following actions will be done.  See below.

deinstallation of zlib-devel-1.2.3-15.2.s390x

break zlib-devel-1.2.3-15.2.s390x

This is a SAP central instance.

Looking at software management, we see:
 
???
? ?Name  ?Summary   ?Avail. 
Vers.?Inst. Vers.?S?
? ?php53-zlib?PHP5 Extension Module ?5.3.17 
 ?   ? ?
?  i  ?zlib  ?Data Compression Library  ?1.2.7  
 ?1.2.3  ? ?
   i  ?zlib-32bit?Data Compression Library  ?1.2.7  
 ?1.2.3  ? ?
?  i  ?zlib-devel?Include Files and Libraries mandatory for Development.?   
 ?1.2.3  ? ?

Any ideas on how to satisfy the dependencies?

Looking at the other SAP systems, all they have installed is the zlib and the 
zlib-32bit packages.

Ron

Ron Foster
Baldor Electric Company
5711 R S Boreham Jr Street
Fort Smith, AR 72901
Phone:479-648-5865
Fax:479-646-5440
Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com
IM Address:ron.fos...@baldor.abb.com
www.baldor.comhttp://www.baldor.com/

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Linux, NFS, and Windows shares

[Ron Foster]

Everyone,

We have a Windows application that accesses files on Linux on system z.  We=
 currently use Microsoft services for Unix.



But we have found that Microsoft is dropping support for this product.  And=
 we have to migrate to a newer operating system.  So we need plan B.



We have tried using native TCPIP client that is in Windows 2008 R2, at leas=
t one function used by the application is not usable. (we make the nfs conn=
ection using the NFS client and then map a Windows share on top of it.



Now we are trying out the Open Text NFS gateway.  However it uses pcnfsd to=
 do authentication.



Anyone have any idea of how to get hands on a PCNFSD module.



Anyone thought about Samba and a NFS mount?

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Where do you specify PORTNO on a SLES11 SP2 system

[Ron Foster]

Everyone,



We are trying to upgrade a system to SLES11 SP2.  We have one of our OSA 
adapters that has a lan on PORTNO 1 instead of PORTNO 0.



How do we specify that? In /etc/sysconfig/hardware?



Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Where do you specify PORTNO on a SLES11 SP2 system

[Ron Foster]

Thanks

After a reboot, the interface came up.

Ron

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Marcy Cortes 
[marcy.d.cor...@wellsfargo.com]
Sent: Wednesday, March 05, 2014 12:34 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Where do you specify PORTNO on a SLES11 SP2 system

It's in /etc/udev/rules.d/51-qeth-0.0..rules

Will be something like
ACTION==add, SUBSYSTEM==ccwgroup, KERNEL==0.0., ATTR{portno}=1


Yast2 is your friend.



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Foster
Sent: Wednesday, March 05, 2014 10:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Where do you specify PORTNO on a SLES11 SP2 system

Everyone,



We are trying to upgrade a system to SLES11 SP2.  We have one of our OSA 
adapters that has a lan on PORTNO 1 instead of PORTNO 0.



How do we specify that? In /etc/sysconfig/hardware?



Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: SLES 11 SP3 problems

[Ron Foster]

Is there a particular process using all the time?

Sent from my iPhone

On Nov 1, 2013, at 12:31 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com 
wrote:

 We're experiencing a problem with kernel 3.0.93 (SP3).   It seems on servers 
 that are memory constrained can go into a loop doing tons of i/o - 8000+ / 
 second.
 It seems to happen with things like WAS deploys.We may have also been 
 able to recreate use a simple perl array.
 
 Has anyone else seen this?
 
 Yes, we have a high priority SR opened with SUSE.
 
 Oddly we have seen something like this after a kernel update on SP2.  That 
 was solved by changing vm.swappiness to something  0.We have put it back 
 to 60 (the default) and still get the problem.
 Upping the memory solves it, but obviously, that's not something we want to 
 be doing, especially in our constrained dev environment.
 
 
 Marcy 
 
 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: TX-Errs on hipersocket interface.

[Ron Foster]

Ursula,

We are running kernel  3.0.42-0.7-default.

Would it help to go to a more recent kernel?

Thanks,
Ron Foster

Baldor Electric Company
 
5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ursula Braun 
[ubr...@linux.vnet.ibm.com]
Sent: Friday, July 26, 2013 3:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.

Jon,

without any performance data my answer can be only vague. But let's
assume a performance increase for data sending when moving from SLES10
to SLES11. If the receiver has already been close to his buffer usage
limit with SLES10, he might hit this limit after upgrading the sender to
SLES11.

Regards, Ursula Braun, Linux on System z Development, IBM Germany


On Thu, 2013-07-25 at 18:21 +, Veencamp, Jonathon D. wrote:
 Question:  Why would SLES 11 see hipersocket retransmits and window 
 adjustments and not SLES 10?  Is the device driver either more forgiving or 
 efficient on SLES 10?

 I'm just curious.  I may be in the same situation soon.

 Regards
 Jon Veencamp
 Federated Insurance

 -Original Message-
 From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ursula 
 Braun
 Sent: Thursday, July 25, 2013 9:54 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: TX-Errs on hipersocket interface.

 Ron,

 Carsten's first explanation is correct. If you see tx_errors on a
 HiperSockets interface, it usually means transmission of a packet fails
 because the receiver has currently no free receive buffer. You should
 verify first if the receiver has configured the maximum of 128 buffers
 (sysfs attribute buffer_count) for his HiperSockets device. 128 is
 nowadays the default, but older qeth driver versions run with a default
 of 16. If you see the tx_errors even though your receiver runs already
 with the maximum of 128 buffers, you either have to live with the
 autotuning mechanisms of tcp or you take actions to slow down the sender
 or to accelerate the receiver.

 As Alan suggested we can document this in the Device Driver book. The
 other option would be to change the current behavior of the qeth driver
 and increase probably both the tx_dropped and the tx_error counter.

 It is definitely not a problem to report to SuSe folks.

 Kind regards, Ursula Braun, Linux on System z development, IBM Germany

 On Thu, 2013-07-25 at 13:18 +, Ron Foster wrote:
  Carsten,
  Do you know where I would start looking for causes of the transmit errors 
  on Hipersockets?
  The error is occurring on SLES11 SP2 systems.  We are not having it on our 
  SLES10 SP4 systems.
  Do I need to open a problem with the SuSe folks?
 
  Thanks,
  Ron Foster
  Baldor Electric Company
  5711 R S Boreham Jr Street
  Fort Smith, AR 72901

 

 The information contained in this e-mail message is intended only for the 
 personal and confidential use of the designated recipient(s) named above. 
 This message may be an attorney-client or work product communication which is 
 privileged and confidential. It may also contain protected health information 
 that is protected by federal law. If you have received this communication in 
 error, please notify us immediately by telephone and destroy (shred) the 
 original message and all attachments. Any review, dissemination, distribution 
 or copying of this message by any person other than the intended recipient(s) 
 or their authorized agents is strictly prohibited. Thank you.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Performance on SLES11 SP2 guest after migration from SLES10 SP4

[Ron Foster]

Berry,

Thanks

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of van Sleeuwen, 
Berry [berry.vansleeu...@atos.net]
Sent: Thursday, July 25, 2013 1:48 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Performance on SLES11 SP2 guest after migration from SLES10 SP4

Hi Ron,

There is a bug in vmstat that results in zero IO. I have seen the same when 
investigating a CCL problem. So don't (for now) rely on the IO counter in 
VMSTAT.

I did report it to IBM and I guess through that channel an update for vmstat 
will be created.

Regards, Berry.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Foster
Sent: woensdag 24 juli 2013 18:03
To: LINUX-390@VM.MARIST.EDU
Subject: Performance on SLES11 SP2 guest after migration from SLES10 SP4


Hello listers,



Over the weekend, we migrated a couple of large SAP systems from SLES10 SP4 to 
SLES11 SP2.  These are large SAP application servers (22GB).



Our SAP folks have a transaction that can be used to measure SAP response time. 
 Our servers are grouped by the applications they run.



Intermittantly one of the SAP application servers in one group will for a while 
have a response time that is about 3 times larger that the SLES10 systems.  
1600 ms  vs 500 ms.  The other sles11 system in the other application group 
will have a response time that is around 700 ms, and the others in the group 
have around 350 ms.  After a few minutes the response times on the SLES11 
systems return to normal.



I start to look at things.  I issue the vmstat command and find something.  The 
in column in the system area is all zeros.  The man page says that this is the 
number of interrupts per second.



Anyone else experience response time problems, or not get the interrupts 
information?



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/





Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org

Re: TX-Errs on hipersocket interface.

[Ron Foster]

Carsten, 

Do you know where I would start looking for causes of the transmit errors on 
Hipersockets?

The error is occurring on SLES11 SP2 systems.  We are not having it on our 
SLES10 SP4 systems.

Do I need to open a problem with the SuSe folks?

Thanks,

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte 
[co...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.

Alan wrote:
Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped, not TX error. Forget
about my
reply then, time to look at other causes for that TX error. Sorry for the
noise.

with kind regards
Carsten Otte
System z firmware development / Boeblingen lab
---
Every revolution was first a thought in one man's mind;
and when the same thought occurs to another man, it is the key to that era.

 - Ralph Waldo Emerson, Essays: First Series, 1841

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: TX-Errs on hipersocket interface.

[Ron Foster]

The receiver is zos.  Anybody here know how to increase the buffers in zos. 

Ron

Sent from my iPhone

On Jul 25, 2013, at 1:14 PM, Ursula Braun ubr...@linux.vnet.ibm.com wrote:

 Ron,
 
 Carsten's first explanation is correct. If you see tx_errors on a
 HiperSockets interface, it usually means transmission of a packet fails
 because the receiver has currently no free receive buffer. You should
 verify first if the receiver has configured the maximum of 128 buffers
 (sysfs attribute buffer_count) for his HiperSockets device. 128 is
 nowadays the default, but older qeth driver versions run with a default
 of 16. If you see the tx_errors even though your receiver runs already
 with the maximum of 128 buffers, you either have to live with the
 autotuning mechanisms of tcp or you take actions to slow down the sender
 or to accelerate the receiver.
 
 As Alan suggested we can document this in the Device Driver book. The
 other option would be to change the current behavior of the qeth driver
 and increase probably both the tx_dropped and the tx_error counter.
 
 It is definitely not a problem to report to SuSe folks.
 
 Kind regards, Ursula Braun, Linux on System z development, IBM Germany
 
 On Thu, 2013-07-25 at 13:18 +, Ron Foster wrote:
 Carsten,
 
 Do you know where I would start looking for causes of the transmit errors on 
 Hipersockets?
 
 The error is occurring on SLES11 SP2 systems.  We are not having it on our 
 SLES10 SP4 systems.
 
 Do I need to open a problem with the SuSe folks?
 
 Thanks,
 
 Ron Foster
 
 Baldor Electric Company
 
 5711 R S Boreham Jr Street
 
 Fort Smith, AR 72901
 
 Phone:479-648-5865
 
 Fax:479-646-5440
 
 Email: ron.fos...@baldor.abb.com
 
 IM Address:rfos...@baldor.com
 
 www.baldor.com
 
 
 
 
 From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte 
 [co...@de.ibm.com]
 Sent: Thursday, July 25, 2013 7:53 AM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: TX-Errs on hipersocket interface.
 
 Alan wrote:
 Carsten, this is information that really needs to be in the Device Driver
 book, as it differs from the traditional interpretation of TX/RX counters.
 Ah, you're right - that would be accouned as dropped, not TX error. Forget
 about my
 reply then, time to look at other causes for that TX error. Sorry for the
 noise.
 
 with kind regards
 Carsten Otte
 System z firmware development / Boeblingen lab
 ---
 Every revolution was first a thought in one man's mind;
 and when the same thought occurs to another man, it is the key to that era.
 
 - Ralph Waldo Emerson, Essays: First Series, 1841
 
 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/
 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
 visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/
 
 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Performance on SLES11 SP2 guest after migration from SLES10 SP4

[Ron Foster]

Hello listers,



Over the weekend, we migrated a couple of large SAP systems from SLES10 SP4 to 
SLES11 SP2.  These are large SAP application servers (22GB).



Our SAP folks have a transaction that can be used to measure SAP response time. 
 Our servers are grouped by the applications they run.



Intermittantly one of the SAP application servers in one group will for a while 
have a response time that is about 3 times larger that the SLES10 systems.  
1600 ms  vs 500 ms.  The other sles11 system in the other application group 
will have a response time that is around 700 ms, and the others in the group 
have around 350 ms.  After a few minutes the response times on the SLES11 
systems return to normal.



I start to look at things.  I issue the vmstat command and find something.  The 
in column in the system area is all zeros.  The man page says that this is the 
number of interrupts per second.



Anyone else experience response time problems, or not get the interrupts 
information?



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

TX-Errs on hipersocket interface.

[Ron Foster]

Hello,



While investigating another problem, I did a netstat -I on our production SAP 
Linux App Servers.



To my surprise, I am getting TX-ERRS on a hipersocket interface on two of our 
systems.  The two systems have recently been converted to SLES11 SP2.  The 
hipersocket device is connected to a z/OS system where our DB2 system lives.



The hipersocket device is also used by other SAP APP servers that are SLES10 
SP4.  Those servers have zeros in the TX-ERRS column.



Any ideas on how to trouble shoot Transmit errors on a hipersocket?



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Adding space to Logical Volume Group by expanding the underlying physical disks?

[Ron Foster]

Eric,

I am a SuSe person, but I would consider using the pvmove command to copy 
physical volumes around.  The lvm physical volumes would not have to be the 
same size.  That is, you can copy directly from a smaller lvm physical volume 
to a larger lvm physical volume and would not have to expand it. (Eliminates 
step 3 from your process).

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Eric Chevalier 
[et...@tulsagrammer.com]
Sent: Friday, June 21, 2013 10:34 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Adding space to Logical Volume Group by expanding the underlying 
physical disks?

Greetings!

We run a TSM server on a virtual RHEL6 system hosted by z/VM. The TSM
databases are stored on a logical volume group that's getting close to
running out of space. An obvious solution would be to add more DASD to
the LVG. But because we're also running low on device numbers I've been
tasked with exploring the possibility of expanding the physical drives
currently used by the LVG. I've been studying a message thread from June
of last year titled Extending a DASD partition which seems to suggest
that this approach is possible. The approach I'm thinking of is to

  * Allocate a single new drive much larger than the existing LVG
physical drives.
  * Copy physical drive #1 to the new drive.
  * Redefine drive #1 to be larger
  * Copy physical drive #2 to the expanded drive #1
  * Repeat with drives #3 through #n
  * Delete drive #n

With this approach we only need to allocate one additional device
number, and only for a limited period of time. Does this approach sound
reasonable? There's one issue that I can think of, though: I'll be
starting out with a set of devices allocated to the LVG: /dev/dasdc
through /dev/dasdj. When I'm finished, I'll have dasdd through dasdk.
It's not clear to me where the assignment of devices to the LVG is kept
and whether it could easily be hand-edited.

I'm open to any comments or suggestions you folks might have!

Eric

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Adding space to Logical Volume Group by expanding the underlying physical disks?

[Ron Foster]

dasdfmt to format the dasd.
fdasd to partition it
pvmove to move the data.  

Yes it have done this and it has worked.

One caveat, sometimes you cannot move the entire physical volume with one 
command.  You have to move it a logical volume at a time.  But we can cross 
that bridge when you get there.


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Eric Chevalier 
[et...@tulsagrammer.com]
Sent: Friday, June 21, 2013 11:19 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Adding space to Logical Volume Group by expanding the underlying 
physical disks?

Ron,

Thank you very much for that suggestion. It looks like it might be
exactly what I want! I'm assuming I still need to fdasd to perform the
intial format of the new drive, then just pvmove? If the answer is
yes, you've just made my day!

Eric

On 6/21/13 11:03 AM, Ron Foster wrote:
 Eric,

 I am a SuSe person, but I would consider using the pvmove command to copy 
 physical volumes around.  The lvm physical volumes would not have to be the 
 same size.  That is, you can copy directly from a smaller lvm physical volume 
 to a larger lvm physical volume and would not have to expand it. (Eliminates 
 step 3 from your process).

 Ron Foster

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Appropriate hipersocket MFS size for use with SAP Apps Servers

[Ron Foster]

Rob,

The traffic is between our Sap application servers running under zvm.  

During the latest conference call, the TCP ip folks determined that the SAP 
traffic in question generally has packets less than 8k.  So changing the frame 
size would not help.

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Rob van der Heij 
[rvdh...@gmail.com]
Sent: Saturday, June 15, 2013 2:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Appropriate hipersocket MFS size for use with SAP Apps Servers

On 13 June 2013 23:58, Ron Foster ron.fos...@baldor.abb.com wrote:

3. One of the things that the TCP IP folks want us to do on the hardware
 side is to increase the maximum frame size to 64k. for this hipersocket.

 4. This would normally increase the MTU size to 56k for the hipersocket.

 5. If I remember properly the 56k value would exceed the SAP recommended
 MTU size of 8k.

 6. The IBM z/os TCP/IP support says that the MTU size could be forced to
 8k.

 Anyone have any experience in forcing an MTU to 8k like this?  Any
 unwelcome side effects?


The queuing that the MVS folks observe is likely in another place than the
MTU size, at least there are other knobs to work first. If you only
increase the MSS and MTU to the max, you may end up with throughput
seriously lower than what you achieve now. I suppose the massive volumes
you talk about is for the shared NFS space between the two?

I can dig up some more questions for you when I get through the rest of my
pending inbox (I hate when you all start these threads when I'm offline ;-)

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Appropriate hipersocket MFS size for use with SAP Apps Servers

[Ron Foster]

Hello listers,



We have a bunch of SAP application servers running under z/vm. They are all 
pointed at the same z/os 1.13 system. There are several DB2s running on this 
z/OS system.  All the Apps servers are using the same hipersocket chpid to 
communicate to the z/os system the same hipersocket chipid. Since going to z/OS 
1.13, we are experiencing storage creep in our TCPIP address space.



This hipersocket is using a 8k MTU size.  I believe this to be the SAP 
recommended size.



Our z/os support folks are being told by their support folks that they would 
like us to increase the MTU size from 8k to something larger.



Anyone have any experience running SAP apps servers under z/vm with a larger 
than 8k MTU size?



Thanks,

Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Appropriate hipersocket MFS size for use with SAP Apps Servers

[Ron Foster]

Alan,

I went to talk to the z/os guy to get a better understanding of what the TCP IP 
folks are wanting done.

I now have a better understanding of what is going on.

1. We have so much data flowing through the hipersocket chipid that we are 
experiencing queueing in the hipersocket.  (This is on a z196.)

2. It appears that something, either hipersocket or TCPIP, is not reacting well 
to that queueing.  It appears that is what is causing the storage creep.

3. One of the things that the TCP IP folks want us to do on the hardware side 
is to increase the maximum frame size to 64k. for this hipersocket.

4. This would normally increase the MTU size to 56k for the hipersocket.

5. If I remember properly the 56k value would exceed the SAP recommended MTU 
size of 8k.

6. The IBM z/os TCP/IP support says that the MTU size could be forced to 8k.

Anyone have any experience in forcing an MTU to 8k like this?  Any unwelcome 
side effects?

Thanks,
Ron 


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Alan Altmark 
[alan_altm...@us.ibm.com]
Sent: Thursday, June 13, 2013 3:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Appropriate hipersocket MFS size for use with SAP Apps Servers

On Thursday, 06/13/2013 at 03:29 EDT, Ron Foster
ron.fos...@baldor.abb.com wrote:
 We have a bunch of SAP application servers running under z/vm. They are
all
 pointed at the same z/os 1.13 system. There are several DB2s running on
this
 z/OS system.  All the Apps servers are using the same hipersocket chpid
to
 communicate to the z/os system the same hipersocket chipid. Since going
to z/OS
 1.13, we are experiencing storage creep in our TCPIP address space.

 This hipersocket is using a 8k MTU size.  I believe this to be the SAP
 recommended size.

 Our z/os support folks are being told by their support folks that they
would
 like us to increase the MTU size from 8k to something larger.

That sounds strange, to say the least.  What logic do they give to support
the conclusion that a larger MTU will prevent storage creep?  Large MTU or
small, the path through the stack should be the same.  If you didn't have
storage creep on the earlier release with an 8K MTU, you shouldn't have it
now.

Alan Altmark

Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Is sitar available for sles11 SP2

[Ron Foster]

Hello Listers,



Many moons ago we found in a redbook the mention of a package called sitar.  It 
provided a wealth of information about a Linux system.  We incorporated sitar 
output into our system documentation.



We are now in the process of building our SLES11 SP2 environment.  It appears 
that sitar is no longer available.



Does anyone know if there is a replacement available?



Thanks,

Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: devmap_mknod.sh and /dev/ram3 on sles11 sp2

[Ron Foster]

Thanks for the information.  
Ron

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Mark Post 
[mp...@suse.com]
Sent: Monday, October 29, 2012 6:08 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: devmap_mknod.sh and /dev/ram3 on sles11 sp2

 On 10/18/2012 at 09:43 AM, Ron Foster ron.fos...@baldor.abb.com wrote:
 We are starting a journey from SLES10 SP4 to SLES11 SP2.  Part of the journey
 is building a a SLES11 enironment with certain capabilities.  One of those
 capabilities is the ability to boot the install CDs and then perform a
 FDR/upstream restore from the environment provided by the install CDs.  (I
 know that we could boot another Linux system and reach out and do a restore,
 but this procedure is for when that scenario will not work.)

 Anyway,  our procedure calls for executing a devmap_mknod.sh script.  It
 appears that that script is not available in a SLES11 sp2 environment.  It
 also appears that /dev/ram3 is not available.

 Any ideas whether devmap_mknod.sh is necessary.  Also about the ram3
 ramdisk.

I would have to say that devmap_mknod.sh is not necessary.  That was from 
device-mapper 1.x, and it talks about devfs, the LVM1 control device and things 
like that.  /dev/mapper/control doesn't even exist in LVM2.

I suspect the reason you're not seeing things like /dev/ram3 is because on 
System z, even the rescue environment needs to be fetched from a network 
installation server, just like the installer does.  Instead of the initrd 
integrating the installer code into the running system, it needs to integrate 
the rescue system code into the running system.

I'm not sure that you can do what you want to do with the tools you're using.  
At least, not the way you seem to be trying to use them.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

devmap_mknod.sh and /dev/ram3 on sles11 sp2

[Ron Foster]

Hello listers,



We are starting a journey from SLES10 SP4 to SLES11 SP2.  Part of the journey 
is building a a SLES11 enironment with certain capabilities.  One of those 
capabilities is the ability to boot the install CDs and then perform a 
FDR/upstream restore from the environment provided by the install CDs.  (I know 
that we could boot another Linux system and reach out and do a restore, but 
this procedure is for when that scenario will not work.)



Anyway,  our procedure calls for executing a devmap_mknod.sh script.  It 
appears that that script is not available in a SLES11 sp2 environment.  It also 
appears that /dev/ram3 is not available.



Any ideas whether devmap_mknod.sh is necessary.  Also about the ram3 ramdisk.



Thanks,

Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Can't Connect to Linux LPAR

[Ron Foster]

Dave,

Do you have access to the ASCII console for that LPAR. 

(I don't know if SLES11 SP1 has the entry in /etc/inittab that activates it. It 
would make life simpler.)

I don't have any LPARS running SLES11 SP1, but I do have 3 running SLES10 SP4.

The line on my SLES10 system looks like this:

2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 linux 

I think the important part is the ttyS1.

(To get access, you could try the echo  command to append the necessary line 
on /etc/inittab).

Meanwhile,
Do you get something that looks like this when you boot..
eth0  name: IBM OSA Express Network card (0.0.0700)
eth0  IP address: 10.80.200.126/24
eth0  is up
(This is from a SLES11 SP1 linux guest talking to a z/vm vswitch.  A OSA 
adapter looks similar.)  A SLES10 OSA looks like this.
eth3  configuration: qeth-bus-ccw-0.0.a104
eth3  IP address: 10.80.200.224/24
eth3 done



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of David Stuart 
[david.stu...@ventura.org]
Sent: Monday, October 01, 2012 3:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Can't Connect to Linux LPAR

Afternoon,

/set newbie=on

I am running SuSE 11 SP 1 in a  LPAR (Yesm an LPAR, no z/VM anywhere on the 
horizon).

This LPAR was set up as a proof of concept, but management could never decide 
on what concepts to prove, so it basically sits idle all the time.

I went to sign on this afternoon to check the logs, etc., and I couldn't 
connect to the System.  All connections time out.  A ping times out, as well.  
So I logged on via the HMC - Operating System Messages.  There were some 
errors, so I performed a SHUTDOWN -R NOW, and it shut down cleanly, and 
restarted.  Everything appears to have restarted successfully, but I still 
can't connect.  Pings, both in from my PC and out from the Linux system, time 
out.  An ifconfig eth0 shows the network interface to be configured with the 
correct ip address and net mask.

So, I am puzzled, and somewhat lost on what to do next.  I know it's not a 
problem with the OSA Card, as it is shared with other LPARs, and is working 
just fine.

All ideas and suggestions welcomed.  But please keep in mind, the only access I 
have is via the HMC - Operating System Messages, which means no cut  paste, 
etc.


Thanks,
Dave




Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Can't Connect to Linux LPAR

[Ron Foster]

David,

Going along with what Robert said, you can try pinging yourself(157.145.4.160) 
to see if the network is running.  If you don't know what your gateway is, then 
you can find it by looking at /etc/sysconfig/network/routes.

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of David Stuart 
[david.stu...@ventura.org]
Sent: Monday, October 01, 2012 4:48 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Can't Connect to Linux LPAR

Afternoon Ron,

I get a message at the very end of the boot cycle that says:

Welcome to SUSE Linux ... Kernal 2.6.32.36-0.5-default (ttys0).

And for eth0, I see:

eth0name: OSA Express Network card (0.0.0530)
eth0IP address: 157.145.4.160/22  followed by a SuSEfirewall2 
not active message and then
eth0..done

I never see a 'is up' message.

0530 is the correct device base address for the OSA and the IP address is 
correct.

Could it be so simple that what i need to do is a ifup command?  If so, why.  
It used to works...


Thanks,
Dave


Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org



 Ron Foster ron.fos...@baldor.abb.com 10/1/2012 2:28 PM 
Dave,

Do you have access to the ASCII console for that LPAR.

(I don't know if SLES11 SP1 has the entry in /etc/inittab that activates it. It 
would make life simpler.)

I don't have any LPARS running SLES11 SP1, but I do have 3 running SLES10 SP4.

The line on my SLES10 system looks like this:

2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 linux

I think the important part is the ttyS1.

(To get access, you could try the echo  command to append the necessary line 
on /etc/inittab).

Meanwhile,
Do you get something that looks like this when you boot..
eth0  name: IBM OSA Express Network card (0.0.0700)
eth0  IP address: 10.80.200.126/24
eth0  is up
(This is from a SLES11 SP1 linux guest talking to a z/vm vswitch.  A OSA 
adapter looks similar.)  A SLES10 OSA looks like this.
eth3  configuration: qeth-bus-ccw-0.0.a104
eth3  IP address: 10.80.200.224/24
eth3 done



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of David Stuart 
[david.stu...@ventura.org]
Sent: Monday, October 01, 2012 3:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Can't Connect to Linux LPAR

Afternoon,

/set newbie=on

I am running SuSE 11 SP 1 in a  LPAR (Yesm an LPAR, no z/VM anywhere on the 
horizon).

This LPAR was set up as a proof of concept, but management could never decide 
on what concepts to prove, so it basically sits idle all the time.

I went to sign on this afternoon to check the logs, etc., and I couldn't 
connect to the System.  All connections time out.  A ping times out, as well.  
So I logged on via the HMC - Operating System Messages.  There were some 
errors, so I performed a SHUTDOWN -R NOW, and it shut down cleanly, and 
restarted.  Everything appears to have restarted successfully, but I still 
can't connect.  Pings, both in from my PC and out from the Linux system, time 
out.  An ifconfig eth0 shows the network interface to be configured with the 
correct ip address and net mask.

So, I am puzzled, and somewhat lost on what to do next.  I know it's not a 
problem with the OSA Card, as it is shared with other LPARs, and is working 
just fine.

All ideas and suggestions welcomed.  But please keep in mind, the only access I 
have is via the HMC - Operating System Messages, which means no cut  paste, 
etc.


Thanks,
Dave




Dave Stuart
Prin. Info. Systems Support Analyst
County of Ventura, CA
805-662-6731
david.stu...@ventura.org


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send

Re: What is the maximum amount of memory supported by SLES10

[Ron Foster]

Everyone,

Thanks for the good information.

We currently have a 100GB Linux guest.  

We are furiously applying fixes to SAP to lessen the need for storage. 

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Mark Post 
[mp...@suse.com]
Sent: Wednesday, August 15, 2012 1:10 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: What is the maximum amount of memory supported by SLES10

 On 8/10/2012 at 04:58 PM, Ron Foster ron.fos...@baldor.abb.com wrote:
 We are trying to bring up a new SAP module.  The SAP support folks are
 requesting a 100 GB virtual machine be created before they will work on the
 problem.



 Would this be supported?

Yes.  The maximum supported memory size is currently 256GB, which is the same 
as z/VM's maximum.  The Linux kernel itself will support 4TB, but an LPAR can 
only go up to 1TB.  I don't know if z/VM has a limit on the size of any 
individual guest or not.  I know you guys run some Linux in LPARs, but that 
isn't much help if you can't assign that much memory to an LPAR for testing.  
(I don't know too many people who have 1TB of paid-for-but-unused memory on a 
System z box.)


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: What is the maximum amount of memory supported by SLES10

[Ron Foster]

Bob,
Thanks for the info.
Ron


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Bob McCarthy 
[bob.mccar...@custserv.com]
Sent: Monday, August 13, 2012 7:20 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: What is the maximum amount of memory supported by SLES10

Ron,
   I don't know what the maximum amount of memory supported by SLES10 is, but I 
currently have a SLES10 guest running with 116gb of virtual memory for over two 
years. It runs on a z196 with a total memory size of 172gb.
   Bob

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Foster
Sent: Friday, August 10, 2012 4:59 PM
To: LINUX-390@VM.MARIST.EDU
Subject: What is the maximum amount of memory supported by SLES10

Hello,



We are trying to bring up a new SAP module.  The SAP support folks are 
requesting a 100 GB virtual machine be created before they will work on the 
problem.



Would this be supported?



Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

What is the maximum amount of memory supported by SLES10

[Ron Foster]

Hello,



We are trying to bring up a new SAP module.  The SAP support folks are 
requesting a 100 GB virtual machine be created before they will work on the 
problem.



Would this be supported?



Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Issues with persistence of Drivers

[Ron Foster]

Ben,

But yast does work if you have access to the integrated ASCII terminal in the 
HMC, and have set up /etc/inittab to use it.

Ron

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ben Duncan 
[b...@linux4ms.net]
Sent: Tuesday, July 03, 2012 7:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issues with persistence of Drivers

I have access to the guest via ssh, but that has to be set up manually
(ipconfig , route ..etc) every time the
system gets rebooted.

BLowing away and resetting, is not an option on the interface since I
have 48 of these servers we will try AGAIN
to move to the z114 sunday.

Nor is yast, since It doesnt' work on the z/VM 3270 terminal ; ...

Ben Duncan - Business Network Solutions, Inc. 336 Elton Road  Jackson
MS, 39212
Never attribute to malice, that which can be adequately explained by
stupidity
- Hanlon's Razor


  Original Message 
 Subject: Re: Issues with persistence of Drivers
 From: Mark Post mp...@suse.com
 Date: Mon, July 02, 2012 3:29 pm
 To: LINUX-390@VM.MARIST.EDU


  On 7/2/2012 at 04:15 PM, Rick Troth r...@casita.net wrote:
  You
  probably don't NEED
  access to the VM system console.  (And it would not tell you much
  about this guest anyway.)

 Actually he does, since I'm going to suggest deleting and redefining hist NIC.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Issues with persistence of Drivers

[Ron Foster]

Are you using vswitch or dedicated OSA adapters?
What does the output of a #cp q OSA look like?
Are you getting any errors when you logon the guest?

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ben Duncan 
[b...@linux4ms.net]
Sent: Monday, July 02, 2012 12:09 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Issues with persistence of Drivers

Ok, This is my first post to this group so bear with me. I have been
following this group, since I am the
local LINUX expert for the STATE of MS, ITS and as such a GOOD deal
involves zLinux on the mainframe.

I am having issues with a test of migration from a Z9 machine to a Z114.
Both machines have z/vm version 5.4.
We can get the image over to the Z114 with it up and running, but are
having to force the network up on the Z114 with the znetconf -A command.

THese are devices 0600, 0601, 0603 1731/01 when on the Z9 as well as the
Z114.

The network driver and network works fine on the Z9.

After rebooting the Z114 zLinux, the network device goes away.

We are experiencing the same thing with the multi-path drivers.

Any one got any ideas ?


Thanks ..


Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS,
39212
Never attribute to malice, that which can be adequately explained by
stupidity
- Hanlon's Razor


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Issues with persistence of Drivers

[Ron Foster]

A vmcp q v osa would work.

Also, are you the one who logs on the quest.  That is do you have the authority 
to shutdown zlinux and logoff the guest.  Then logon the guest and ipl the 
Linux guest?

If so, what kind of messages are you getting when you first logon to the Linux 
guest and before you ipl the Linux image?  Just looking to see if you have full 
access to the devices you need.

Also, are you using vswitches or dedicated OSAs?

If vswitch, layer2 or layer3.

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ben Duncan 
[b...@linux4ms.net]
Sent: Monday, July 02, 2012 1:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issues with persistence of Drivers

Opps sorry. Suse 11.1 zLinux

uname -ran output: Linux sup00039 2.6.32.46-0.3-default #1 SMP
2011-09-29 17:49:31 +0200 s390x s390x s390x GNU/Linux

cat /etc/SuSE-release :

SUSE Linux Enterprise Server 11 (s390x)
VERSION = 11
PATCHLEVEL = 1

Sorry, I cannot give a vm CP query since I am not allowed zvm access.


after doing znetconf -A:

sup00039:/etc/udev/rules.d # znetconf -c
Device IDs TypeCard Type  CHPID Drv. Name
State

0.0.0600,0.0.0601,0.0.0602 1731/01 GuestLAN QDIO 01 qeth eth0
online

/etc/sysconfig/network/ifcfg-eth0 file:

BOOTPROTO='static'
IPADDR='10.12.9.114'
NETMASK='255.255.255.0'
BROADCAST='10.12.9.144'
STARTMODE='onboot'
NAME='OSA Express Network card (0.0.0600)'


I even delete the /etc/udev/rules.d/70-persistent-net.rules to force a
rebuild
but that does seem to help ... it looks like this:

# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# S/390 qeth device at 0.0.0600
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it,as long as you keep each rule on a single line.
# S/390 qeth device at 0.0.0600
SUBSYSTEM==net, ACTION==add, DRIVERS==qeth, KERNELS==0.0.0600,
ATTR{type}==1, KERNEL==eth*, NAME=eth0

supztest:/var/log # vmcp q 0600
OSA  0600 ON NIC  0600  UNIT 000 SUBCHANNEL = 0006
 0600 DEVTYPE OSA CHPID 01 OSD
 0600 MAC 02-08-01-00-00-03 CURRENT
 0600 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE

Anything else I need to supply ?


MY Guess is there is a config file that HOLDS the MAC address that is
not getting changed
and fubaring the whole thing


Thanks ..


Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS,
39212
Never attribute to malice, that which can be adequately explained by
stupidity
- Hanlon's Razor




 Original Message 
Subject: Re: Issues with persistence of Drivers
From: Mark Post mp...@suse.com
Date: Mon, July 02, 2012 12:18 pm
To: LINUX-390@VM.MARIST.EDU


 On 7/2/2012 at 01:09 PM, Ben Duncan b...@linux4ms.net wrote:
 The network driver and network works fine on the Z9.

 After rebooting the Z114 zLinux, the network device goes away.

 We are experiencing the same thing with the multi-path drivers.

Distribution? Version? Interface definition file(s)? CP QUERY output for
NIC? Etc.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Issues with persistence of Drivers

[Ron Foster]

The waiting for mandatory device message seems to indicate that a qeth device 
is not getting initialized.  Have you carefully looked at the 2 or 3 screens 
that preceed the waiting for mandatory device message.

There might be a message that might be useful.

Also, you mentioned having to put the gateway route back in.  Do you have an 
example of what the routes (/etc/sysconfig/network/routes) looks like before 
and after you put the GW route in.

Are the interfaces getting renamed?  Like eth1 becomes eth0, but your route is 
over eth1?

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ben Duncan 
[b...@linux4ms.net]
Sent: Monday, July 02, 2012 2:16 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issues with persistence of Drivers

Output of vmcp q v osa:
 vmcp q v osa
OSA  0600 ON NIC  0600  UNIT 000 SUBCHANNEL = 0006
 0600 DEVTYPE OSA CHPID 01 OSD
 0600 MAC 02-08-01-00-00-03 CURRENT
 0600 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE
OSA  0601 ON NIC  0600  UNIT 001 SUBCHANNEL = 0007
 0601 DEVTYPE OSA CHPID 01 OSD
 0601 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE
OSA  0602 ON NIC  0600  UNIT 002 SUBCHANNEL = 0008
 0602 DEVTYPE OSA CHPID 01 OSD
 0602 QDIO ACTIVE QIOASSIST-ELIGIBLE
 0602
 0602 INP + 01 IOCNT = 1139  ADP = 012 PROG = 000 UNAVAIL = 116
 0602  BYTES = 00023C08
 0602 OUT + 01 IOCNT =   ADP = 000 PROG = 000 UNAVAIL = 128
 0602  BYTES = 
 0602 OUT + 02 IOCNT =   ADP = 000 PROG = 000 UNAVAIL = 128
 0602  BYTES = 
 0602 OUT + 03 IOCNT = 0816  ADP = 000 PROG = 128 UNAVAIL = 000
 0602  BYTES = 0003BD67
 0602 OUT + 04 IOCNT =   ADP = 000 PROG = 000 UNAVAIL = 128
 0602  BYTES = 

It is a vswitch at Layer 3.

Yes, I have root access, but do not have a z/vm console or access.
When rebooting, it hangs on:
Waiting for Mandatory device etho __NSC__ anc counts down from 30.
We than have to do a znetconf -A then add the GW route in.

Having been a member of the kernel dev team in the past (X86 only)
and having dealt with Linux since 1994, this tells me some config file
did
not get the NOTICE OF UPDATE for the z/vm devices.

I dunno, and will profess all this z/VM layer stuff is new to me, But I
like it ..


Ben Duncan - Business Network Solutions, Inc. 336 Elton Road  Jackson
MS, 39212
Never attribute to malice, that which can be adequately explained by
stupidity
- Hanlon's Razor


  Original Message 
 Subject: Re: Issues with persistence of Drivers
 From: Ron Foster ron.fos...@baldor.abb.com
 Date: Mon, July 02, 2012 1:48 pm
 To: LINUX-390@VM.MARIST.EDU


 A vmcp q v osa would work.

 Also, are you the one who logs on the quest.  That is do you have the 
 authority to shutdown zlinux and logoff the guest.  Then logon the guest and 
 ipl the Linux guest?

 If so, what kind of messages are you getting when you first logon to the 
 Linux guest and before you ipl the Linux image?  Just looking to see if you 
 have full access to the devices you need.

 Also, are you using vswitches or dedicated OSAs?

 If vswitch, layer2 or layer3.

 Ron Foster

 Baldor Electric Company

 5711 R S Boreham Jr Street

 Fort Smith, AR 72901

 Phone:479-648-5865

 Fax:479-646-5440

 Email: ron.fos...@baldor.abb.com

 www.baldor.com



 
 From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Ben Duncan 
 [b...@linux4ms.net]
 Sent: Monday, July 02, 2012 1:30 PM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: Issues with persistence of Drivers

 Opps sorry. Suse 11.1 zLinux

 uname -ran output: Linux sup00039 2.6.32.46-0.3-default #1 SMP
 2011-09-29 17:49:31 +0200 s390x s390x s390x GNU/Linux

 cat /etc/SuSE-release :

 SUSE Linux Enterprise Server 11 (s390x)
 VERSION = 11
 PATCHLEVEL = 1

 Sorry, I cannot give a vm CP query since I am not allowed zvm access.


 after doing znetconf -A:

 sup00039:/etc/udev/rules.d # znetconf -c
 Device IDs TypeCard Type  CHPID Drv. Name
 State
 
 0.0.0600,0.0.0601,0.0.0602 1731/01 GuestLAN QDIO 01 qeth eth0
 online

 /etc/sysconfig/network/ifcfg-eth0 file:

 BOOTPROTO='static'
 IPADDR='10.12.9.114'
 NETMASK='255.255.255.0'
 BROADCAST='10.12.9.144'
 STARTMODE='onboot'
 NAME='OSA Express Network card (0.0.0600)'


 I even delete the /etc/udev/rules.d/70-persistent-net.rules to force a
 rebuild
 but that does seem to help ... it looks like this:

 # This file was automatically generated by the /lib/udev/write_net_rules
 # program run by the persistent-net-generator.rules rules file

Re: Corruption of nfs mounted SAP log files

[Ron Foster]

Mark,

We have an SR open with Novell, and a SAP OSS message open.

The Novell SR number is SR#10772685131.

(And may I say that Paul Evans, the Novell person handling this, has done an 
excellent job in working with developers to identify the kernel level (sles10 
sp4 .91) that this problem behavior started happening in as well as the change 
number (#709369) that is suspected to cause the problem.)

For the benefit of any SAP users out there:
The change # is a change to NFS behavior, I don't know if or when the SLES11 
kernel would incorporate this change#. 

Another tidbit for any SAP users out there::
Also, according to the information Paul and the developers found  is that the 
file corruption could have been happening before this change number.  The 
corruption was not as noticable in that you occasionally had missing lines 
instead of hex nulls that you get after the change.  So unless you really know 
the structure of these particular log files, you might never know that you have 
been having a log file problem.

Anyway, using the information given by Paul and the developers that he worked 
with, we are now working with SAP to find a long term solution.

So if there are any SAP users out there, we really would like to know if the 
activity in your system is such that your ALOG, and ULOG files get written to 
at the same time by multiple Linux guests, and how you keep the corruption from 
happening (nfs levels, kernel levels, nfs mount options.)

Right now we have resorted to using the noac nfs option, but that slows things 
way down.
It has been suggested to migrate to the SLES10 SP4 .89 kernel.  It does not 
have the offending change number.  (This is not a long term solution.)
The SAP folks say that going the NFSv4 will fix the problem, but our latest 
corruption occured when we were at NFSv4.  (The SAP basis folks had us move 
back to NFSv3 after the latest problem.)
There also has been a suggestion to go away to a local dir/trans instead of a 
shared dir/trans.

Any comments or suggestions would be greatly appreciated.


Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Mark Post 
[mp...@suse.com]
Sent: Wednesday, June 27, 2012 9:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Corruption of nfs mounted SAP log files

 On 6/14/2012 at 10:25 AM, Ron Foster ron.fos...@baldor.abb.com wrote:
 So anyone running SAP on linux for zSeries care to share how their
 /usr/sap/trans is set up.  Any special NFS mount options, etc.

Ron, do you have a service request opened on this problem?  If so, with whom?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: DB2 Connect client, any sense in running server?

[Ron Foster]

Thomas,

We are an SAP shop.  Years ago, we ran the full DB2 connect client on each SAP 
application server.  This would be a real pail at times when DB2 maintenance 
came along.  It was also a consumed quite a bit of disk space on the server.  
Also there was the matter of the configuration that had to be co-ordinated with 
the SAP folks.

SAP has since migrated to what was called a 'thin client.'  (I can find the 
real name if you want.)  One of the advantages of the thin client was that to 
install, you basically just untarred a directory structure and then pointed 
your PATH to it.  It is so simple that the the SAP admin folks took over the 
maintenance of DB2 connect.  As far as configuration goes, sometimes we have to 
make an entry in a INI file, but most of the time we do not.

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Tom Ambros 
[thomas_amb...@keybank.com]
Sent: Thursday, June 21, 2012 9:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: DB2 Connect client, any sense in running server?

We're running the DB2 Connect client at the various distributed machines
that require it.  Is there any sense in running the DB2 Connect server
product in a Linux on System Z guest to serve the other guests or the
distributed machines removing the client from those distributed devices?

I am of the impression that the only purpose for the server, at this
point, is to perform two-factor commit under certain circumstances that we
do not encounter here.

Do the advantages of running the client wash out when Linux on System Z
for a set of guests becomes the configuration?

Thank you for sharing your experience and advice.

Thomas Ambros
Operating Systems and Connectivity Engineering
518-436-6433

This communication may contain privileged and/or confidential information. It 
is intended solely for the use of the addressee. If you are not the intended 
recipient, you are strictly prohibited from disclosing, copying, distributing 
or using any of this information. If you received this communication in error, 
please contact the sender immediately and destroy the material in its entirety, 
whether electronic or hard copy. This communication may contain nonpublic 
personal information about consumers subject to the restrictions of the 
Gramm-Leach-Bliley Act. You may not directly or indirectly reuse or redisclose 
such information for any purpose other than to provide the services for which 
you are receiving the information.

127 Public Square, Cleveland, OH 44114
If you prefer not to receive future e-mail offers for products or services from 
Key
send an e-mail to mailto:dnereque...@key.com with 'No Promotional E-mails' in 
the
SUBJECT line.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Network card speed

[Ron Foster]

Victor,

How do the guests attach to this OSA card?
Is it through a VSWITCH?

Also, the network folks who control the switch that the OSA card is attached to 
should be able to tell
you the speed at which the connection from the switch to the OSA adapter is 
operating.

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Victor Echavarry 
Diaz [vechava...@evertecinc.com]
Sent: Wednesday, June 20, 2012 10:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Network card speed

Ursula:
This is my output
# lsqeth eth0
Device name : eth0
-
card_type   : GuestLAN QDIO
cdev0   : 0.0.0360
cdev1   : 0.0.0361
cdev2   : 0.0.0362
chpid   : 23
online  : 1
portno  : 1
route4  : no
route6  : no
checksumming: sw checksumming
state   : UP (LAN ONLINE)
priority_queueing   : always queue 2
fake_ll : 0
fake_broadcast  : 0
buffer_count: 16
add_hhlen   : 0
layer2  : 0
large_send  : no

Regards,
Victor Echavarry
System Programmer
Technology Systems  Operations Division
EVERTEC



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ursula 
Braun
Sent: Wednesday, June 20, 2012 11:14 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Network card speed

On Wed, 2012-06-20 at 09:15 -0400, Victor Echavarry Diaz wrote:
 Ursula:
 Which tool we have for SLES 10? Our majority of servers are on SLES 10.

Victor,

for SLES10 (and SLES11) you can derive the maximum speed from the
card_type line in the output of
lsqeth ethx
Once OSA-devices are online, it displays one of these values
OSD_100
OSD_1000
OSD_10GIG

Regards, Ursula Braun, IBM Germany

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Network card speed

[Ron Foster]

Victor,

The output you included showed that Linux thinks this is Guestlan QDIO 
connection.  I always thought that between the Linux guests and the VSWITCH, 
you used the QDIO protocol.  And from the SHARE presentations that I have 
attended, that if you have settings like correct MTU sizes, that this protocol 
is very fast.  (I don't have a presentation handy at the moment, but it think I 
remember that the speed that this protocol can operate at is much faster than 
the OSA adapter can send it out over the wire.)

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Victor Echavarry 
Diaz [vechava...@evertecinc.com]
Sent: Wednesday, June 20, 2012 10:56 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Network card speed

Ron:
Is through VSWITCH. The OSA is Gb speed. The issue is we use velocity to 
monitor it show the guest with 100 Mbs. You go to the SLES 11 and with ethtool 
show 1Gb card speed. So, we need a utility to confirm which is the real speed 
inside the guest.
Regards,
Victor Echavarry
System Programmer
Technology Systems  Operations Division
EVERTEC



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Foster
Sent: Wednesday, June 20, 2012 11:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Network card speed

Victor,

How do the guests attach to this OSA card?
Is it through a VSWITCH?

Also, the network folks who control the switch that the OSA card is attached to 
should be able to tell
you the speed at which the connection from the switch to the OSA adapter is 
operating.

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Victor Echavarry 
Diaz [vechava...@evertecinc.com]
Sent: Wednesday, June 20, 2012 10:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Network card speed

Ursula:
This is my output
# lsqeth eth0
Device name : eth0
-
card_type   : GuestLAN QDIO
cdev0   : 0.0.0360
cdev1   : 0.0.0361
cdev2   : 0.0.0362
chpid   : 23
online  : 1
portno  : 1
route4  : no
route6  : no
checksumming: sw checksumming
state   : UP (LAN ONLINE)
priority_queueing   : always queue 2
fake_ll : 0
fake_broadcast  : 0
buffer_count: 16
add_hhlen   : 0
layer2  : 0
large_send  : no

Regards,
Victor Echavarry
System Programmer
Technology Systems  Operations Division
EVERTEC



-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ursula 
Braun
Sent: Wednesday, June 20, 2012 11:14 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Network card speed

On Wed, 2012-06-20 at 09:15 -0400, Victor Echavarry Diaz wrote:
 Ursula:
 Which tool we have for SLES 10? Our majority of servers are on SLES 10.

Victor,

for SLES10 (and SLES11) you can derive the maximum speed from the
card_type line in the output of
lsqeth ethx
Once OSA-devices are online, it displays one of these values
OSD_100
OSD_1000
OSD_10GIG

Regards, Ursula Braun, IBM Germany

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/



-
CONFIDENTIALITY NOTE: This email communication and its attachments
contain information that are proprietary and confidential to
EVERTEC, INC., its affiliates or its clients.  They may not be
disclosed, distributed, used, copied or modified in any way without
EVERTEC, Inc.’s authorization. If you are not the intended
recipient

Corruption of nfs mounted SAP log files

[Ron Foster]

Hello listers,



This is part of a continuing story related to some SAP related log files.  I 
thought I would bring it up one more time to see if the folks running SAP might 
have any additional input.



We have a central NFS server for our SAP systems.  It is currently running 
SLES10 SP4.  (There are some dependencies between SLES11 SP2 and SAP, that have 
to be addressed before we can get up to SLES11 SP2.)  The problem we are having 
is with a nfs mount called /usr/sap/trans.  This mount is used to move programs 
between systems in a SAP landscape.  For example DEVQAProduction.  In order 
for this movement of programs to take place, multiple systems must have this 
file system mounted read write at the same time.  As a matter of fact, our 
workload has come to the point where it might be that we are writing to a 
particular log file at the same file from multiple systems.



This has been working fine for years using NFSV3 mounts.  However, a 
combination of SAP maintenance, and SLES10 SP4 broke this mechanism.  
Intermittantly we started getting corrupted records in our ALOG (sap activity 
log) file.  We did some research and found that for NFSV3 mounts on Linux, the 
nfs noac parameter was suggested.  This parameter disables NFS buffering.  So 
we implemented this parameter on our /usr/sap/trans mounts.  The corrupted 
records were fixed.  But this exacted a high performance penalty.



We did some more research, SAP recommends that NFSv4 mounts be used.  So we 
undertook a project to set up NFSv4 mounts.  One night, we implemented NFSv4 
mounts on our production system.  We removed noac, and added no_subtree_check, 
and nohide NFS options.  By 11am the next day, we had so may ALOG corruptions 
that it was decided to rip out the NFSv4 mounts and implement NFSv3 mounts in 
our production, DEV, and QA system DURING THE DAY.



Looking at the various log files, we can see that our DEV and QA systems do not 
appear to have a problem writing to this log file.  It appears that the problem 
occurs when DEV or QA systems are writing to the log file at about the same 
time that production system is writing to the log file.  We cannot tell for 
sure, because the records are corrupted.  Be we can see from other logs, a 
process from production was run during the period that the records were 
corrupted in the log file, and that process from production should have written 
records to the log file.



The corruption show up as ^@ characters.  I think that these characters are 
hexadecimal zeros.



So anyone running SAP on linux for zSeries care to share how their 
/usr/sap/trans is set up.  Any special NFS mount options, etc.



Thanks,

Ron



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.commailto:ron.fos...@baldor.abb.com

www.baldor.comhttp://www.baldor.com/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

NFS mounted filesystem corruption problems

[Ron Foster at Baldor-IS]

Hello listers,

We have a central NFS server that has several clients.  This NFS server
has a filesystem used to contain SAP transports.  (For the SAP folks,
this is our /usr/sap/trans filesystem.)  To make a long story short,
these transports are what SAP uses to move program and database changes
from one SAP system to another.

We are having a situation where where some of the log files associated
with the transport system are getting corrupted.  We are not experts on
this SAP supplied transport system, but it appears that frequently when
we try to transport some changes from our Linux system that runs the
SAP ECC dev/test systems up to the next higher level, that sometimes a
couple of the log files, the ALOG and ULOG get a bunch of ^@ records in
the file.  This causes the SAP transport system to have problems.

At this point, I am trying to figure out whether this might be an NFS
problem or a SAP program.  Except for a few months adventure with the
z/OS NFS server, NFS has just worked on both AIX and Linux.  If you got
the filesystem mounted, NFS was a reliable way to get data from one
system to another.

So what could the problem be?

The SAP admin folks have opened a message with the SAP support folks.

But what if it is a Linux problem?  Here is a little more history.

Most of the other systems that are connected to this NFS server are at
the 2.6.16.60-0.89.1 or the 2.6.16.60-0.91.1 kernel levels.

But we still had one set of servers that were at the 2.6.16.60-0.59
kernel level.  (Let me say something here.  The transport system for
this set of servers was rock solid that this kernel level.)  But we
needed to upgrade these servers to a higher level.  In an attempt to fix
some other problems, the decision was made to update the dev/TST and
production servers to the latest and greatest level.  2.6.16.60-0.95.1.
At that level, the QA system started having hipersocket/ksoftirq
problems.  We contacted Novell, and they supplied a PTF which took the
kernel up to 2.6.16.60-0.95.1.3954.0.PTF.746392-default.

Two days after this kernel level was putting the QA/TST system, the SAP
transport started experiencing corrupted files.  Over the weekend, the
NFS Server was updated to 2.6.16.60-0.91.1.  But we still experience the
corruption problems.

At this point, we have not gotten the Novell folks involved.

Does anyone have any suggestions?  Should we backout the .95 kernel and
it's PTF?

Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Does cpuplugd use the cpu hot plug interface?

[Ron Foster at Baldor-IS]

Mark,

The landscape of servers having this problem is SLES10.  (And due to a number 
of unfortunate events, still SP3).  The latest event being... We put the .95 
(SP4) kernel into the developers QA system that belongs to this landscape and 
almost immediately ran into the ksoftirq problem.  IBM has issued a PTF for the 
.95 kernel and we are watching to see if it is stable,  If it is we start 
rolling out the .95 kernel into our production servers in this landscape.

Thanks for the info about the .95 patch level.  This lets us know that the .95 
kernel will fix at least two of our problems.  

Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Thursday, February 23, 2012 1:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Does cpuplugd use the cpu hot plug interface?

 On 2/22/2012 at 11:22 PM, Ron Foster at Baldor-IS rfos...@baldor.com 
 wrote:
 Hello listers,
 We are experiencing a problem where occasionally we get some uninterruptable
 processes that appear to hang.
 We use CPUPLUGD.

-snip-
 I found this hit that might be related:

 http://git390.marist.edu/cgi-bin/gitweb.cgi?p=linux-2.6.git;a=commit;h=f2db2e6
 cb3f5f766cbb3788af44705685ff2445a

-snip-
 Does CPUPLUGD use this mechanism?

I think it would have to use it.

 Could this be be our problem?

It could be.  You don't say what version you're seeing this on, but I see the 
patch for this mentioned in the changelog for  
kernel-default-2.6.32.54-0.3.1.s390x.rpm on SLES11 SP1 and 
kernel-default-2.6.16.60-0.95.1 on SLES10 SP4.
patches.arch/s390-34-01-pfault-cpu-hotplug.patch and
patches.arch/s390-60-01-pfault-cpu-hotplug.patch respectively.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Does cpuplugd use the cpu hot plug interface?

[Ron Foster at Baldor-IS]

Hello listers,
We are experiencing a problem where occasionally we get some uninterruptable 
processes that appear to hang.
We use CPUPLUGD.

The problem re-appeared whenever we moved workload around and caused some 
stress on memory.
I found this hit that might be related:

http://git390.marist.edu/cgi-bin/gitweb.cgi?p=linux-2.6.git;a=commit;h=f2db2e6cb3f5f766cbb3788af44705685ff2445a

It says:
[S390] pfault: cpu hotplug vs missing completion interrupts
On cpu hot remove a PFAULT CANCEL command is sent to the hypervisor
which in turn will cancel all outstanding pfault requests that have
been issued on that cpu (the same happens with a SIGP cpu reset).
The result is that we end up with uninterruptible processes where
the interrupt that would wake up these processes never arrives.

Does CPUPLUGD use this mechanism?
Could this be be our problem?
Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: ksoftirqd using 100% CPU

[Ron Foster at Baldor-IS]

FYI,

Known problem with the .95 kernel.  IBM has released a PTF and we are testing 
it.

Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Friday, February 10, 2012 12:11 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ksoftirqd using 100% CPU

 On 2/10/2012 at 11:33 AM, Alan Altmark alan_altm...@us.ibm.com wrote:
 On Friday, 02/10/2012 at 10:21 EST, Ron Foster at Baldor-IS
 rfos...@baldor.com wrote:

 I did not know that we could open a PMR with IBM directly.

 Only if your Linux support contract is with IBM.

But, if you've already opened a PMR with IBM for z/VM or for hardware (for 
whatever reason related to the incident), we'd like to know about it anyway.  I 
know the same is true in the reverse, if a customer comes to us first, and then 
later needs to work with IBM on the problem because it involves IBM software or 
hardware.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Any recommendations on SET MIH

[Ron Foster at Baldor-IS]

Hello,

We recently started having a chpid start throwing interface control checks.  
The z/OS guy made the chpid unavailable to zOS and told us to vary off the 
chpid to z/VM.  This happened a few months ago.  Since then z/VM was IPL'ed.  
And the chpid started throwing Interface Control checks.  It took a while (a 
few days) to think about looking for an interface control check, but one of the 
LPAR Linux systems (an NFS Server)  had them in the log.

My question is what about the Linux guests under z/VM.  We are using set MIH 
off.  Is that appropriate?  The virtual machine operations book says the CP 
sends you a message if it detects an interface control check.  Does this 
message show up in /var/log messages?

We do not have a z/VM console log manager.  We have something that a person 
here put together with PROP. (and sometimes it is not running).  So we may or 
may not have had interface control checks reflected to the operator console.

Any ideas, should we run set MIH on(at least until the hardware gets fixed.)

Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: ksoftirqd using 100% CPU

[Ron Foster at Baldor-IS]

Shane,
As best we can tell, there were no relevant messages that came out on the vm 
operator console.
Ron

From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Shane G 
[ibm-m...@tpg.com.au]
Sent: Friday, February 10, 2012 6:46 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ksoftirqd using 100% CPU

On Fri, Feb 10th, 2012 at 11:00 PM, Joerg Reuter wrote:

 On Thu, Feb 09, 2012 at 04:43:25PM -0600, Ron Foster at Baldor-IS wrote:

  The only messages I can find have to do with a hipersockets time out.
  Feb  9 11:21:39 bus0104 kernel: NETDEV WATCHDOG: hsi0: transmit timed
 out
  Feb  9 11:21:39 bus0104 kernel: qeth: Recovery of device 0.0.5100
  started ...

 Hmm, that shouldn't happen.

Lol ...
I was wondering if the OP could see anything from z/VM, but if it really is a
softirq/tasklet problem that probably means (Linux) dodgy driver.
And in almost all occasions that probably means network ...

Keeping an eye on /proc/interrupts might be instructive.

Shane ...

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: ksoftirqd using 100% CPU

[Ron Foster at Baldor-IS]

Jeorg,

We have a support agreement with Novell, so I will be opening up a service 
request.

The developers were getting hostile, so I had to revert the development system 
that was consistently having the problem to a previous level.  But I have found 
another system that had the problem once yesterday that we can use to gather 
the documentation.

Ron

I did not know that we could open a PMR with IBM directly.



From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Joerg Reuter 
[jreu...@suse.de]
Sent: Friday, February 10, 2012 6:00 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: ksoftirqd using 100% CPU

On Thu, Feb 09, 2012 at 04:43:25PM -0600, Ron Foster at Baldor-IS wrote:

 The only messages I can find have to do with a hipersockets time out.
 Feb  9 11:21:39 bus0104 kernel: NETDEV WATCHDOG: hsi0: transmit timed out
 Feb  9 11:21:39 bus0104 kernel: qeth: Recovery of device 0.0.5100
 started ...

Hmm, that shouldn't happen. If you have a support agreement,
can you open a service request with Novell / SUSE, please? We'll
need the files generated by running supportconfig and dbginfo.sh,
and if you already have opened a case with IBM, the PMR would be handy.

Regards,
Joerg
--
Joerg Reuterhttp://yaina.de/jreuter
And I make my way to where the warm scent of soil fills the evening air.
Everything is waiting quietly out there (Anne Clark)

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

ksoftirqd using 100% CPU

[Ron Foster at Baldor-IS]

Hello listers,

Last night I upgraded one of the Linux guests used by our developers to
kernel level 2.6.16.60-0.95.1-default.  (Latest SLES10 SP4 kernel)  By
about 11:30 AM this morning, I was getting complaints from our
developers that the system was hanging.  Looking around, I saw that
ksoftirqd was using close to 100% cpu.

Anyone got any ideas on what to check?  I have looked in the archives,
but they are a little old.

The only messages I can find have to do with a hipersockets time out.
Feb  9 11:21:39 bus0104 kernel: NETDEV WATCHDOG: hsi0: transmit timed out
Feb  9 11:21:39 bus0104 kernel: qeth: Recovery of device 0.0.5100
started ...
Feb  9 11:21:39 bus0104 kernel: qeth: Device 0.0.5100/0.0.5101/0.0.5102
is a HiperSockets card (level: HSEC)
Feb  9 11:21:39 bus0104 kernel: with link type HiperSockets.
Feb  9 11:21:39 bus0104 kernel: qeth: Hardware IP fragmentation not
supported on hsi0
Feb  9 11:21:39 bus0104 kernel: qeth: VLAN enabled
Feb  9 11:21:39 bus0104 kernel: qeth: Multicast enabled
Feb  9 11:21:39 bus0104 kernel: qeth: IPV6 enabled
Feb  9 11:21:39 bus0104 kernel: qeth: Broadcast enabled
Feb  9 11:21:39 bus0104 kernel: qeth: Using SW checksumming on hsi0.
Feb  9 11:21:39 bus0104 kernel: qeth: Outbound TSO not supported on hsi0
Feb  9 11:21:39 bus0104 kernel: qeth: Device 0.0.5100 successfully
recovered!
q
Anyone got any ideas on what to check?  I have looked in the archives,
but they are a little old.

Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

Mark,

Back in deep dark ancient history, if you had a Linux system with multiple 
interfaces, you had to put the device name you on the default route or you got 
an error message at boot up.  It looks like that has changed.

When I put a - for the device name, I no longer get the message when I boot the 
system.

That makes the upgrade easier.

Thanks,
Ron




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Friday, February 03, 2012 10:28 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

 On 2/3/2012 at 10:13 AM, Ron Foster at Baldor-IS rfos...@baldor.com wrote:
 3. You may ask why we used qeth-bus-ccw-0.0.0700 instead of the short
 interface name eth0.  The reason why is that in our experience, the short
 interface names
 have this habit of changing.  We would come in some Saturday night, take all
 the Linux systems down, apply some z/vm maintenance, and then bring up our
 Linux
 systems.  At that point, some number of our Linux systems no longer
 communicated with the outside world.  I finally got tired of that and changed
 all the default
 routes to use the long names.

That sounds very odd.  SLES10 uses udev to control that, and the rules are 
based on virtual device number to make sure the same name gets assigned every 
time.  Was this system upgraded from SLES9 before?  That's the only thing I 
could think of that might have an influence on this since SLES9's use of udev 
was very much limited and different.

 4. You might say that that problem is fixed and does not happen anymore.  On
 this system I am upgrading the interface we want to use for communication
 to the outside world is eth4.  I start out the upgrade, and by the time I
 get to the second part of the upgrade, that is the part where I lose network
 connectivity.  The interface name has changed to eth0 and it looks like
 SLES11 SP1 is no longer honoring the long interface name, so this Linux
 system
 cannot communicate with the outside world during the second part of the
 upgrade.

 I suppose my next step is to put the SLES10 SP4 system back, and change the
 default route to use eth4 and see if when the upgrade process changes the
 interface
 name, it also changes the default route.

I would try just leaving the interface name off entirely, since the kernel 
should be able to figure out what interface to use based on the IP address of 
the default gateway.

 Does anyone know where some documentation that documents this behavior?

No, since it's typically not supposed to act this way.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

Marcy,

Thanks for the info.

It appears that on SLES11SP1 the name of the file changed to 

70-persistent-net.rules

Thanks for giving the information on where the rules files are.

Ron

From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes 
[marcy.d.cor...@wellsfargo.com]
Sent: Friday, February 03, 2012 9:36 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

So you can modify /etc/udev/rules.d/30-net_persistent_names.rules

For the servers we have with more than 1 interface, it contains this:

SUBSYSTEM==net, ACTION==add, ENV{PHYSDEVPATH}==*0.0.3000, 
IMPORT=/lib/udev/rename_netiface %k eth0
SUBSYSTEM==net, ACTION==add, ENV{PHYSDEVPATH}==*0.0.4000, 
IMPORT=/lib/udev/rename_netiface %k eth1


That file refers you to 
/usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names for more 
info



Marcy

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Ron 
Foster at Baldor-IS
Sent: Friday, February 03, 2012 7:13 AM
To: LINUX-390@vm.marist.edu
Subject: Re: [LINUX-390] Anyone lose network connectivity during upgrade to 
SLES11 SP1

Tobias,

I will have to further testing, but I think you have come up with the cause of 
our problem.  I am just going to have to figure out the best way to fix it.

Here is the problem:

1. Almost all of our systems have more than one network interface.
2. So in order to avoid an error message, we have to modify our default route 
to include the interface.
In order to keep that interface name from changing, we used the SLES10 version 
of persistent interface names.  In other words, our default route looks like 
this:
default 10.80.200.1 - qeth-bus-ccw-0.0.0700
3. You may ask why we used qeth-bus-ccw-0.0.0700 instead of the short interface 
name eth0.  The reason why is that in our experience, the short interface names
have this habit of changing.  We would come in some Saturday night, take all 
the Linux systems down, apply some z/vm maintenance, and then bring up our Linux
systems.  At that point, some number of our Linux systems no longer 
communicated with the outside world.  I finally got tired of that and changed 
all the default
routes to use the long names.
4. You might say that that problem is fixed and does not happen anymore.  On 
this system I am upgrading the interface we want to use for communication
to the outside world is eth4.  I start out the upgrade, and by the time I get 
to the second part of the upgrade, that is the part where I lose network
connectivity.  The interface name has changed to eth0 and it looks like SLES11 
SP1 is no longer honoring the long interface name, so this Linux system
cannot communicate with the outside world during the second part of the upgrade.

I suppose my next step is to put the SLES10 SP4 system back, and change the 
default route to use eth4 and see if when the upgrade process changes the 
interface
name, it also changes the default route.

Does anyone know where some documentation that documents this behavior?

Thanks,
Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Tobias Doerkes 
[tdoer...@hotmail.com]
Sent: Friday, February 03, 2012 2:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

Hi,

what about routing? Is it possible that the default route does point to an 
inactive interface?

Kind regards,
Tobias.

PS: Sorry i forgot the subject.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

Tobias,

Yes the default route was pointing to an interface that used the long form of 
the interface name.  It appears that SLES11 SP1 does not use that form of the 
interface name any more.

Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Tobias Doerkes 
[tdoer...@hotmail.com]
Sent: Friday, February 03, 2012 2:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

Hi,

what about routing? Is it possible that the default route does point to an 
inactive interface?

Kind regards,
Tobias.

PS: Sorry i forgot the subject.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

Tobias,

I will have to further testing, but I think you have come up with the cause of 
our problem.  I am just going to have to figure out the best way to fix it.

Here is the problem:

1. Almost all of our systems have more than one network interface.
2. So in order to avoid an error message, we have to modify our default route 
to include the interface.  
In order to keep that interface name from changing, we used the SLES10 version 
of persistent interface names.  In other words, our default route looks like 
this: 
default 10.80.200.1 - qeth-bus-ccw-0.0.0700
3. You may ask why we used qeth-bus-ccw-0.0.0700 instead of the short interface 
name eth0.  The reason why is that in our experience, the short interface names
have this habit of changing.  We would come in some Saturday night, take all 
the Linux systems down, apply some z/vm maintenance, and then bring up our Linux
systems.  At that point, some number of our Linux systems no longer 
communicated with the outside world.  I finally got tired of that and changed 
all the default
routes to use the long names.
4. You might say that that problem is fixed and does not happen anymore.  On 
this system I am upgrading the interface we want to use for communication
to the outside world is eth4.  I start out the upgrade, and by the time I get 
to the second part of the upgrade, that is the part where I lose network 
connectivity.  The interface name has changed to eth0 and it looks like SLES11 
SP1 is no longer honoring the long interface name, so this Linux system
cannot communicate with the outside world during the second part of the upgrade.

I suppose my next step is to put the SLES10 SP4 system back, and change the 
default route to use eth4 and see if when the upgrade process changes the 
interface
name, it also changes the default route.

Does anyone know where some documentation that documents this behavior?

Thanks,
Ron   


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Tobias Doerkes 
[tdoer...@hotmail.com]
Sent: Friday, February 03, 2012 2:03 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

Hi,

what about routing? Is it possible that the default route does point to an 
inactive interface?

Kind regards,
Tobias.

PS: Sorry i forgot the subject.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

Hello,
We are in the midst of performing our first upgrade from SLES10 SP4 to
SLES11 SP1 and are having network connection issues.
We are attempting to upgrade our Linux sandbox system that runs under
z/VM.  We ipl from the card reader and perform the first part of the
upgrade just fine.  After the first part of the upgrade, the install
program reboots itself.  All appears to be working fine until the part
that tells us to VNC into the system to finish the upgrade.
At that point we try to do this and VNC does not connect.  We try to
ping the guest and get no response.  I run nmap against the address and
it shows no ports open.
The device 0700 being used is connected to a VSWITCH.  Before the
upgrade, the device works fine.  The first part of the upgrade works
fine.  It is only the second part of the upgrade that does not work ok.
Here are what I think are the relevant portions of the messages that
come out out boot.
dasd-eckd.412b53: 0.0.0201: DASD with 4 KB/block, 2403360 KB total size,
48 KB/t
rack, compatible disk layout
 dasdd:
qeth.736dae: 0.0.0700: Device is a Guest LAN QDIO card (level: V620)
with link type GuestLAN QDIO (portname: )
qeth.47953b: 0.0.0700: Hardware IP fragmentation not supported on eth0
qeth.066069: 0.0.0700: Inbound source MAC-address not supported on eth0
qeth.d7fdb4: 0.0.0700: VLAN enabled
qeth.e90c78: 0.0.0700: Multicast enabled
qeth.5a9d02: 0.0.0700: IPV6 enabled
qeth.184d8a: 0.0.0700: Broadcast enabled
qeth.dac2aa: 0.0.0700: Using SW checksumming on eth0.
qeth.9c4c89: 0.0.0700: Outbound TSO not supported on eth0
VOL1/  0X0200:
Adding 2403256k swap on /dev/dasdb1.  Priority:-1 extents:1 across:2403256k
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised:
dm-de...@redhat.com
redir.aspx?C=c96b8535c5c94f02aa7b733fd5bd1f87URL=mailto%3adm-devel%40redhat.com

loop: module loaded

REISERFS (device dasda2): found reiserfs format 3.6 with standard journal
(Deleted lines)
Disabling IPv6 privacy..done
..done
Setting up hostname 'bus0105'..done
Setting up loopback interface lo
loIP address: 127.0.0.1/8
  IP address: 127.0.0.2/8
..done
Running sadc
..done
Setting kernel specific parameters for a SAP system
..doneSystem Boot Control: The system has been set up
Skipped features:  [80C [14Dboot.md
System Boot Control: Running /etc/init.d/boot.local
..doneStarting syslog services..done
Starting D-Bus daemon..done
Loading CPUFreq modules (CPUFreq not supported)
Starting HAL daemon..done
Setting up (localfs) network interfaces:
lo
loIP address: 127.0.0.1/8
  IP address: 127.0.0.2/8
lo
..doneeth0  name: IBM OSA Express Network card (0.0.0700)
eth0  IP address: 10.80.200.126/24
eth0
..doneWaiting for mandatory devices:  qeth-bus-ccw-0.0.0600
qeth-bus-ccw-0.0.510
0 qeth-bus-ccw-0.0.5200 qeth-bus-ccw-0.0.a006 __NSC__
20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
qeth-bus-ccw-0.0.0600   No interface found
..failedqeth-bus-ccw-0.0.5100   No interface found
..failedqeth-bus-ccw-0.0.5200   No interface found
..failedqeth-bus-ccw-0.0.a006   No interface found
..failedSetting up service (localfs) network  .  .  .  .  .  .  .  .  .
...fail
ed

***
***  Please return to your X-Server screen to finish installation
***

pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.

starting VNC server...
A log file will be written to: /var/log/YaST2/vncserver.log ...

***
***   You can connect to 10.80.200.126, display :1 now with
vncviewer
***   Or use a Java capable browser on
http://10.80.200.126:5801/
redir.aspx?C=c96b8535c5c94f02aa7b733fd5bd1f87URL=http%3a%2f%2f10.80.200.126%3a5801%2f

***

(When YaST2 is finished, close your VNC viewer and return to this window.)

*** Starting YaST2 ***
This is a sandbox system, so for various reasons has many network
interfaces.
But for this run, the 0600, 5100, 5200, and a006 interfaces have been
removed
from the directory.  That is the reason for all the no interface found
messages.
We have also made an update run where we removed the interfaces from the
guest before we started.  The results were the same.  We try to connect
to 10.80.200.126
and do not get a response.
Any ideas?
Any additional documentation required?
Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

My cohort said that in his latest try, he removed all the extraneous 
interfaces, and had the same result.  He said he tried to ping it and did not 
get a response.


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Thursday, February 02, 2012 2:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

 On 2/2/2012 at 02:34 PM, Ron Foster at Baldor-IS rfos...@baldor.com wrote:
 We have also made an update run where we removed the interfaces from the
 guest before we started.  The results were the same.  We try to connect
 to 10.80.200.126
 and do not get a response.
 Any ideas?

When you do this with all the extraneous interfaces removed, what messages come 
out on the console after the activation of the 0.0.0700 vNIC?  Are you able to 
ping that vNIC from another guest on the 10.80.200.126/24 network?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

This is a layer 3 vswitch.


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Thursday, February 02, 2012 2:41 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Anyone lose network connectivity during upgrade to SLES11 SP1

 On 2/2/2012 at 02:34 PM, Ron Foster at Baldor-IS rfos...@baldor.com wrote:
 We have also made an update run where we removed the interfaces from the
 guest before we started.  The results were the same.  We try to connect
 to 10.80.200.126
 and do not get a response.
 Any ideas?

Also, is this a Layer 2 vNIC?  If so, is LLADDR specified in 
/etc/sysconfig/network/ifcfg-??


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Anyone lose network connectivity during upgrade to SLES11 SP1

[Ron Foster at Baldor-IS]

No. The ping attempt was not made from the same subnet. We will try  
this on the next attempt.

Sent from my iPhone

On Feb 2, 2012, at 4:13 PM, Mark Post mp...@novell.com wrote:

 On 2/2/2012 at 04:14 PM, Ron Foster at Baldor-IS rfos...@baldor.com 
  wrote:
 My cohort said that in his latest try, he removed all the extraneous
 interfaces, and had the same result.  He said he tried to ping it  
 and did not
 get a response.

 My question, though, was the ping attempt made from the same subnet?  
 I.e., no routing involved.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions,
 send email to lists...@vm.marist.edu with the message: INFO  
 LINUX-390 or visit
 http://www.marist.edu/htbin/wlvindex?LINUX-390
 --
 For more information on Linux on System z, visit
 http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Is it possible to upgrade from SLES10 SP4 to SLES11 SP1?

[Ron Foster at Baldor-IS]

Hello listers,

Due to other work late last year, we were unable to migrate from SLES10
SP3 to SLES11, so we migrated to SLES10 SP4 instead.

Now is the time to start looking at migrating the systems to SLES11 SP1.

However, when I go out to the Novell website and look for the How to
upgrade to SLES11 SP1, I do not see SLES10 SP4 as a supported migration
path.

Anyone know if you can migrate from SLES10 SP4 to SLES11 SP1?

Thanks,
Ron Foster
Baldor Electric

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Is it possible to upgrade from SLES10 SP4 to SLES11 SP1?

[Ron Foster at Baldor-IS]

Mark,

One of my cohorts tried to upgrade a system.

He said he got a message saing something like the product could not be upgraded.

He did not print off the exact message.

Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Wednesday, February 01, 2012 12:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Is it possible to upgrade from SLES10 SP4 to SLES11 SP1?

 On 2/1/2012 at 09:33 AM, Ron Foster at Baldor-IS rfos...@baldor.com wrote:
 Hello listers,

 Due to other work late last year, we were unable to migrate from SLES10
 SP3 to SLES11, so we migrated to SLES10 SP4 instead.

 Now is the time to start looking at migrating the systems to SLES11 SP1.

 However, when I go out to the Novell website and look for the How to
 upgrade to SLES11 SP1, I do not see SLES10 SP4 as a supported migration
 path.

 Anyone know if you can migrate from SLES10 SP4 to SLES11 SP1?

When the How to upgrade to SLES/SLED 11 SP1 TID was written, SLES10 SP4 
hadn't been released.  I've sent the author a note asking him if that should be 
updated to list SLES10 SP4, since upgrading from it to SLES11 SP1 is supported. 
 Just make sure you have all available maintenance for SLES10 SP4 installed 
before starting the upgrade.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Is it possible to upgrade from SLES10 SP4 to SLES11 SP1?

[Ron Foster at Baldor-IS]

Hello,

I was going through the process of performing the upgrade on another system 
with my cohort.  We were going to gather all the evidence to open a service 
request.  The upgrade got past the point where it was not finding a product to 
be upgraded.  My cohort said he did not apply all the latest SP4 maintenance.  
When I went through it with him, we did all the maintenance.

The upgrade did not complete successfully, but got further.

Ron

From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Wednesday, February 01, 2012 2:22 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Is it possible to upgrade from SLES10 SP4 to SLES11 SP1?

 On 2/1/2012 at 03:10 PM, Ron Foster at Baldor-IS rfos...@baldor.com wrote:

 One of my cohorts tried to upgrade a system.

 He said he got a message saing something like the product could not be
 upgraded.

 He did not print off the exact message.

Ron,

Well that's pretty unhelpful.  :(  If the logs are still on the system, it's 
not too late to open up a service request about it.  That upgrade path has been 
tested, which is why it has been declared to be supported in the release notes.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Interface control check message in /var/log/messages

[Ron Foster at Baldor-IS]

Hello listers,

While looking for something else, I ran across the following in
/var/log/messages.  As far as I can tell, these messages have only
appeared once.  (I did not look that hard.)

The message came out of our Linux LPAR system.

Nov 29 17:20:08 busnfs kernel: dasd_erp(3990):  0.0.940f: channel or
interface control check
Nov 29 17:20:08 busnfs kernel: dasd_erp(3990):  0.0.940f:
dasd_3990_erp_action_4: first time retry

Should I let someone know about this?

Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Interface control check message in /var/log/messages

[Ron Foster at Baldor-IS]

Marcy,

This particular Linux system is LPAR.

The z/OS guy said that they have a chpid going to the DS8800 in question varied 
off to the z/OS systems because of errors it was giving.  I am in the process 
of trying to figure out how to vary off this chipid to this linux lpar.

Thanks for your help.
Ron Foster
Baldor


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes 
[marcy.d.cor...@wellsfargo.com]
Sent: Wednesday, November 30, 2011 12:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interface control check message in /var/log/messages

Are you in an LPAR or under z/VM?

You had an i/o fail.  It retried and was likely successful (or you'd be having 
more pain).

You can have your HW vendor investigate.

If you are under z/VM then there's probably some messages in the operator 
console as well.  And EREP records.
Under an LPAR, well, I don't know much about that :)

Marcy

This message may contain confidential and/or privileged information. If you are 
not the addressee or authorized to receive this for the addressee, you must not 
use, copy, disclose, or take any action based on this message or any 
information herein. If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message. Thank you for 
your cooperation.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Ron 
Foster at Baldor-IS
Sent: Wednesday, November 30, 2011 10:10 AM
To: LINUX-390@vm.marist.edu
Subject: [LINUX-390] Interface control check message in /var/log/messages

Hello listers,

While looking for something else, I ran across the following in
/var/log/messages.  As far as I can tell, these messages have only
appeared once.  (I did not look that hard.)

The message came out of our Linux LPAR system.

Nov 29 17:20:08 busnfs kernel: dasd_erp(3990):  0.0.940f: channel or
interface control check
Nov 29 17:20:08 busnfs kernel: dasd_erp(3990):  0.0.940f:
dasd_3990_erp_action_4: first time retry

Should I let someone know about this?

Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Interface control check message in /var/log/messages

[Ron Foster at Baldor-IS]

Mike/Marcy,

I have got the chpid varied off.  

Thanks for the help,
Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Michael O'Reilly 
[mik...@us.ibm.com]
Sent: Wednesday, November 30, 2011 1:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interface control check message in /var/log/messages

Ron,

Perhaps you are looking for: Linux on System z Device Drivers, Features,
and Commands on SUSE Linux Enterprise Server 11 SP1
   at http://public.dhe.ibm.com/software/dw/linux390/docu/l26edd01.pdf
Chapter 42. Avoiding common pitfalls: Ensuring correct channel path
status

Note: I recommend that you first run lscss to make sure no other devices,
eg. the 3215, are using the chpid.



 Mike O'Reilly
 IBM Linux Change Team


















 Ron Foster at
 Baldor-IS
 RFoster@baldor.c  To
 om   LINUX-390@vm.marist.edu
 Sent by: Linux on  cc
 390 Port
 linux-...@vm.mar Subject
 ist.edu  Re: Interface control check message
   in /var/log/messages

 11/30/2011 11:06
 AM


 Please respond to
 Linux on 390 Port
 linux-...@vm.mar
 ist.edu






Marcy,

This particular Linux system is LPAR.

The z/OS guy said that they have a chpid going to the DS8800 in question
varied off to the z/OS systems because of errors it was giving.  I am in
the process of trying to figure out how to vary off this chipid to this
linux lpar.

Thanks for your help.
Ron Foster
Baldor


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Marcy Cortes
[marcy.d.cor...@wellsfargo.com]
Sent: Wednesday, November 30, 2011 12:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interface control check message in /var/log/messages

Are you in an LPAR or under z/VM?

You had an i/o fail.  It retried and was likely successful (or you'd be
having more pain).

You can have your HW vendor investigate.

If you are under z/VM then there's probably some messages in the operator
console as well.  And EREP records.
Under an LPAR, well, I don't know much about that :)

Marcy

This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you
must not use, copy, disclose, or take any action based on this message or
any information herein. If you have received this message in error, please
advise the sender immediately by reply e-mail and delete this message.
Thank you for your cooperation.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Ron
Foster at Baldor-IS
Sent: Wednesday, November 30, 2011 10:10 AM
To: LINUX-390@vm.marist.edu
Subject: [LINUX-390] Interface control check message in /var/log/messages

Hello listers,

While looking for something else, I ran across the following in
/var/log/messages.  As far as I can tell, these messages have only
appeared once.  (I did not look that hard.)

The message came out of our Linux LPAR system.

Nov 29 17:20:08 busnfs kernel: dasd_erp(3990):  0.0.940f: channel or
interface control check
Nov 29 17:20:08 busnfs kernel: dasd_erp(3990):  0.0.940f:
dasd_3990_erp_action_4: first time retry

Should I let someone know about this?

Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit

Re: Interface control check message in /var/log/messages

[Ron Foster at Baldor-IS]

chchp -v 0 0.1d

1d is the chpid that i varied offline.

Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Wednesday, November 30, 2011 2:17 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Interface control check message in /var/log/messages

 On 11/30/2011 at 02:49 PM, Ron Foster at Baldor-IS rfos...@baldor.com 
 wrote:

 Mike/Marcy,

 I have got the chpid varied off.

For the benefit of others, how did you do that?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Accessing Old Linux System After DASD Move

[Ron Foster at Baldor-IS]

You'll then also need the other
volumes, probably also at their prior subchannel addresses.  (I/O
addresses are not necessarily cast in stone, but you don't know at
this point.)

In my experience, the important address to get correct is the IPL
volume.  That address appears to be baked into the initrd.

We use lvm here, so if all the lvm volumes are there accessible
to the lpar, lvm will find them regardless of the address.

You can run without swap volumes long enough to fix them.

If you are lucky, then the system will come up in full muti-user
mode.

If not..

Then if / gets mounted, then you have access to commands
that would be useful to fix the situation.  (Just for such
emergencies, we leave a specially named fstab in /etc
that mounts a minimum number of filesystems.  We put that
fstab in place and see if the boot gets a little farther.)

One of the key things if you get far enough is to see how
the fstab is constructed.  There are several types of mounts.
Some require the volumes to have a certain address.  Some
might be tied to the storage controller in use.  Some might require
certain subchannel addresses.

If you get into multi-user mode, but without a network 
adapter that works, then you hope that that the inittab has
the entry in it that lets you access the emulated ascii
terminal on the HMC.

How good is the documentation concerning these systems.
Did someone turn on sitar or something like it to 
produce documentation.  Do you still have it somewhere?
If so, then it should be easier to match the environment that
this image is expecting.  How about DR documentation?  If
someone saved the image, they might have also saved the
recovery documentation.

BTW, I am a SLES person, I don't know if Red Hat
works the same way.

Good luck,
Ron


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Richard Troth 
[vmcow...@gmail.com]
Sent: Thursday, November 03, 2011 1:15 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Accessing Old Linux System After DASD Move

First, let's hope these old Linux systems used EXT2 (or EXT3, which is
compatible), if you need to read the content.  Linux supports a wide
range of filesystem types.

USS will not be able to use the Linux volumes ... at all.

z/OS *may* be able to read the partitions on the Linux volumes
(usually just one per).  This magic requires that Linux had been using
CDL, the compatible disk layout.  The partitions should then be
usable on any other Linux system: z, PC, even things like PowerMac.
Other filesystem types (besides EXT2 or EXT3) will be usable by such
other Linux systems, no problem.  You could read the partitions (as
RECFM=U datasets), copy the content (as binary) to a working Linux
system (any HW) and do what we call a loop-back mount.  You can
probably recover all the content that way, and it would let you engage
one of your Linux people to help snoop around.

There is a tool for CMS to read EXT2 filesystems.  Do you have VM in-house?

That's for scanning.  But you said you have been asked to bring them
up.  How did they run?  (Rhetorical: you said LPAR.)  Start with just
one.  (dunno how many Linux images you have, if LPAR then maybe only
ever just one)  To make it bootable, you'll need the boot vol at
whatever address it was before.  You'll then also need the other
volumes, probably also at their prior subchannel addresses.  (I/O
addresses are not necessarily cast in stone, but you don't know at
this point.)  Once all the DASD are arranged at their prior addresses,
you should be able to point-n-shoot.  Other failures might not stop
the boot sequence.  (Like network interface missing or at a different
addr.)  But filesystems get usually get checked.

So ... where are you at after all that?

-- R;   
Rick Troth
Velocity Software
http://www.velocitysoftware.com/





On Thu, Nov 3, 2011 at 13:47, Craig Pace cp...@fruit.com wrote:
 List,

 I have been doing some reading, scanning and searching and have come to
 many different answers and was wondering if someone might have some
 suggestions on this item.  We have an old Linux environment.  I am not
 sure how old it is; however, I know it is between 2  3 years at least.
 The system (Linux on System z - LPAR Mode) was not active and had the DASD
 (ECKD format) moved from one storage sub-system to another with now
 different UCBs.  I have been asked to look into bring up this system.  Is
 there any easy way to access the data to update the required
 configuration to now point to the correct UCB addresses?  At this point,
 we only have z/OS LPARs running in the environment with no other Linux.  I
 was hoping that I might be able to do something with USS; however, he does
 not know about the formatted filesystems that was built by Linux-390.



 Thanks,

 Craig Pace
 Lead z/OS Systems Programmer
 Fruit of the Loom, Inc.®

 Office: (270) 781-6400 ext. 4397
 Cell:   (270) 991-7452
 Fax:(270) 438-4430
 E-mail:  cp...@fruit.com

 One Fruit of the 

Re: Yast not auto selecting all security and recommended patches

[Ron Foster at Baldor-IS]

SPident-0.9-74.36.1


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Sunday, October 16, 2011 12:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Yast not auto selecting all security and recommended patches

 On 10/14/2011 at 05:08 PM, Ron Foster at Baldor-IS rfos...@baldor.com 
 wrote:

 It sounds logical, but the line in the yast update screen implies SP4.  For
 example,

 *slesp4-SPident *Recommended update for SPident
 *recommended*7441-0*

Ron,

What does rpm -q SPident report?


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Yast not auto selecting all security and recommended patches

[Ron Foster at Baldor-IS]

Hello listers,

I was in the process of verifying that the proper patches were installed
on a group of servers that were freshly upgraded from SLES10SP3 to
SLES10SP4.  When I went into online update, I noticed several patches
that were classified as security or recommended that were not auto
selected.  They were for modules that we do have installed.

I was under the impression that security or recommended patches were
automatically selected.

When I go rummage around the YaST documentation on the Novell site, it
seems to indicate that the actions for security and recommended patches
were automatically set.

If I manually select a patch, I get installation finished in the
progress log, but none of the other indiations that a patch is actually
applied (like messages indicating things were being downloaded, or
patches applied.

Any ideas as to what is going on?

Should I manually apply these fixes?

Anybody else run into this problem?

Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Fwd: Yast not auto selecting all security and recommended patches

[Ron Foster at Baldor-IS]

More information:

When I invoke the graphical version of online update, under the summary
heading,
I see a green checkmark followed by summary information.

Dusting off a few brain cells, I seem to remember this happening
ocassionally for
one or two patches at a time.  This system has 27 patches that appear to be
in this state.

Ron

 Original Message 
Subject:Yast not auto selecting all security and recommended patches
Date:   Fri, 14 Oct 2011 15:29:48 -0500
From:   Ron Foster at Baldor-IS rfos...@baldor.com
Organization:   Baldor Electric Company
To: Linux on 390 Port LINUX-390@VM.MARIST.EDU



Hello listers,

I was in the process of verifying that the proper patches were installed
on a group of servers that were freshly upgraded from SLES10SP3 to
SLES10SP4.  When I went into online update, I noticed several patches
that were classified as security or recommended that were not auto
selected.  They were for modules that we do have installed.

I was under the impression that security or recommended patches were
automatically selected.

When I go rummage around the YaST documentation on the Novell site, it
seems to indicate that the actions for security and recommended patches
were automatically set.

If I manually select a patch, I get installation finished in the
progress log, but none of the other indiations that a patch is actually
applied (like messages indicating things were being downloaded, or
patches applied.

Any ideas as to what is going on?

Should I manually apply these fixes?

Anybody else run into this problem?

Ron


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Yast not auto selecting all security and recommended patches

[Ron Foster at Baldor-IS]

Mark,

It sounds logical, but the line in the yast update screen implies SP4.  For 
example,

│slesp4-SPident │Recommended update for SPident
│recommended│7441-0│

Ron

From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post 
[mp...@novell.com]
Sent: Friday, October 14, 2011 3:40 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Yast not auto selecting all security and recommended patches

 On 10/14/2011 at 04:29 PM, Ron Foster at Baldor-IS rfos...@baldor.com 
 wrote:

 If I manually select a patch, I get installation finished in the
 progress log, but none of the other indiations that a patch is actually
 applied (like messages indicating things were being downloaded, or
 patches applied.

 Any ideas as to what is going on?

Sounds like these were patches for the SP3 version of the packages, which means 
they were obsoleted by SP4, but because the patch info files are already on the 
system, they still how up in your list.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: DASD assignment different between SLES10 and SLES11

[Ron Foster at Baldor-IS]

Peter,

Actually we observed this behavior as far back as SLES10 SP3.  We started using 
persistent device names and forgot about it.

The documentation for this is in the release notes.  From the release notes: 

  Installation using Persistent Device names
If you plan to add additional storage devices to your system after the OS
installation, we strongly recommend to use persistent device names for all
storage devices during installation. The installer by default uses the
kernel device names.

There is additional information in the SLES11 device driver manual on the 
developerworks site.
From the Device Drivers, Features, and Commands manual
SC34-2595-01

(from page 35)
autodetect
causes the DASD device driver to allocate device names and the
corresponding minor numbers to all DASD devices and set them online
during the boot process. See “DASD naming scheme” on page 31 for the
naming scheme.
The device names are assigned in order of ascending subchannel numbers.
Auto-detection can yield confusing results if you change your I/O
configuration and reboot, or if you are running as a guest operating system
in VM because the devices might appear with different names and minor
numbers after rebooting.

What may have changed is how dasd= is specified and/or how it works.  It is 
different between the SLES10 and SLES11 manuals.

Ron Foster





From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E. Abresch 
Jr.   - at Pepco [peabre...@pepco.com]
Sent: Thursday, September 29, 2011 9:59 AM
To: LINUX-390@VM.MARIST.EDU
Subject: DASD assignment different between SLES10 and SLES11

Under SLES10, we see the following:

0.0.0150(ECKD) at ( 94:  0) is dasda  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0151(ECKD) at ( 94:  4) is dasdb  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0152(ECKD) at ( 94:  8) is dasdc  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0153(ECKD) at ( 94: 12) is dasdd  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0154(ECKD) at ( 94: 16) is dasde  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.015f(ECKD) at ( 94: 60) is dasdp  : active at blocksize 4096,
150840 blocks, 589 MB

Notice that 0.0.015f is dasdp


Under SLES11, we see the following:

Bus-ID Status  Name  Device  Type  BlkSz  Size  Blocks
==
0.0.0150   active  dasda 94:0ECKD  4096   2347MB600840
0.0.0151   active  dasdb 94:4ECKD  4096   2347MB600840
0.0.0152   active  dasdc 94:8ECKD  4096   2347MB600840
0.0.0155   active  dasdd 94:12   ECKD  4096   2347MB600840
0.0.0156   active  dasde 94:16   ECKD  4096   2347MB600840
0.0.015f   active  dasdf 94:20   ECKD  4096   589MB 150840

Notice that 0.0.015f is dasdf rather than dasdp. How can I insure that
0.0.015f is always dasdp?

I read that this behavior had change but naturally now that I need this
doc, I cannot find it anywhere. I do not remember where I read it. E.

Can anyone point me in the right direction? Thanks as always.

Peter

This Email message and any attachment may contain information that is
proprietary, legally privileged, confidential and/or subject to copyright
belonging to Pepco Holdings, Inc. or its affiliates (PHI).  This Email is
intended solely for the use of the person(s) to which it is addressed.  If
you are not an intended recipient, or the employee or agent responsible for
delivery of this Email to the intended recipient(s), you are hereby notified
that any dissemination, distribution or copying of this Email is strictly
prohibited.  If you have received this message in error, please immediately
notify the sender and permanently delete this Email and any copies.  PHI
policies expressly prohibit employees from making defamatory or offensive
statements and infringing any copyright or any other legal right by Email
communication.  PHI will not accept any liability in respect of such
communications.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: DASD assignment different between SLES10 and SLES11

[Ron Foster at Baldor-IS]

Peter,
We do not have SLES11, but from the manual, on page 21 (Module parameters on 
the kernel parameter line),  it appears that the appropriate format of the 
dasd= parameter might be:

dasd_mod.dasd=0.0.150-0.0.15f

so your parameter line would be:

parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 
dasd_mod.dasd=0.0.150-0.0.15f
 TERM=dumb

Ron Foster



From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E. Abresch 
Jr.   - at Pepco [peabre...@pepco.com]
Sent: Thursday, September 29, 2011 11:09 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: DASD assignment different between SLES10 and SLES11

Yes, our root is always dasda and our swap is always dasdp. This is what
our original automated Linux cloning process expects and we wish to not
re-engineer our cloning process at this time.

Under SLES10, in /etc/zipl.conf we have the following:

parameters = root=/dev/dasda1 dasd=150-15f TERM=dumb

Under SLES11, in /etc/zipl.conf we have the following:

parameters = root=/dev/disk/by-path/ccw-0.0.0150-part1 TERM=dumb

I am thinking this is where I need to make my change, but my own memory is
slow to swap back in for me to remember all of it.

But . . .

readlink -f /dev/disk/by-path/ccw-0.0.$15F
reveals /dev/disk/by-path/ccw-0.0.5F  - it seems to strip the 1 from the
15f.

In my SLES10 cloning script, where I have the following:

echo Creating DASD swap space on /dev/dasdp1
swapoff -a
echo Formatting DASD swap space on /dev/dasdp1
dasdfmt -vy -f /dev/dasdp -d cdl -l swap01 -b 4096
echo Partitioning DASD swap space on /dev/dasdp1
fdasd -l swap01 -a /dev/dasdp
echo Making DASD swap space on /dev/dasdp1
sleep 5
mkswap /dev/dasdp1
echo Activating DASD swap space on /dev/dasdp1
swapon -a
echo Verifying DASD swap space on /dev/dasdp1
swapon ?s

I can change in my SLES11 cloning script to:

echo Creating DASD swap space on /dev/disk/by-path/ccw-0.0.5F
swapoff -a
echo Formatting DASD swap space on /dev/disk/by-path/ccw-0.0.5F
dasdfmt -vy -f /dev/disk/by-path/ccw-0.0.5F -d cdl -l swap01 -b 4096
echo Partitioning DASD swap space on /dev/disk/by-path/ccw-0.0.5F
fdasd -l swap01 -a /dev/disk/by-path/ccw-0.0.5F
echo Making DASD swap space on /dev/disk/by-path/ccw-0.0.5F
sleep 5
mkswap /dev/disk/by-path/ccw-0.0.5F
echo Activating DASD swap space on /dev/disk/by-path/ccw-0.0.5F
swapon -a
echo Verifying DASD swap space on /dev/disk/by-path/ccw-0.0.5F
swapon ?s

Is this what I should do? I am hesitant as there might me other scripted
mounts that do /dev/dasdx# . Should I eat the bullet now or defer?



Peter



From:   Ron Foster at Baldor-IS rfos...@baldor.com
To: LINUX-390@vm.marist.edu
Date:   09/29/2011 11:38 AM
Subject:Re: DASD assignment different between SLES10 and SLES11
Sent by:Linux on 390 Port LINUX-390@vm.marist.edu



Peter,

Actually we observed this behavior as far back as SLES10 SP3.  We started
using persistent device names and forgot about it.

The documentation for this is in the release notes.  From the release
notes:

  Installation using Persistent Device names
If you plan to add additional storage devices to your system after the
OS
installation, we strongly recommend to use persistent device names for
all
storage devices during installation. The installer by default uses the
kernel device names.

There is additional information in the SLES11 device driver manual on the
developerworks site.
From the Device Drivers, Features, and Commands manual
SC34-2595-01

(from page 35)
autodetect
causes the DASD device driver to allocate device names and the
corresponding minor numbers to all DASD devices and set them online
during the boot process. See ?DASD naming scheme? on page 31 for the
naming scheme.
The device names are assigned in order of ascending subchannel numbers.
Auto-detection can yield confusing results if you change your I/O
configuration and reboot, or if you are running as a guest operating
system
in VM because the devices might appear with different names and minor
numbers after rebooting.

What may have changed is how dasd= is specified and/or how it works.  It
is different between the SLES10 and SLES11 manuals.

Ron Foster





From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of Peter E.
Abresch Jr.   - at Pepco [peabre...@pepco.com]
Sent: Thursday, September 29, 2011 9:59 AM
To: LINUX-390@VM.MARIST.EDU
Subject: DASD assignment different between SLES10 and SLES11

Under SLES10, we see the following:

0.0.0150(ECKD) at ( 94:  0) is dasda  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0151(ECKD) at ( 94:  4) is dasdb  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0152(ECKD) at ( 94:  8) is dasdc  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0153(ECKD) at ( 94: 12) is dasdd  : active at blocksize 4096,
600840 blocks, 2347 MB
0.0.0154(ECKD) at ( 94: 16) is dasde  : active at blocksize 4096,
600840 blocks, 2347

Re: Mount error

[Ron Foster at Baldor-IS]

Saurabh,

First we need to determine if you really need to reach out from one Linux 
system to fix another Linux system.

At some point in the life of SLES, it became possible to put an appropriate 
entry in the /etc/inittab.  That entry allowes you to access the ASCII console 
emulator that is a part of the HMC.  If your system is at the appropriate SLES 
level, and you have the appropriate entry in /etc/inittab, and the only problem 
you are having is the fact that TCP/IP is not up, then you will have a way to 
use vi and YaST to fix your problem.

The entry is:
#zVM 5.3 Guest ASCII Console Support
cn:2345:respawn:/sbin/agetty -L 9600 ttyS1 xterm

In order for a guest to access the console, someone have to issue the following 
command:

att sysa to linuxguest

(where linux guest is the machine you are attaching the console to.)

Then navigate to your z/VM LPAR on the HMC and start the ASCII console.  Hit 
enter a couple of times and you should get a Linux logon prompt.

But if you cannot use that method...
You have to know a little bit about the how your filesystems are structured to 
do this.  

Just a thought, in zLinux, yes you have to make volumes available so that they 
are online, but you mount filesystems.  If you are using LVM, then one mount 
can access filesystems on more than one volume.

Is either one of the systems using LVM?  We happen to use LVM on our boot 
volume, so we have had to construct a special Linux guest that does not run LVM 
in order perform a task like this.  In our case, our mounts that we use looks 
like this.

mount -v -t reiserfs /dev/system/root /mnt
mount -v -t ext2 /dev/dasda1 /mnt/boot
mount -v -t reiserfs /dev/system/home /mnt/home
mount -v -t reiserfs /dev/system/opt /mnt/opt
mount -v -t reiserfs /dev/system/tmp /mnt/tmp
mount -v -t reiserfs /dev/system/usr /mnt/usr
mount -v -t reiserfs /dev/system/var /mnt/var

(Notice the mounts must contain the type of filesystem you are using.)

First you mount the root (/) filesystem.  In this case, it is an LVM, and we 
mount it to /mnt.
(mnt is where the other systems disks will start to appear.)
Next we mount the /boot filesystem at /mnt/boot.

Now due to the way we have structured things, we then have to mount our /home, 
/opt, /tmp, /var, /usr, and /var
filesystems.

Once we get done, then the other systems drives are available from a 
directory structure in /mnt.  The local 
system, is available from a directory structure in /.

How did you all set up things?  Did you all use LVM? 

If you did not use LVM, then you have to know that /mnt should be mounted to a 
particular partition.

Hope this helps,
Ron



When you booted the


From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] On Behalf Of saurabh 
khandelwal [sourabhkhandelwal...@gmail.com]
Sent: Wednesday, August 24, 2011 1:38 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Mount error

Hello,
I have two z/linux system.In both tcpip is not working. so Iogged on one
z/linux in 3270 session and copied all disk of another linux to this linux
user directory.
now I want to change the network config of the another linux by mounting the
another Linux disk here.I made that another Linux down,so that this linux
have r/w access to its dasd.

Output of LSDAD in another linux, where I monut 5 dasd of the another linux.


lsdasd
0.0.0200(ECKD) at ( 94:  0) is dasda  : active at blocksize 4096,
1802880 bl
ocks, 7042 MB
0.0.0300(ECKD) at ( 94: 40) is dasdk  : active at blocksize 4096, 600840
blo
cks, 2347 MB
0.0.0301(ECKD) at ( 94: 44) is dasdl  : active at blocksize 4096, 600840
blo
cks, 2347 MB
0.0.0302(ECKD) at ( 94: 48) is dasdm  : active at blocksize 4096, 600840
blo
cks, 2347 MB
0.0.0303(ECKD) at ( 94: 52) is dasdn  : active at blocksize 4096, 600840
blo
cks, 2347 MB
0.0.0304(ECKD) at ( 94: 56) is dasdo  : active at blocksize 4096, 600840
blo
cks, 2347 MB
sles9sp2:~ #

Out of these dasd 300-304 is from another linux, which I am trying to monut
here.


now when I am trying to monut the dasd . I was able to monut the first dasd
with below command

mount /dev/dasdl1 /d1

but, when I triyng to mount another dasd, I am getting below command


mount /dev/dasdl1 /d2
mount: /dev/dasdl1 already mounted or /d2 busy



sles9sp2:~ # mount /dev/dasdn1 /d2
mount /dev/dasdn1 /d2
FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev dasdn1.
mount: you must specify the filesystem type
Aug 23 23:07:46 sles9sp2 kernel: FAT: bogus number of reserved sectors
Aug 23 23:07:46 sles9sp2 kernel: VFS: Can't find a valid FAT filesystem on
dev d
asdn1.
sles9sp2:~ #



User directory entry for sles9sp2

 SLES9SP2 DIRMPART A1  F 80  Trunc=80 Size=37 Line=0 Col=1 Alt=0

 USER SLES9SP2 SLES9SP2 2g
*INCLUDE $VOLINKS
 option todenable lnknopas quickdsp
 CLASS G
 MAXSTORAGE 4g
 MACHINE ESA
 CPU 0 BASE NODEDICATE
 CPU 1  NODEDICATE
 CPU 2  NODEDICATE
 ipl cms parm autocr
 iucv *ident gateany gateway revoke
 iucv allow
* 

Re: location of Yast files

[Ron Foster at Baldor-IS]

I had a smiliar problem when we had to change the IP address of our NFS
server.  If you are SLES10..

Try looking at /var/lib/zypp/db/sources.  Look through the files and
find the one that describes the installation source you are interested in.

This will let you get into yast, but just changing the file does not
rebuild everything you need.  Next you go into
yastsoftwareinstallation source.

Highlight the installation source you are interested in.  Edit it.  Hist
ok to the popup describing the definition.  (The cache will be
rebuilt.)  Select
yes to accept the license agreement.  Next to get out of the
installation source app.  Then Finish.

All should be well.

Ron


On 6/7/2011 9:00 AM, Bernie Wu wrote:

Thanks Mark.  It did eventually time out.


The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. This message may 
be an attorney-client communication and/or work product and as such is 
privileged and confidential. If the reader of this message is 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, distribution, or copying of this message 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Anyone know what a disabled wait 62c8 means?

[Ron Foster at Baldor-IS]

Everyone,

I have been trying to boot a z/vm SLES10 SP3 guest  that has been shut
down for a while.

After the first page or so of messages, I get a HCPGIR450W 00020001
8000  0011662c8

The last message put out by the SLES boot process before this message is:
IP route cache hash table entries :32768 (order: 6, 262144bytes)

Anyone got any ideas?

Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: multipl cpu's

[Ron Foster at Baldor-IS]

Hello,

We are a SAP shop and do not run WebSphere.  However we do run some SAP
Java instances.  On some of those systems, we have found it beneficial
to define two CPUS, and let the garbage collector know about it.
Depending on the size of your heap, sometimes the the garbage collection
times improve noticeably.

Ron Foster

On 4/25/2011 12:09 PM, Mark Post wrote:

On 4/25/2011 at 09:34 AM, Dean, David (I/S)david_d...@bcbst.com  wrote:

Can some of you weigh in on the merits (demerits) of defining multiple CPU's
to virtual Linux boxes?  We are heavy WebSphere and have gotten differing
opinions.

The typical advice is that if you are driving a single CPU over 80%, then a 
second one would likely be useful.  Otherwise, you just add to z/VM's workload 
to schedule that virtual CPU with no benefit to the guest.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Security question about having zLinux web servers out in DMZ.

[Ron Foster at Baldor-IS]

Hello listers,

Our company has recently been acquired by another company.  We are at
the point of having to get our two networks to talk to each other.
Before we can do that, we have to comply with certain security rules.
One of them being that the mainframe cannot be exposed to the internet.

We have a couple of zLinux web servers that are running in a couple of
z/VM guests that are connected to our DMZ.  The new folks say this is a
show stopper as far as hooking up the two networks.

The questions I have are:

Is this a common restriction?  That is, you have to have your DMZ based
web servers running on some other platform so that your mainframe is not
exposed to the internet.

Or, the new folks just don't understand the built-in security provided
by the z10 and z\VM 6.1.

I know that we will end up conforming to the rules that the new folks
have, but I was just wondering if the new folks really know what they
are talking about.

Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Security question about having zLinux web servers out in DMZ.

[Ron Foster at Baldor-IS]

Everyone,

Thanks for the good responses.  Right now My Boss and his Boss are
talking to the security guys.  I have told them some of what you all
have told me.  It could be useful.

Richard, Thanks for the offer to help.  We shall see how things progress
from here.

Thanks,
Ron

On 3/30/2011 12:32 PM, Tom Duerbusch wrote:

Not a valid restriction.

Open Systems and Network types only run a single stack in a box (vast majority 
of the time).
Here, they still can't grasp that I have some 70 stacks running on a single 
box.  (but there is only 2 ethernet cables...so you can't have 70 stacks)

 From their viewpoint, treat each stack as a standalone box when dealing with 
them.  Just like standalone boxes, if you have one stack routing to another stack, 
it is the same as one box being routed to another box.

If some stacks need to be passed thru the DMZ to the outside world, just 
identify the IP addresses envolved.

Tom Duerbusch
THD Consulting


Ron Foster at Baldor-ISrfos...@baldor.com  3/30/2011 10:56 AM

Hello listers,

Our company has recently been acquired by another company.  We are at
the point of having to get our two networks to talk to each other.
Before we can do that, we have to comply with certain security rules.
One of them being that the mainframe cannot be exposed to the internet.

We have a couple of zLinux web servers that are running in a couple of
z/VM guests that are connected to our DMZ.  The new folks say this is a
show stopper as far as hooking up the two networks.

The questions I have are:

Is this a common restriction?  That is, you have to have your DMZ based
web servers running on some other platform so that your mainframe is not
exposed to the internet.

Or, the new folks just don't understand the built-in security provided
by the z10 and z\VM 6.1.

I know that we will end up conforming to the rules that the new folks
have, but I was just wondering if the new folks really know what they
are talking about.

Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
.



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Advice on setting up minidisks

[Ron Foster at Baldor-IS]

Everyone,

Thanks for all the advice.

Ron

On 1/13/2011 2:23 PM, Mauro Souza wrote:

On the new projects I work with, we try to allocate mod-3s and mod-9s to zVM
and to Linux filesystem (var, home, usr, etc and so...), and use FCP disks
to everything else, like Oracle databases, webserver logs, NFS area, and
everything it's supposed to grow a lot in the future.

Troubleshooting zVM and Linux installed on 3390 is way easier for me (and
for almost every zVM guy) than on FCP. And creating 600GB of storage area in
3390-3 disks is not a pleasant task... So we mix them.

Mauro
http://mauro.limeiratem.com - registered Linux User: 294521
Scripture is both history, and a love letter from God.


On Thu, Jan 13, 2011 at 5:41 PM, Ron Foster at Baldor-ISrfos...@baldor.com

wrote:
Hello list,

This may have been discussed before...

Way back in deep dark ancient history, we used the Redbook to get
started with Linux under z/VM.  As a result, we carved up our storage
subsystem in to a bunch of mod3 drives.  We put a few mod 9 drives in
the mix.

We added drives to a guest in standard chunks.  That is when storage was
needed by a Linux system, we added a mod9 or mod3 to it.

When that Shark went off lease and we moved to a DS8000, we pretty well
kept the same philosophy.  Only we added a bunch more mod3 and mod 9
drives.

We are a SAP shop and any large databases reside in DB2 on z/OS.  There
are a few large file systems on 3 or 4 of our Linux systems, but for the
most part the drives attached to a Linux system go something like this.
A boot drive.  One to several mod3 drives for swapping (the appropriate
ones have vdisks).  One to several mod3 or mod9 drives for the SAP code
and local files.

We are moving our production drives.  We finally have gotten our
production Linux systems where about half or do very little swapping.

We do not have dirmaint, so we keep up with disk allocations with
dirmaint and a spreadsheet.

Now time has come to migrate to another storage system.  I was wondering
what other folks do.

1. Do they have a whole bunch of mod9 and mod3 drives that they allocate
to their guests?

2. Do they take mod27 drives (someone at SHARE warned me about taking
mod54 drives) and use mdisk to carve them up into something smaller.

Any input would be appreciated.

Thanks,
Ron Foster

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
.



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Advice on setting up minidisks

[Ron Foster at Baldor-IS]

Hello list,

This may have been discussed before...

Way back in deep dark ancient history, we used the Redbook to get
started with Linux under z/VM.  As a result, we carved up our storage
subsystem in to a bunch of mod3 drives.  We put a few mod 9 drives in
the mix.

We added drives to a guest in standard chunks.  That is when storage was
needed by a Linux system, we added a mod9 or mod3 to it.

When that Shark went off lease and we moved to a DS8000, we pretty well
kept the same philosophy.  Only we added a bunch more mod3 and mod 9 drives.

We are a SAP shop and any large databases reside in DB2 on z/OS.  There
are a few large file systems on 3 or 4 of our Linux systems, but for the
most part the drives attached to a Linux system go something like this.
A boot drive.  One to several mod3 drives for swapping (the appropriate
ones have vdisks).  One to several mod3 or mod9 drives for the SAP code
and local files.

We are moving our production drives.  We finally have gotten our
production Linux systems where about half or do very little swapping.

We do not have dirmaint, so we keep up with disk allocations with
dirmaint and a spreadsheet.

Now time has come to migrate to another storage system.  I was wondering
what other folks do.

1. Do they have a whole bunch of mod9 and mod3 drives that they allocate
to their guests?

2. Do they take mod27 drives (someone at SHARE warned me about taking
mod54 drives) and use mdisk to carve them up into something smaller.

Any input would be appreciated.

Thanks,
Ron Foster

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Defining channel bonding of OSA adapters with Yast

[Ron Foster at Baldor-IS]

Hello listers,

We had an OSA adapter go out the other night on our z10.  Our linux
guests running under z/VM did not have any problems when this OSA
adapter went out.  The vswitches they were attached to had multiple
adapters defined to them.  The vswitch just moved things around and they
just kept running as if nothing happened.  (That is until the CE noticed
that our primary and backup OSA adapters that our vswitches used were on
the same physical card.  But that is another story...)

However, we have three Linux LPARS.  They had problems.  The OSA adapter
that went down was their only connection to a particular network.

All of a sudden it seemed to be a good idea to figure out how to do
channel bonding.  Spending a little time with Google, I found a SHARE
presentation (Networking with Linux on System Z) that gave me a setup.
The setup had you issue several commands, and then showed excerpts from
some configuration files.  Since I did not attend the presentation, I
was not sure how much I would need to add to get it to work.

Spending a little more time with Google, I found a post on the list from
Pieter Harder.  It had a complete set of configuration files.  I should
be able to get them to work...

But I am a YaST kind of guy.  I found an article on the Novell
knowledgebase (3815448) as of SLES10 SP2 that showed how to do it on an
Intel system.  I start going through the procedure and see that at a
certain point that I am supposed to add a device type of bond.  My
SLES10 SP3 system does not give me an option of bond.  I get ethernet,
hipersockets, iucv and several others, but no bond.

Has anyone been able to set up channel bonding with YaST?  Or did they
use files like Pieter put in his post?

Thanks,
Ron

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: CRON

[Ron Foster at Baldor-IS]

If running SLES, have you looked at /etc/sysconfig/cron

Mark Pace wrote:

Is there an easy way to make cron not send me an email every time it runs
one of my jobs?  I have one job that runs every 15 mins, and as you may
imagine that generates a lot of mail.  Or is there a way clean up an mbox
without manually doing it?

--
Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: input requested on running SAP on z/Linux

[Ron Foster at Baldor-IS]

Mark,

Is it ok to let this person know we would be willing to talk to him.
(This is the original e-mail.)

Ron

bruce.light...@its.ms.gov wrote:

We are in the research and planning stage of a project that will probably
be an SAP implementation with DB2 as the database back-end.

Currently, we run DB2 on AIX, Linux under z/VM, Linux under VMWare, and on
z/OS ( plus a new Win 2008r2 server).
We also run a passel of WebSphere application servers on AIX and Linux
under VMWare.

With that as background, I am looking for input from current SAP shops on
the process of determining the platform for implementing SAP - both the app
server portion and the DB portion.
Why should I choose/avoid Linux on Z for any portion ( I will admit that I
am biased toward Linux on Z ) and is there a benefit from running on DB2
LUW over DB2 z/OS or vice-versa ?

I have a couple of RedBooks but any decent whitepapers, RedBooks,
RedPieces, etc will be gratefully accepted.

Thanks,
Bruce Lightsey
Mississippi Dept. of Information Technology Services
301 N. Lamar St., Suite 508
Jackson, Ms 39201-1495

mailto:bruce.light...@its.ms.gov

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/




--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Red Hat 5 Update 5 Install Failing on Network

[Ron Foster at Baldor-IS]

William,

I am a SLES person instead of a Red Hat person, but...

We use vswitches for connection our Linux guests to the outside world.
I get similar
problems when I forget to authorize a newly created Linux guest to the
vswitch.

Also, is 512MB enough to do a Red Hat install?  I have had a number of
problems
running the SLES installer with not enough memory.

Ron

Scully, William P wrote:

Sorry for the long email but I cannot seem to get RH 5 Update 5 to
install on z/VM.  Whether I answer the installer's questions by hand or
encode them into the parm file, the results are the same:  I can't seem
to ping the network router:


CP Q V ALL

STORAGE = 512M

XSTORE = none

CPU 00  ID  FF04E00020978000 (BASE) IFL  CPUAFF SUPP

No AP Crypto Queues are available

CONS 0009 ON LDEV L001D   TERM START HOST TCPIPFROM 10.132.9.185

 0009 CL T NOCONT NOHOLD COPY 001READY FORM STANDARD

 0009 TO SCUWI01  RDR DIST GENERAL   FLASHC 000 DEST OFF

 0009 FLASH   CHAR   MDFY   0 FCB   LPP OFF

 0009 3215   NOEOF OPEN 0030 NOKEEP NOMSG   NAME LINUX024 CONSOLE

 0009 SUBCHANNEL = 0017

RDR  000C CL * NOCONT NOHOLD   EOF   READY

 000C 2540 CLOSEDNOKEEP NORESCAN  SUBCHANNEL = 0018

PUN  000D CL A NOCONT NOHOLD COPY 001READY FORM STANDARD

 000D TO LINUX024 PUN DIST GENERAL   DEST OFF

 000D FLASH  000 CHAR   MDFY   0 FCB

 000D 2540   NOEOF CLOSEDNOKEEP NOMSG NONAME

 000D SUBCHANNEL = 0019

PRT  000E CL A NOCONT   HOLD COPY 001READY FORM STANDARD

 000E TO LINUX024 RDR DIST GENERAL   FLASHC 000 DEST OFF

 000E FLASH   CHAR   MDFY   0 FCB   LPP OFF

 000E 1403   NOEOF CLOSEDNOKEEP NOMSG NONAME

 000E SUBCHANNEL = 001A

DASD 0190 3390 VCVR01 R/O107 CYL ON DASD  567A SUBCHANNEL = 001C

DASD 019D 3390 VCVR01 R/O250 CYL ON DASD  567A SUBCHANNEL = 001D

DASD 019E 3390 VCVR19 R/O600 CYL ON DASD  5604 SUBCHANNEL = 001E

DASD 0200 9336 (VDSK) R/W 409600 BLK ON DASD  VDSK SUBCHANNEL = 

DASD 0201 3390 LNX172 R/W   3338 CYL ON DASD  2873 SUBCHANNEL = 0009

DASD 0202 3390 LNX031 R/W   3338 CYL ON DASD  2317 SUBCHANNEL = 000A

OSA  0C00 ON NIC  0C00  UNIT 000 SUBCHANNEL = 0011

 0C00 DEVTYPE OSA CHPID 0E OSD

 0C00 MAC 02-00-C3-00-00-33 CURRENT

 0C00 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE

OSA  0C01 ON NIC  0C00  UNIT 001 SUBCHANNEL = 0012

 0C01 DEVTYPE OSA CHPID 0E OSD

 0C01 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE

OSA  0C02 ON NIC  0C00  UNIT 002 SUBCHANNEL = 0013

 0C02 DEVTYPE OSA CHPID 0E OSD

 0C02 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE

OSA  0D00 ON NIC  0D00  UNIT 000 SUBCHANNEL = 0014

 0D00 DEVTYPE OSA CHPID 0F OSD

 0D00 MAC 02-00-C3-00-00-34 CURRENT

 0D00 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE

OSA  0D01 ON NIC  0D00  UNIT 001 SUBCHANNEL = 0015

 0D01 DEVTYPE OSA CHPID 0F OSD

 0D01 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE

OSA  0D02 ON NIC  0D00  UNIT 002 SUBCHANNEL = 0016

 0D02 DEVTYPE OSA CHPID 0F OSD

 0D02 QDIO-ELIGIBLE   QIOASSIST-ELIGIBLE



rhel55

02 FILES PURGED

 NO FILES CHANGED

RDR FILE 0031 SENT FROM LINUX024 PUN WAS 0031 RECS 075K CPY  001 A
NOHOLD NOKEEP
RDR FILE 0032 SENT FROM LINUX024 PUN WAS 0032 RECS 0008 CPY  001 A
NOHOLD NOKEEP
RDR FILE 0033 SENT FROM LINUX024 PUN WAS 0033 RECS 119K CPY  001 A
NOHOLD NOKEEP
 NO FILES CHANGED

Linux version 2.6.18-194.el5 (mockbu...@s390-005.build.bos.redhat.com)
(gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Tue Ma
r 16 22:05:06 EDT 2010

We are running under VM (64 bit mode)

Detected 1 CPU's

Boot cpu address  0

Built 1 zonelists.  Total pages: 131072

Kernel command line: root=/dev/ram0 ro ip=off ramdisk_size=4 mpath

 DASD=200-20F HOSTNAME=linux024.ca.com

 NETTYPE=qeth IPADDR=141.202.200.124

 SUBCHANNELS=0.0.0C00,0.0.0C01,0.0.0C02

 NETWORK=141.202.200.0 NETMASK=255.255.255.0

 SEARCHDNS=ca.com BROADCAST=141.202.200.255

 GATEWAY=141.202.200.101 DNS=141.202.1.108
MTU=1500
 LAYER2=0

PID hash table entries: 4096 (order: 12, 32768 bytes)

Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)

Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)


Memory: 499200k/524288k available (3412k kernel code, 0k reserved, 2257k
data, 136k init)
Write protected kernel read-only data: 0x356000 - 0x409fff

Calibrating delay loop...

3670.01 BogoMIPS (lpj=18350080)

Security Framework v1.0.0 initialized

SELinux:  Initializing.

selinux_register_security:  Registering secondary module capability

Capability LSM initialized as secondary

Mount-cache hash table entries: 256

cpu 0 phys_idx=0 vers=FF ident=04E000 machine=2097 unused=8000

Brought up 1 CPUs

checking if image is initramfs...

 it is

Freeing initrd 

Re: SMT and cloned DASD

[Ron Foster at Baldor-IS]

Miguel,

We are still SLES10.
We use a technique similar to the one outline in this URL.
http://www.novell.com/support/php/search.do?cmd=displayKCdocType=kcexternalId=7005155sliceId=1docTypeID=DT_TID_1_1dialogID=143913381stateId=0%200%20143909538

Even though it mentions Xen.  It works for z/VM. 


We clone the system.

We modify the hostGUID.

We then register the system.

Ron

Miguel Angel Barajas wrote:

Hi there,


 I'm trying to update 20 SLES10sp2 z390x with SMT 11, but this workloads has been 
cloned with zVM tools, and all the workloads report the same UUID, so, when a second 
SLES are registered, the first registry disappears and the SMT thinks that is 
the same machine but with different IP and Hostname.


 There is a way to chance the UUID on zVM? or how can I workaround this?


Thanks!


Miguel Angel Barajas Hernandez
Data Center Architect
Novell de México
mabara...@novell.com
t +52 55 52842700
f +52 55 52842799
m +52 55 39884315
Certified Linux Administrator
Certified Linux Professional
Certified Linux Engineer
Linux Technical Specialist
Data Center Technical Specialist
Data Center Advanced Technical Specialist
Data Center Sales Specialist 2010
End-User Sales Specialist 2010
Certified Novell Salesperson
Certified Computer Technical Support
Certified Network Support Professional

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


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

SAP Application server size

[Ron Foster at Baldor-IS]

To the SAP folks out there.

Our company is still in the process of assimilating workload from an
acquisition that we made in 2007.  Most of that workload has been going
into our Production ECC system that has 2 batch servers, 3 SD servers,
4 MMPP servers, a FICO server, and an IPP server.  Over the years we
could tweak and adjust the server things to handle the additional workload.

It has now come to the point where the SAP Admin folks want to make the
SD and the MMPP servers 16GB each.  (These servers just run ABAP.
There is no java on these servers.)

I was wondering what size application servers the SAP out there run.  Is
there a point where a SAP application server is too big?  Has anyone hit it?

Should I try to steer the SAP Admin folks towards the idea that we
should make another application server?

Any ideas or comments?

Ron
Baldor Electric Company

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

Re: SLES10 upgrade from SP2 to SP3

[Ron Foster at Baldor-IS]

Just remember to put on all the SP2 patches before you select the move  
to sp3 patch.

Ron

Sent from my iPhone

On Apr 23, 2010, at 1:55 PM, Smith, Ann (ISD, IT) ann.sm...@thehartford.com 
  wrote:

 Once I selected the 'move-to sle10-sp3' it came up with a warning that
 said don't install until you read this:

 http://www.novell.com/support/documentLink.do?externalID=7004640

 So they are providing the doc when you select it !

 -Original Message-
 From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
 Mark Post
 Sent: Friday, April 23, 2010 2:33 PM
 To: LINUX-390@VM.MARIST.EDU
 Subject: Re: SLES10 upgrade from SP2 to SP3

 On 4/23/2010 at 01:48 PM, Smith, Ann (ISD, IT)
 ann.sm...@thehartford.com
 wrote:
 I haven't been able to locate an instructions doc for upgrading from
 SLES10 SP2 to SP3.
 All I could find on the Novell website was a release notes doc.
 Don't know why I'm having so much trouble finding an upgrade doc this
 time around. I must just be brain dead.
 I usually use YaST2 to do upgrades.
 Any help would be greatly appreciated.

 It should be pretty straightforward.  Install all the remaining SP2
 updates, then install the move-to-sles10-sp3 patch.  Once that has
 been completed you should be able to see a whole bunch of SP3 updates.
 Install them and you should be at SP3.


 Mark Post

 --
 For LINUX-390 subscribe / signoff / archive access instructions, send
 email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
 visit http://www.marist.edu/htbin/wlvindex?LINUX-390
 
 This communication, including attachments, is for the exclusive use  
 of addressee and may contain proprietary, confidential and/or  
 privileged information.  If you are not the intended recipient, any  
 use, copying, disclosure, dissemination or distribution is strictly  
 prohibited.  If you are not the intended recipient, please notify  
 the sender immediately by return e-mail, delete this communication  
 and destroy all copies.
 

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

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

Re: Unable to kill process

[Ron Foster at Baldor-IS]

Fernando,

This morning we had what we thought to be a similar problem.  We
gathered all the right people into the same room and set about going
though the steps to kill the process.  This time a kill -9 worked.

As far as the lsof, I did one right after the first step in the
process.  The killing of the DB2 thread.  I was going to do another lsof
if we went through all the other steps and a kill -9 did not work.

Would it still be helpful for me to send you the lsof output that I have.

Thanks,
Ron Foster

Fernando Gieseler wrote:

Ron,

Please, verify what is the PID (process ID) are running the ghost
process.

After this verification, run 'lsof -p PID' and verify which the files
are open.

Understanding which files are open, you can remove file permissions or
debug the problem.

If you can, send-me the result of lsof command.

Have you tried kill -15 ??

Regards,



Fernando Gieseler
_
Technical Sales Specialist for System z
-  Linux and z/VM -
IBM Brasil
fone: +55-51-2131-5848
cel: +55-51-9988-8177
fax: +55-51-2131-5875
ITN: 5 759-5848
T/L: 759-5848
f...@br.ibm.com



From:   Ron Foster at Baldor-IS rfos...@baldor.com
To: LINUX-390@vm.marist.edu
Date:   06/04/2010 12:02
Subject:Re: Unable to kill process
Sent by:Linux on 390 Port LINUX-390@vm.marist.edu






Mark,


 If kill -9 doesn't work then the process is in a system routine that
can be
 cancelled.
Thanks for the info.
 Did you have a problem with disks and/or nfs? (sap process needing to
 complete i/o?)
We happen to have the problem on another SAP application server as I am
typing this.  I have checked all the nfs mounts and they all appear to
be working.  I did not spot messages in /var/log/messages.  The drives
for this system are eckd.  The storage guy has not notified me of any
problems with the storage subsystem.  The z/VM folks here do not have a
z/VM console manager running, so we cannot see if there were any z/vm
console messages come out.

The storage guy is saying that since the storage subsystem did not phone
home, the disks are ok.

 thats a support question if ever I heard one. Contact SAP/IBM. (Which of
 course will lead to a question on maintenace levels of linux and sap.)



Since we are having the problem right now, I contacted our SAP basis
manager and requested that he contact SAP.  I will be opening an SR with
Novell when I get finished with this e-mail.

Looking at the time the process has been running in SAP, it looks like
it started yesterday afternoon shortly after the other process.
Different application server.
 Are you saying that shutdown didn't work either and that you were
forced to
 crash the linux guest?
Yes,

I ended up logging onto the 3270 console.  I did a init 1 to take it
down to single user mode.  The kill did not work, so I did the shutdown
command.  I let it sit a few minutes.  The normal shutdown sequence not
complete.  So I ended up doing a #cp logoff.

 were you alreday in shutdown?
The only shutdown was after I did the init 1.

Thanks,
Ron

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




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

Re: Unable to kill process

[Ron Foster at Baldor-IS]

Shane,

Based on your comment...

We have opened up problems with Novell and SAP.  So far this has
happened on two of our Linux Guests.  We crashed and booted one Monday
night.  We crashed and booted the other one Tuesday night.  (On the off
chance that it might help, last night I took a standalone dump of the
Linux guest in trouble.  So far Novell has not wanted me to send the
dump to them.)

This morning, it looked like we had the same sort of problem happening
on a third Linux guest.  That is we had a SAP dialog process that all
night.   (We have the SAP parameters set to time out a dialog process
after a few minutes.  The timeout did not work.)  The DBAs cancelled
the DB2 thread.  The SAP Administrators issued all the commands thru SAP
to get rid of the process.  They did not work.  The process did not go
away.  Then we tried a kill -9 and the process died.

On the other two occassions, we issued the same commands.  But they were
done independently by people in the different areas in different rooms.
This time everyone was in the same room waiting for the problem to happen...

Thanks for the insight,
Ron

Shane Ginnane wrote:

That is *UN*interruptible sleep.
Programming error , pure and simple.

And yes, it probably really is unkillable.

Shane ...

Ron wrote on 06/04/2010 08:41:15 AM:



I just had to #CP logoff on of our production SAP systems.  It had a SAP
process on it with a process state of D  interruptible sleep.

The sap cancel options would not work.
kill would not work.
kill -9 would not work on it.



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




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

Re: Unable to kill process

[Ron Foster at Baldor-IS]

Fernando,

The problem is happening again.  The process is in state D for
uninterruptable sleep.  I do not want to try a kill -15 at this moment.
I am waiting for Novell to get back to me on what information they might
want to gather.  I have done a lsof.  To keep from cluttering up the
list, I am sending it to you privately.

Thanks for your help,
Ron

Fernando Gieseler wrote:

Ron,

Please, verify what is the PID (process ID) are running the ghost
process.

After this verification, run 'lsof -p PID' and verify which the files
are open.

Understanding which files are open, you can remove file permissions or
debug the problem.

If you can, send-me the result of lsof command.

Have you tried kill -15 ??

Regards,



Fernando Gieseler
_
Technical Sales Specialist for System z
-  Linux and z/VM -
IBM Brasil
fone: +55-51-2131-5848
cel: +55-51-9988-8177
fax: +55-51-2131-5875
ITN: 5 759-5848
T/L: 759-5848
f...@br.ibm.com



From:   Ron Foster at Baldor-IS rfos...@baldor.com
To: LINUX-390@vm.marist.edu
Date:   06/04/2010 12:02
Subject:Re: Unable to kill process
Sent by:Linux on 390 Port LINUX-390@vm.marist.edu






Mark,


 If kill -9 doesn't work then the process is in a system routine that
can be
 cancelled.
Thanks for the info.
 Did you have a problem with disks and/or nfs? (sap process needing to
 complete i/o?)
We happen to have the problem on another SAP application server as I am
typing this.  I have checked all the nfs mounts and they all appear to
be working.  I did not spot messages in /var/log/messages.  The drives
for this system are eckd.  The storage guy has not notified me of any
problems with the storage subsystem.  The z/VM folks here do not have a
z/VM console manager running, so we cannot see if there were any z/vm
console messages come out.

The storage guy is saying that since the storage subsystem did not phone
home, the disks are ok.

 thats a support question if ever I heard one. Contact SAP/IBM. (Which of
 course will lead to a question on maintenace levels of linux and sap.)



Since we are having the problem right now, I contacted our SAP basis
manager and requested that he contact SAP.  I will be opening an SR with
Novell when I get finished with this e-mail.

Looking at the time the process has been running in SAP, it looks like
it started yesterday afternoon shortly after the other process.
Different application server.
 Are you saying that shutdown didn't work either and that you were
forced to
 crash the linux guest?
Yes,

I ended up logging onto the 3270 console.  I did a init 1 to take it
down to single user mode.  The kill did not work, so I did the shutdown
command.  I let it sit a few minutes.  The normal shutdown sequence not
complete.  So I ended up doing a #cp logoff.

 were you alreday in shutdown?
The only shutdown was after I did the init 1.

Thanks,
Ron

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




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

Re: Unable to kill process

[Ron Foster at Baldor-IS]

Barton,

We are not using VMRM on this system.  So it could not be that sort of
problem.

Ron

Barton Robinson wrote:

Any chance VMRM was active and too storage away?

Mark Perry wrote:


Hi Ron,
thats a support question if ever I heard one. Contact SAP/IBM. (Which of
course will lead to a question on maintenace levels of linux and sap.)

If kill -9 doesn't work then the process is in a system routine that can be
cancelled.
Are you saying that shutdown didn't work either and that you were forced to
crash the linux guest?
Did you have a problem with disks and/or nfs? (sap process needing to
complete i/o?)
were you alreday in shutdown?
soemtimes the order that things are shutdoiwn is very important
(users/sap/nfs/filesystem/network).

mark

On 6 April 2010 06:41, Ron Foster at Baldor-IS rfos...@baldor.com wrote:



Hello,

I just had to #CP logoff on of our production SAP systems.  It had a SAP
process on it with a process state of D  interruptible sleep.

The sap cancel options would not work.
kill would not work.
kill -9 would not work on it.

Any ideas on how to avoid having to log off next time.

Ron

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



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





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




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

Re: Unable to kill process

[Ron Foster at Baldor-IS]

Mark,



If kill -9 doesn't work then the process is in a system routine that can be
cancelled.

Thanks for the info.

Did you have a problem with disks and/or nfs? (sap process needing to
complete i/o?)

We happen to have the problem on another SAP application server as I am
typing this.  I have checked all the nfs mounts and they all appear to
be working.  I did not spot messages in /var/log/messages.  The drives
for this system are eckd.  The storage guy has not notified me of any
problems with the storage subsystem.  The z/VM folks here do not have a
z/VM console manager running, so we cannot see if there were any z/vm
console messages come out.

The storage guy is saying that since the storage subsystem did not phone
home, the disks are ok.


thats a support question if ever I heard one. Contact SAP/IBM. (Which of
course will lead to a question on maintenace levels of linux and sap.)




Since we are having the problem right now, I contacted our SAP basis
manager and requested that he contact SAP.  I will be opening an SR with
Novell when I get finished with this e-mail.

Looking at the time the process has been running in SAP, it looks like
it started yesterday afternoon shortly after the other process.
Different application server.

Are you saying that shutdown didn't work either and that you were forced to
crash the linux guest?

Yes,

I ended up logging onto the 3270 console.  I did a init 1 to take it
down to single user mode.  The kill did not work, so I did the shutdown
command.  I let it sit a few minutes.  The normal shutdown sequence not
complete.  So I ended up doing a #cp logoff.


were you alreday in shutdown?

The only shutdown was after I did the init 1.

Thanks,
Ron

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

Unable to kill process

[Ron Foster at Baldor-IS]

Hello,

I just had to #CP logoff on of our production SAP systems.  It had a SAP
process on it with a process state of D  interruptible sleep.

The sap cancel options would not work.
kill would not work.
kill -9 would not work on it.

Any ideas on how to avoid having to log off next time.

Ron

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

Re: How to tell what logical volume is called dm-7

[Ron Foster at Baldor-IS]

Pieter and Bruce,

Thanks for the info.

Ron

Harder, Pieter wrote:

lvdisplay -m /dev/VG name/LV name
will display the physical volumes and extents for a logical volume.

Pvscan will tell what physical volumes belongs to what volume group, if any.

Lvscan will tell what logical volumes are defined.

Best regards,
Pieter Harder

pieter.har...@brabantwater.nl
tel  +31-73-6837133 / +31-6-47272537


-Oorspronkelijk bericht-
Van: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Namens Bruce Hayden
Verzonden: woensdag 24 februari 2010 15:34
Aan: LINUX-390@VM.MARIST.EDU
Onderwerp: Re: How to tell what logical volume is called dm-7

The only way I figured out how to do it is to compare the minor
numbers of the /dev/dm-* files with the /dev/mapper/* files and match
them up.

On Wed, Feb 24, 2010 at 9:14 AM, Ron Foster at Baldor-IS
rfos...@baldor.com wrote:


Hello list,

We are having a problem with a file system.  We are using lvm.  The
message is telling us we have a problem with dm-7.  How do we tell which
logical volume is represented by dm-7.

Thanks,
ROn

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






--
Bruce Hayden
z/VM and Linux on System z ATS
IBM, Endicott, NY

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

Brabant Water N.V.
Postbus 1068
5200 BC  's-Hertogenbosch
http://www.brabantwater.nl
Handelsregister: 16005077

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




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

How to tell what logical volume is called dm-7

[Ron Foster at Baldor-IS]

Hello list,

We are having a problem with a file system.  We are using lvm.  The
message is telling us we have a problem with dm-7.  How do we tell which
logical volume is represented by dm-7.

Thanks,
ROn

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

Oops message in /var/log/messages

[Ron Foster at Baldor-IS]

Everyone,

This is something I have never ran into.
It is coming out of a system running SAP.  (Our main test system.)
# uname -a
Linux bus0104 2.6.16.60-0.34-default #1 SMP Fri Jan 16 14:59:01 UTC 2009
s390x s390x s390x GNU/Linux


Any ideas:



Feb  4 10:05:45 bus0104g syslog-ng[1630]: STATS: dropped 0
Feb  4 10:08:34 bus0104g kernel: Unable to handle kernel pointer
dereference at virtual kernel address fffe76ffc000
Feb  4 10:08:34 bus0104g kernel: Oops: 0038 [#1]
Feb  4 10:08:34 bus0104g kernel: CPU:0Not tainted
Feb  4 10:08:34 bus0104g kernel: Process BTS_04_BTC_W19 (pid: 14622,
task: 0001104e0628, ksp: 00013328b668)
Feb  4 10:08:34 bus0104g kernel: Krnl PSW : 070420018000
0033662a (memcpy+0x16/0x28)
Feb  4 10:08:34 bus0104g kernel: Krnl GPRS: fffe76ffcd28
0010 00017d7b2018 fffe76ffcd28
Feb  4 10:08:34 bus0104g kernel:0010
14aaad40 d5d1 
Feb  4 10:08:34 bus0104g kernel:0f07eea0
0001 00013328b988 00017db23240
Feb  4 10:08:34 bus0104g kernel:00017d7b2018
0010 00018091a9b4 00013328b500
Feb  4 10:08:34 bus0104g kernel: Krnl Code: a8 c0 00 00 a7 14 ff fe eb
cd f0 78 00 04 07 fe 07 07 b9 04
Feb  4 10:08:34 bus0104g kernel: Call Trace:
Feb  4 10:08:34 bus0104g kernel: ([000180945734]
internal_insert_key+0x19c/0x1ac [reiserfs])
Feb  4 10:08:34 bus0104g kernel:  [0001809478cc]
balance_internal+0x4ac/0x1f78 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [00018091dff6]
do_balance+0x361a/0x3700 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [00018094e178]
reiserfs_cut_from_item+0x12b4/0x1400 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [00018091f4c4]
reiserfs_unlink+0x76c/0x8d8 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [0024e354]
sys_unlink+0x1f0/0x300
Feb  4 10:08:34 bus0104g kernel:  [00115da4] sysc_noemu+0x10/0x16
Feb  4 10:08:34 bus0104g kernel:  [020001439702] 0x20001439702
Feb  4 10:08:34 bus0104g kernel:
Feb  4 10:08:34 bus0104g kernel:  Badness in do_exit at kernel/exit.c:842
Feb  4 10:08:34 bus0104g kernel: 00013328b090 0401
3328b090 00013328b1a0
Feb  4 10:08:34 bus0104g kernel:04013328b080
0404 0404 00105b42
Feb  4 10:08:34 bus0104g kernel:
d5d1 00013328b458 01c0
Feb  4 10:08:34 bus0104g kernel:00013328b458
00010008 000e 00013328b188
Feb  4 10:08:34 bus0104g kernel:004a9520
00105b42 00013328b110 00013328b150
Feb  4 10:08:34 bus0104g kernel: Call Trace:
Feb  4 10:08:34 bus0104g kernel: ([00105b5e]
dump_stack+0x2aa/0x364)
Feb  4 10:08:34 bus0104g kernel:  [0014f9c2] do_exit+0x62/0x1510
Feb  4 10:08:34 bus0104g kernel:  [00104cb2] die+0x10a/0x10c
Feb  4 10:08:34 bus0104g kernel:  [00102248]
do_dat_exception+0x754/0x858
Feb  4 10:08:34 bus0104g kernel:  [00115daa] sysc_return+0x0/0x10
Feb  4 10:08:34 bus0104g kernel:  [0033662a] memcpy+0x16/0x28
Feb  4 10:08:34 bus0104g kernel: ([000180945734]
internal_insert_key+0x19c/0x1ac [reiserfs])
Feb  4 10:08:34 bus0104g kernel:  [0001809478cc]
balance_internal+0x4ac/0x1f78 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [00018091dff6]
do_balance+0x361a/0x3700 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [00018094e178]
reiserfs_cut_from_item+0x12b4/0x1400 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [00018091f4c4]
reiserfs_unlink+0x76c/0x8d8 [reiserfs]
Feb  4 10:08:34 bus0104g kernel:  [0024e354]
sys_unlink+0x1f0/0x300
Feb  4 10:08:34 bus0104g kernel:  [00115da4] sysc_noemu+0x10/0x16
Feb  4 10:08:34 bus0104g kernel:  [020001439702] 0x20001439702
Feb  4 10:08:34 bus0104g kernel:

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

Re: Oops message in /var/log/messages

[Ron Foster at Baldor-IS]

Mark,

I have followed your suggestion.

Ron

Mark Post wrote:

On 2/4/2010 at 11:53 AM, Ron Foster at Baldor-IS rfos...@baldor.com wrote:


Any ideas:



Feb  4 10:05:45 bus0104g syslog-ng[1630]: STATS: dropped 0
Feb  4 10:08:34 bus0104g kernel: Unable to handle kernel pointer
dereference at virtual kernel address fffe76ffc000
Feb  4 10:08:34 bus0104g kernel: Oops: 0038 [#1]
Feb  4 10:08:34 bus0104g kernel: CPU:0Not tainted
Feb  4 10:08:34 bus0104g kernel: Process BTS_04_BTC_W19 (pid: 14622,
task: 0001104e0628, ksp: 00013328b668)
Feb  4 10:08:34 bus0104g kernel: Krnl PSW : 070420018000
0033662a (memcpy+0x16/0x28)



Any kernel oops should be reported immediately to your support provider.  An 
oops is a very severe problem that needs to get fixed.


Mark Post

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




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