Hobbit problem with bbtest

2009-04-01 Thread Rempel, Horst
Hello everybody,
Since 7 month I use hobbit to observe the availability of our VSE, VM
and Linux systems running on the z9.
The hobbit-server 4.2.0 is running in sles10 sp2.
Everything worked well until last friday. In the Current Staus screen
the icons for bbd, bbtest, http and the complete conn column changed
from green to purple (no report).
After a system reboot everything seems to be ok again because all icons
were green.
But after some time the problem was back, the icons for bbd, bbtest,
http and the complete conn column changed from green to purple (no
report).
When I log on to hobbit and run 'bbtest-net' manually all purple icons
change to green except the bbtest icon (still purple).
After a while the already mentioned icon will change to purple again.

So it looks to me that bbtest-net will not restart after the interval of
600 sec.
But why ? I cannot see any errormessage. There is enough space in the
filesystem. 
My colleagues promissed me, that they have nothing changed.
I have no idea what happended. Every hint is appreciated.

kind regards Horst Rempel 
 
 

--
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: s390 repositories for RHEL

2009-04-01 Thread Mark Perry
Erling Ringen Elvsrud wrote:
 Hello list,

 I need a few packages that is not included in RHEL. First and foremost
 Puppet and dependencies which is at least ruby-rpm and ruby-shadow if
 I remember correctly.

 I have not found any s390 packages in the well known repositories like
 EPEL, rpmforge or dag. Do you know any repositories that
 contain s390 binary packages for RHEL?

 I could build them myself from the EPEL srpms, but if binary packages
 (from a reasonable source) exists I prefer to use that.

Interestingly (maybe not for you), SLES-11 has a puppet rpm:

Name: puppet   Relocations: (not relocatable)
Version : 0.24.5Vendor: SUSE LINUX
Products GmbH, Nuernberg, Germany
Release : 5.6   Build Date: Wed 25 Feb 2009
18:11:34 CET
Install Date: (not installed)   Build Host: s390z18
Group   : Productivity/Networking/System   Source RPM:
puppet-0.24.5-5.6.src.rpm
Size: 1624845  License: GPL v2 or later
Signature   : RSA/8, Wed 25 Feb 2009 18:11:38 CET, Key ID e3a5c360307e3d54
Packager: http://bugs.opensuse.org
URL : http://reductivelabs.com/projects/puppet/
Summary : A network tool for managing many disparate systems
Description :
Puppet lets you centrally manage every important aspect of your system
using a cross-platform specification language that manages all the
separate elements normally aggregated in different files, like users,
cron jobs, and hosts, along with obviously discrete elements like
packages, services, and files.
Distribution: SUSE Linux Enterprise 11

Name: puppet-serverRelocations: (not relocatable)
Version : 0.24.5Vendor: SUSE LINUX
Products GmbH, Nuernberg, Germany
Release : 5.6   Build Date: Wed 25 Feb 2009
18:11:34 CET
Install Date: (not installed)   Build Host: s390z18
Group   : Productivity/Networking/System   Source RPM:
puppet-0.24.5-5.6.src.rpm
Size: 22708License: GPL v2 or later
Signature   : RSA/8, Wed 25 Feb 2009 18:11:38 CET, Key ID e3a5c360307e3d54
Packager: http://bugs.opensuse.org
URL : http://reductivelabs.com/projects/puppet/
Summary : A network tool for managing many disparate systems
Description :
Puppet lets you centrally manage every important aspect of your system
using a cross-platform specification language that manages all the
separate elements normally aggregated in different files, like users,
cron jobs, and hosts, along with obviously discrete elements like
packages, services, and files.
Distribution: SUSE Linux Enterprise 11

mark

--
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


s390 repositories for RHEL

2009-04-01 Thread Erling Ringen Elvsrud
Hello list,

I need a few packages that is not included in RHEL. First and foremost
Puppet and dependencies which is at least ruby-rpm and ruby-shadow if
I remember correctly.

I have not found any s390 packages in the well known repositories like
EPEL, rpmforge or dag. Do you know any repositories that
contain s390 binary packages for RHEL?

I could build them myself from the EPEL srpms, but if binary packages
(from a reasonable source) exists I prefer to use that.

Best regards,

Erling Ringen Elvsrud

--
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: Hobbit problem with bbtest

2009-04-01 Thread Rich Smrcina

Horst,

If you also notice that the graphs aren't accumulating any data then the
filesystem may be out of inodes.  Issue df -i to check.  I will run into
this problem occasionally, even though the filesystem looks good otherwise.

The Hobbit mailing list and archive will also be a good source for
debugging this.  I might suggest taking this question there.

Rempel, Horst wrote:

Hello everybody,
Since 7 month I use hobbit to observe the availability of our VSE, VM
and Linux systems running on the z9.
The hobbit-server 4.2.0 is running in sles10 sp2.
Everything worked well until last friday. In the Current Staus screen
the icons for bbd, bbtest, http and the complete conn column changed
from green to purple (no report).
After a system reboot everything seems to be ok again because all icons
were green.
But after some time the problem was back, the icons for bbd, bbtest,
http and the complete conn column changed from green to purple (no
report).
When I log on to hobbit and run 'bbtest-net' manually all purple icons
change to green except the bbtest icon (still purple).
After a while the already mentioned icon will change to purple again.

So it looks to me that bbtest-net will not restart after the interval of
600 sec.
But why ? I cannot see any errormessage. There is enough space in the
filesystem.
My colleagues promissed me, that they have nothing changed.
I have no idea what happended. Every hint is appreciated.

kind regards Horst Rempel



--
Rich Smrcina
Phone: 414-491-6001
http://www.linkedin.com/in/richsmrcina

Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009

--
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


AW: Hobbit problem with bbtest

2009-04-01 Thread Rempel, Horst
Hello Rich,
when I do df -i I see that there are a lot of free inodes.

lx100:~ # df -i
FilesystemInodes   IUsed   IFree IUse% Mounted on
/dev/dasda1   1313285995  1253335% /
udev   30862 303   305591% /dev
/dev/mapper/system-lvhome
  262144  99  2620451% /home
/dev/mapper/system-lvopt
  524288   30895  4933936% /opt
/dev/mapper/system-lvsrv
  131072  72  1310001% /srv
/dev/mapper/system-lvtmp
  262144  34  2621101% /tmp
/dev/mapper/system-lvusr
  524288   63293  460995   13% /usr
/dev/mapper/system-lvvar
  262144   17067  2450777% /var
/dev/mapper/data-lvdata1
 35974402774 35946661% /srv/data

So this is not the problem.
I will subscribe to hobbit mailing list tomorrow.
Thank you. 
kind regards 
Horst  

-Ursprüngliche Nachricht-
Von: Linux on 390 Port [mailto:linux-...@vm.marist.edu] Im Auftrag von Rich 
Smrcina
Gesendet: Mittwoch, 1. April 2009 13:44
An: LINUX-390@VM.MARIST.EDU
Betreff: Re: Hobbit problem with bbtest

Horst,

If you also notice that the graphs aren't accumulating any data then the 
filesystem may be out of inodes.  Issue df -i to check.  I will run into this 
problem occasionally, even though the filesystem looks good otherwise.

The Hobbit mailing list and archive will also be a good source for debugging 
this.  I might suggest taking this question there.

Rempel, Horst wrote:
 Hello everybody,
 Since 7 month I use hobbit to observe the availability of our VSE, VM 
 and Linux systems running on the z9.
 The hobbit-server 4.2.0 is running in sles10 sp2.
 Everything worked well until last friday. In the Current Staus screen 
 the icons for bbd, bbtest, http and the complete conn column changed 
 from green to purple (no report).
 After a system reboot everything seems to be ok again because all 
 icons were green.
 But after some time the problem was back, the icons for bbd, bbtest, 
 http and the complete conn column changed from green to purple (no 
 report).
 When I log on to hobbit and run 'bbtest-net' manually all purple icons 
 change to green except the bbtest icon (still purple).
 After a while the already mentioned icon will change to purple again.

 So it looks to me that bbtest-net will not restart after the interval 
 of 600 sec.
 But why ? I cannot see any errormessage. There is enough space in the 
 filesystem.
 My colleagues promissed me, that they have nothing changed.
 I have no idea what happended. Every hint is appreciated.

 kind regards Horst Rempel


--
Rich Smrcina
Phone: 414-491-6001
http://www.linkedin.com/in/richsmrcina

Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009

--
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


Formatting 3390-9 problem with RedHat

2009-04-01 Thread Bauer, Bobby (NIH/CIT) [E]
Suddenly this morning I'm having trouble formatting a 3390-9 in compatibility 
mode. After formatting the device under VM with cpfmtxa and examining the vtoc 
with IEHLIST, it is as expected, it tells me there is a permanent I/O error.





Attaching the device to a guest and formatting with:



dasdfmt -v -b 4096 -d cdl -f /dev/dasdg  -l ncial5

Retrieving disk geometry...

Drive Geometry: 10017 Cylinders * 15 Heads =  150255 Tracks



I am going to format the device /dev/dasdg in the following way:

   Device number of device : 0x204

   Labelling device: yes

   Disk label  : VOL1

   Disk identifier : NCIAL5

   Extent start (trk no)   : 0

   Extent end (trk no) : 150254

   Compatible Disk Layout  : yes

   Blocksize   : 4096



--- ATTENTION! ---

All data of that device will be lost.

Type yes to continue, no will leave the disk untouched: yes

Formatting the device. This may take a while (get yourself a coffee).

Detaching the device...

Invalidate first track...

formatting tracks complete...

Revalidate first track...

Re-accessing the device...

Finished formatting the device.

Retrieving dasd information... ok

Writing empty bootstrap...

Writing label...

Writing VTOC... ok

Rereading the partition table... ok



Re-examining the vtoc I now see valid allocation which from experience tells me 
a volume restore will not result in a valid volume.



I've used these procedures maybe 100 times. Any ideas?





Bobby Bauer

Center for Information Technology

National Institutes of Health

Bethesda, MD 20892-5628

301-594-7474







--
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: Formatting 3390-9 problem with RedHat

2009-04-01 Thread Scott Rohling
Are you dedicating/attaching volumes to this guest?  If they are minidisks,
then you've been given full pack minidisks which include cylinder 0 (note
the 10017 size) ..  and Linux is formatting the dasd label..

If they are dedicated volumes - then I'm not sure how it's going to act from
a z/VM point of view in terms of a valid VTOC.

Scott

On Wed, Apr 1, 2009 at 7:40 AM, Bauer, Bobby (NIH/CIT) [E] 
baue...@mail.nih.gov wrote:

 Suddenly this morning I'm having trouble formatting a 3390-9 in
 compatibility mode. After formatting the device under VM with cpfmtxa and
 examining the vtoc with IEHLIST, it is as expected, it tells me there is a
 permanent I/O error.





 Attaching the device to a guest and formatting with:



 dasdfmt -v -b 4096 -d cdl -f /dev/dasdg  -l ncial5

 Retrieving disk geometry...

 Drive Geometry: 10017 Cylinders * 15 Heads =  150255 Tracks



 I am going to format the device /dev/dasdg in the following way:

   Device number of device : 0x204

   Labelling device: yes

   Disk label  : VOL1

   Disk identifier : NCIAL5

   Extent start (trk no)   : 0

   Extent end (trk no) : 150254

   Compatible Disk Layout  : yes

   Blocksize   : 4096



 --- ATTENTION! ---

 All data of that device will be lost.

 Type yes to continue, no will leave the disk untouched: yes

 Formatting the device. This may take a while (get yourself a coffee).

 Detaching the device...

 Invalidate first track...

 formatting tracks complete...

 Revalidate first track...

 Re-accessing the device...

 Finished formatting the device.

 Retrieving dasd information... ok

 Writing empty bootstrap...

 Writing label...

 Writing VTOC... ok

 Rereading the partition table... ok



 Re-examining the vtoc I now see valid allocation which from experience
 tells me a volume restore will not result in a valid volume.



 I've used these procedures maybe 100 times. Any ideas?





 Bobby Bauer

 Center for Information Technology

 National Institutes of Health

 Bethesda, MD 20892-5628

 301-594-7474







 --
 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: Formatting 3390-9 problem with RedHat

2009-04-01 Thread Bauer, Bobby (NIH/CIT) [E]
The devices are attached, full volume minidisk. As I understand it, yes, Linux 
is changing the label but it has never exhibited this behavior of changing the 
layout of the vtoc. Saying that would imply maybe some maintenance has changed 
the behavior.


Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474



-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott 
Rohling
Sent: Wednesday, April 01, 2009 9:51 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Formatting 3390-9 problem with RedHat

Are you dedicating/attaching volumes to this guest?  If they are minidisks,
then you've been given full pack minidisks which include cylinder 0 (note
the 10017 size) ..  and Linux is formatting the dasd label..

If they are dedicated volumes - then I'm not sure how it's going to act from
a z/VM point of view in terms of a valid VTOC.

Scott

On Wed, Apr 1, 2009 at 7:40 AM, Bauer, Bobby (NIH/CIT) [E] 
baue...@mail.nih.gov wrote:

 Suddenly this morning I'm having trouble formatting a 3390-9 in
 compatibility mode. After formatting the device under VM with cpfmtxa and
 examining the vtoc with IEHLIST, it is as expected, it tells me there is a
 permanent I/O error.





 Attaching the device to a guest and formatting with:



 dasdfmt -v -b 4096 -d cdl -f /dev/dasdg  -l ncial5

 Retrieving disk geometry...

 Drive Geometry: 10017 Cylinders * 15 Heads =  150255 Tracks



 I am going to format the device /dev/dasdg in the following way:

   Device number of device : 0x204

   Labelling device: yes

   Disk label  : VOL1

   Disk identifier : NCIAL5

   Extent start (trk no)   : 0

   Extent end (trk no) : 150254

   Compatible Disk Layout  : yes

   Blocksize   : 4096



 --- ATTENTION! ---

 All data of that device will be lost.

 Type yes to continue, no will leave the disk untouched: yes

 Formatting the device. This may take a while (get yourself a coffee).

 Detaching the device...

 Invalidate first track...

 formatting tracks complete...

 Revalidate first track...

 Re-accessing the device...

 Finished formatting the device.

 Retrieving dasd information... ok

 Writing empty bootstrap...

 Writing label...

 Writing VTOC... ok

 Rereading the partition table... ok



 Re-examining the vtoc I now see valid allocation which from experience
 tells me a volume restore will not result in a valid volume.



 I've used these procedures maybe 100 times. Any ideas?





 Bobby Bauer

 Center for Information Technology

 National Institutes of Health

 Bethesda, MD 20892-5628

 301-594-7474







 --
 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: Formatting 3390-9 problem with RedHat

2009-04-01 Thread Alan Altmark
On Wednesday, 04/01/2009 at 09:56 EDT, Scott Rohling
scott.rohl...@gmail.com wrote:
 Are you dedicating/attaching volumes to this guest?  If they are
minidisks,
 then you've been given full pack minidisks which include cylinder 0
(note
 the 10017 size) ..  and Linux is formatting the dasd label..

 If they are dedicated volumes - then I'm not sure how it's going to act
from
 a z/VM point of view in terms of a valid VTOC.

z/VM doesn't care about the VTOC.  All we care about is the volser.
CPFMTXA places a VTOC on a volume simply to keep z/OS a z/VSE from
allocating datasets on the volume (and it is part of a VOL1 standard
label).

The interesting part of Bobby's post is:
  After formatting the device under VM with cpfmtxa and
  examining the vtoc with IEHLIST, it is as expected, it tells me there
is a
  permanent I/O error.

Bobby: It isn't clear to me what is telling you there is a permanent I/O
error.  IEHLIST?  Linux? What was the I/O error?

Alan Altmark
z/VM Development
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


Re: Formatting 3390-9 problem with RedHat

2009-04-01 Thread Bauer, Bobby (NIH/CIT) [E]
The message comes from IEHLIST

IEH108I REQUEST TERMINATED --- PERMANENT I/O ERROR WHILE READING DATA SET

Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474



-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Alan 
Altmark
Sent: Wednesday, April 01, 2009 11:25 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Formatting 3390-9 problem with RedHat

On Wednesday, 04/01/2009 at 09:56 EDT, Scott Rohling
scott.rohl...@gmail.com wrote:
 Are you dedicating/attaching volumes to this guest?  If they are
minidisks,
 then you've been given full pack minidisks which include cylinder 0
(note
 the 10017 size) ..  and Linux is formatting the dasd label..

 If they are dedicated volumes - then I'm not sure how it's going to act
from
 a z/VM point of view in terms of a valid VTOC.

z/VM doesn't care about the VTOC.  All we care about is the volser.
CPFMTXA places a VTOC on a volume simply to keep z/OS a z/VSE from
allocating datasets on the volume (and it is part of a VOL1 standard
label).

The interesting part of Bobby's post is:
  After formatting the device under VM with cpfmtxa and
  examining the vtoc with IEHLIST, it is as expected, it tells me there
is a
  permanent I/O error.

Bobby: It isn't clear to me what is telling you there is a permanent I/O
error.  IEHLIST?  Linux? What was the I/O error?

Alan Altmark
z/VM Development
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 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: Formatting 3390-9 problem with RedHat

2009-04-01 Thread Bruce Hayden
I think you need to also run fdasd to create the partition(s).  For
example, fdasd -a /dev/dasdg will create 1 partition for the whole
disk.

On Wed, Apr 1, 2009 at 9:40 AM, Bauer, Bobby (NIH/CIT) [E]
baue...@mail.nih.gov wrote:
 Suddenly this morning I'm having trouble formatting a 3390-9 in compatibility 
 mode. After formatting the device under VM with cpfmtxa and examining the 
 vtoc with IEHLIST, it is as expected, it tells me there is a permanent I/O 
 error.





 Attaching the device to a guest and formatting with:



 dasdfmt -v -b 4096 -d cdl -f /dev/dasdg  -l ncial5

 Retrieving disk geometry...

 Drive Geometry: 10017 Cylinders * 15 Heads =  150255 Tracks



 I am going to format the device /dev/dasdg in the following way:

   Device number of device : 0x204

   Labelling device        : yes

   Disk label              : VOL1

   Disk identifier         : NCIAL5

   Extent start (trk no)   : 0

   Extent end (trk no)     : 150254

   Compatible Disk Layout  : yes

   Blocksize               : 4096



 --- ATTENTION! ---

 All data of that device will be lost.

 Type yes to continue, no will leave the disk untouched: yes

 Formatting the device. This may take a while (get yourself a coffee).

 Detaching the device...

 Invalidate first track...

 formatting tracks complete...

 Revalidate first track...

 Re-accessing the device...

 Finished formatting the device.

 Retrieving dasd information... ok

 Writing empty bootstrap...

 Writing label...

 Writing VTOC... ok

 Rereading the partition table... ok



 Re-examining the vtoc I now see valid allocation which from experience tells 
 me a volume restore will not result in a valid volume.



 I've used these procedures maybe 100 times. Any ideas?





 Bobby Bauer

 Center for Information Technology

 National Institutes of Health

 Bethesda, MD 20892-5628

 301-594-7474







 --
 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
Linux on System z Advanced Technical Support
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


Re: Solaris v. Linux

2009-04-01 Thread Kirk Wolf
This may be a well-worn topic here, and if so I apologize...

What about GPL-licensed code using proprietary (closed) instructions and
hipervisor features (DIAG, etc)?
Aren't micro/millicode and zVM hipervisor vectors the new OCO  with
respect to Linux and Solaris on z?

I can guess what RMS would say, but IMO kernel modules that use closed
instructions should be considered non-free.   This would have nasty
implications.

Kirk Wolf
Dovetailed Technologies
http://dovetail.com


On Tue, Mar 31, 2009 at 9:24 PM, John Summerfield 
deb...@herakles.homelinux.org wrote:


 However, sometimes licence conflicts determine what can be done.
 GPL-licence code cannot be mixed with code released under other licences
  - any that keep source code secret for starters. It is not open to
 Oracle to incorporate code from bash into Oracle. It's not permissible
 to alter the Linux kernel and release the result without source code,
 and companies have been sued sucessfully for this violation. Ask Dlink.

 Its also possible for a licence to prohibit release of source code. MS
 owns large parts of OS/2.

 --

 Cheers
 John

 -- spambait
 1...@coco.merseine.nu  z1...@coco.merseine.nu
 -- Advice
 http://webfoot.com/advice/email.top.php
 http://www.catb.org/~esr/faqs/smart-questions.htmlhttp://www.catb.org/%7Eesr/faqs/smart-questions.html
 http://support.microsoft.com/kb/555375

 You cannot reply off-list:-)

 --
 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: Formatting 3390-9 problem with RedHat

2009-04-01 Thread Bauer, Bobby (NIH/CIT) [E]
Problem resolved. I didn't follow my procedures. I evidently forgot to do a 
DIRECTXA command under VM and when I attached the volume to Linux it saw tracks 
0 thru 10016. 
The VM directory only presents tracks 1 thru 10016. 

Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474



-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Scott 
Rohling
Sent: Wednesday, April 01, 2009 9:51 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Formatting 3390-9 problem with RedHat

Are you dedicating/attaching volumes to this guest?  If they are minidisks,
then you've been given full pack minidisks which include cylinder 0 (note
the 10017 size) ..  and Linux is formatting the dasd label..

If they are dedicated volumes - then I'm not sure how it's going to act from
a z/VM point of view in terms of a valid VTOC.

Scott

On Wed, Apr 1, 2009 at 7:40 AM, Bauer, Bobby (NIH/CIT) [E] 
baue...@mail.nih.gov wrote:

 Suddenly this morning I'm having trouble formatting a 3390-9 in
 compatibility mode. After formatting the device under VM with cpfmtxa and
 examining the vtoc with IEHLIST, it is as expected, it tells me there is a
 permanent I/O error.





 Attaching the device to a guest and formatting with:



 dasdfmt -v -b 4096 -d cdl -f /dev/dasdg  -l ncial5

 Retrieving disk geometry...

 Drive Geometry: 10017 Cylinders * 15 Heads =  150255 Tracks



 I am going to format the device /dev/dasdg in the following way:

   Device number of device : 0x204

   Labelling device: yes

   Disk label  : VOL1

   Disk identifier : NCIAL5

   Extent start (trk no)   : 0

   Extent end (trk no) : 150254

   Compatible Disk Layout  : yes

   Blocksize   : 4096



 --- ATTENTION! ---

 All data of that device will be lost.

 Type yes to continue, no will leave the disk untouched: yes

 Formatting the device. This may take a while (get yourself a coffee).

 Detaching the device...

 Invalidate first track...

 formatting tracks complete...

 Revalidate first track...

 Re-accessing the device...

 Finished formatting the device.

 Retrieving dasd information... ok

 Writing empty bootstrap...

 Writing label...

 Writing VTOC... ok

 Rereading the partition table... ok



 Re-examining the vtoc I now see valid allocation which from experience
 tells me a volume restore will not result in a valid volume.



 I've used these procedures maybe 100 times. Any ideas?





 Bobby Bauer

 Center for Information Technology

 National Institutes of Health

 Bethesda, MD 20892-5628

 301-594-7474







 --
 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: Solaris v. Linux

2009-04-01 Thread David Boyes
On 4/1/09 11:36 AM, Kirk Wolf k...@dovetail.com wrote:
 
 What about GPL-licensed code using proprietary (closed) instructions and
 hipervisor features (DIAG, etc)?
 Aren't micro/millicode and zVM hipervisor vectors the new OCO  with
 respect to Linux and Solaris on z?

Thus the complete lack of comments in the QDIO code in Linux and the minimal
formatting. Just this side of closed-source.

--
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: SUSE on Native LPAR

2009-04-01 Thread Martin, Larry D
I have made no progress.  I do the initial load from the HMC and all is well.  
I specify NFS and point to a Linux desktop via IP address.

On the desktop I have /sles10sp1/cd1 (..cd2; ..cd3; ..cd4)and I have started 
the NFS Server and exported /sles10sp1.

All that I can get is an error = -1 in return.  I have tried both with punch a 
hole in the firewall and without with the results being identical.  I have 
looked in /var/log but do not see anything that makes any sense to me.

Do I need to export the sub-directories?

I actually did this a year ago but the install never completed because of 
insufficient memory on our z890.  The memory issue is resolved but I can't seem 
to get the install going again.

I would appreciate any advice (but please remember that I am a Linux novice and 
do not understand all of the jargon).

Thanks,   .Larry 

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Ceruti, 
Gerard G
Sent: Thursday, March 26, 2009 6:16 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SUSE on Native LPAR

Hi Martin

This is how I have done all my installs, initial boot off the HMC CD, then 
point to an NFS server ( SuSE PC) I have not been unable to get FTP work, but 
NFS works great, 
check the NFS exports are all defined correctly,
Have you checked  /var/log/messages on the PC for any error messages.

The only other problem I had was with the IP address of the zLinux system, it  
had to have the same subnet at the first router it connected to.

Regards
Gerard Ceruti
may the 'z' be with you

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Martin, 
Larry D
Sent: 25 March 2009 20:53
To: LINUX-390@VM.MARIST.EDU
Subject: SUSE on Native LPAR

I am very new to Linux and am trying to install Linux on an LAPR on a
z9BC.

 

I can load the initial Kernel by putting the CD (CD1) into the CD-ROM
drive on the HMC and perform a Lad from CD.

 

After setting up the network the Linux kernel wants to read the rest of
CD1.  If I tell him to use the HMC CD-ROM the response is Unable to
load (not an exact quote).

 

I have tried to use NFS on a desktop which has SUSE 10 installed (about
a year ago).  I get a error saying the request was rejected error = -1.

 

I have also tried using SMB to point to the CD reader on my Windows
desktop and get the same response as above (both of these take a few
minutes to return).

 

Can someone who has done this give me an idea as to what I am doing
wrong?

 

Thanks,   .Larry

 

Ps. Small shop - no money - VM not an option.

 

Larry D. Martin

Mainframe Systems Support

Office of Information Technology and Communications

301.883.7335

 



..
This E-mail and any of its attachments may contain Prince George's County 
Government or Prince George's County 7th Judicial Circuit Court proprietary 
information, which is privileged and confidential. This E-mail is intended 
solely for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.

_

Standard Bank email Disclaimer and confidentiality note

This e-mail, its attachments and any rights attaching hereto are, unless the 
content clearly indicates otherwise, the property of 
Standard Bank Group Limited and its subsidiaries. It is confidential, private 
and intended for only the addressee. 

Should you not be the addressee and receive this e-mail by mistake, kindly 
notify the sender, and delete this e-mail immediately.
Do not disclose or use it in any way. Views and opinions expressed in this 
e-mail are those of the sender unless clearly stated as 
those of Standard Bank Group. 

Standard Bank Group accepts no liability for any loss or damages howsoever 
incurred, or suffered, resulting, or arising, 
from the use of this email or its attachments. 

Standard Bank Group does not warrant the integrity of this e-mail nor that it 
is free of errors, viruses, interception or interference. 

Licensed divisions of the Standard Bank Group are authorised financial services 
providers in terms of the Financial Advisory and 
Intermediary Services Act, No 37 of 2002 (FAIS).

For information about the Standard Bank Group visit our website 
http://www.standardbank.com




Re: Solaris v. Linux

2009-04-01 Thread Erik N Johnson
It is rather curious that IBM is being so territorial in this regard.
It would be extraordinarily difficult to break into the system Z clone
market, I would think.  People are, I get the impression, largely
stuck with IBM unless they completely change the way in which they
operate their mainframe.  This is obviously restricted by the fact
that we're by and large talking about high volume production servers
that can't afford to be brought offline for any length of time, short
of some major disaster.  It does seem very much as though one hand
giveth whilst the other hand taketh away.

Erik Johnson

On Wed, Apr 1, 2009 at 11:55 AM, David Boyes dbo...@sinenomine.net wrote:
 On 4/1/09 11:36 AM, Kirk Wolf k...@dovetail.com wrote:

 What about GPL-licensed code using proprietary (closed) instructions and
 hipervisor features (DIAG, etc)?
 Aren't micro/millicode and zVM hipervisor vectors the new OCO  with
 respect to Linux and Solaris on z?

 Thus the complete lack of comments in the QDIO code in Linux and the minimal
 formatting. Just this side of closed-source.

 --
 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: Solaris v. Linux

2009-04-01 Thread Patrick Spinler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Kirk Wolf wrote:
 This may be a well-worn topic here, and if so I apologize...

 What about GPL-licensed code using proprietary (closed) instructions and
 hipervisor features (DIAG, etc)?
 Aren't micro/millicode and zVM hipervisor vectors the new OCO  with
 respect to Linux and Solaris on z?

I am not a lawyer, but:

It seems to me that the key question is the derivative work concept of
copyright law that the GPL bases itself on.

I note that these features are cleanly separated from Linux and it's
drivers (E.g. other z/VM guests running OpenSolaris or CMS or MVS or
z/OS could use them, they're in published API's, made by completely
separate groups of people, etc etc).  Ergo, I'd guess that they'd be
pretty clearly pass the no derivative works test, and thus any court or
GPL fanatic would admit there's no license issues.

Similarly, if this was a problem, then any fully proprietary CPU
instruction set and machine architecture would have a pretty hard time
having linux drivers written for it.  Linux pretty clearly wouldn't even
exist, in that case.

- -- Pat

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknTsOMACgkQNObCqA8uBswZMwCfR0hKc1m900ah51Rel1vU4JxY
UvIAn3dF0Xsl8Ix+pLpT+oL46aUH+1jh
=7rdT
-END PGP SIGNATURE-

--
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: Solaris v. Linux

2009-04-01 Thread David Boyes
On 4/1/09 2:14 PM, Erik N Johnson e...@uptownmilitia.com wrote:

 It is rather curious that IBM is being so territorial in this regard.
 It would be extraordinarily difficult to break into the system Z clone
 market, I would think.

Not really. The PSI suit is a good example of how simple it could be, at
least at the low end. You could fairly easily manufacture 600+ MIP System z
emulated systems these days at a dramatically better price point than the
z10BC -- if you could figure out how to avoid the MIRV lawyer launch
response from Somers and POK.

Wrt to guarding patents and proprietary stuff, they (IBM) are actually
pretty lenient as such companies go. If they have patents on valuable
technologies, they have to pursue them if they want to keep them. Thus they
don't make it easy to reverse engineer their stuff, and they make it legally
risky to try. It continually astonishes me that they haven't obliterated the
Hercules guys yet -- the Herc guys are in an enormous very-dark-grey area
wrt to reverse engineering a number of IBM patents on System z technology.

I think that kind of action would be enormously counterproductive for IBM in
that it would waste a lot of good will in the community they've built up due
to liberal patent use policies, but that's not my decision.

Let's take this one offline. It really isn't Linux related any more.

-- db

--
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: SUSE on Native LPAR

2009-04-01 Thread Martin, Larry D
Russell,

I have installed FileZilla on my PC.  Can you be more detailed about how the 
connection is made - from both sides?

Thanks,   Larry

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Jones, 
Russell
Sent: Wednesday, March 25, 2009 3:00 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SUSE on Native LPAR

I copied the install files to my PC and ran an ftp server on my PC to
complete the install. I used a freebe ftp server called FileZilla. 

Russell Jones 
ANPAC
System Programmer


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Martin, Larry D
Sent: Wednesday, March 25, 2009 1:53 PM
To: LINUX-390@VM.MARIST.EDU
Subject: SUSE on Native LPAR

I am very new to Linux and am trying to install Linux on an LAPR on a
z9BC.

 

I can load the initial Kernel by putting the CD (CD1) into the CD-ROM
drive on the HMC and perform a Lad from CD.

 

After setting up the network the Linux kernel wants to read the rest of
CD1.  If I tell him to use the HMC CD-ROM the response is Unable to
load (not an exact quote).

 

I have tried to use NFS on a desktop which has SUSE 10 installed (about
a year ago).  I get a error saying the request was rejected error = -1.

 

I have also tried using SMB to point to the CD reader on my Windows
desktop and get the same response as above (both of these take a few
minutes to return).

 

Can someone who has done this give me an idea as to what I am doing
wrong?

 

Thanks,   .Larry

 

Ps. Small shop - no money - VM not an option.

 

Larry D. Martin

Mainframe Systems Support

Office of Information Technology and Communications

301.883.7335

 




..
This E-mail and any of its attachments may contain Prince George's
County Government or Prince George's County 7th Judicial Circuit Court
proprietary information, which is privileged and confidential. This
E-mail is intended solely for the use of the individual or entity to
which it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination, distribution,
copying, or action taken in relation to the contents of and attachments
to this E-mail is strictly prohibited and may be unlawful. If you have
received this E-mail in error, please notify the sender immediately and
permanently delete the original and any copy of this E-mail and any
printout.

--
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 E-mail and any of its attachments may contain Prince George’s County 
Government or Prince George's County 7th Judicial Circuit Court proprietary 
information, which is privileged and confidential. This E-mail is intended 
solely for the use of the individual or entity to which it is addressed. If you 
are not the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.


swappiness drop_caches ?

2009-04-01 Thread Ayer, Paul W
Good afternoon all,

Just wondering if anyone has some input (good, bad, warnings  ...) or
has had to used the following two items  we are running VM5.4 and
RHEL4.x and 5.x sles 9 and 10 systems



1)  Setting swappiness to other than the default of 60 ?

 Echo nn  /proc/sys/vm/swappiness



2)  dropping caches ?

 
Echo 1 or 2 or 3  /proc/sys/vm/drop_caches


Thanks,
Paul

--
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: swappiness drop_caches ?

2009-04-01 Thread Rob van der Heij
On Wed, Apr 1, 2009 at 9:20 PM, Ayer, Paul W pwa...@statestreet.com wrote:
 Good afternoon all,

 Just wondering if anyone has some input (good, bad, warnings  ...) or
 has had to used the following two items  we are running VM5.4 and
 RHEL4.x and 5.x sles 9 and 10 systems



 1)      Setting swappiness to other than the default of 60 ?

                 Echo nn  /proc/sys/vm/swappiness

This really is a desktop thingy but may turn out useful for us as
well. It defines an amount of page cache to retain even when that
means Linux would need to swap things. You would want it large enough
to hold relevant program binaries and shared libraries, etc.
The nasty part is that it is expressed as a percentage of total memory
resources rather than a fixed amount. So you need to come up with a
right setting each time you change the virtual machine size.
In theory, for largish virtual machines you would want to lower the
swappiness. However, when the application does shared memory that
lives in page cache (for example the Oracle SGA) then you want to make
sure you also leave room for that. Setting it too low will not leave
room for the good stuff.

 2)      dropping caches ?


                Echo 1 or 2 or 3  /proc/sys/vm/drop_caches

The Linux server died when the customer tried this. I told him it
should return after completion, but did not in 5 minutes. Does that
count as bad? ;-)

Obviously, if it works well then this is just temporary relief. Linux
will immediately start to load stuff in page cache again. The other
problem is that z/VM is not aware that the pages have been freed and
will be re-used, so they will still be backed by z/VM real page frames
or paging space. And by just touching and re-arrange of the pages you
may actually make things worse.
Instead, you could use CMM-1 and inflate the balloon by the amount
that you want to drop from the cache. It will use the same criteria to
select pages, but this time it *will* tell z/VM to drop the
corresponding real storage. Although the amount may be a bit harder to
determine, the advantage is that you don't disturb the usage patterns
of the portion that you want to retain.

Rob
-- 
Rob van der Heij
Velocity Software
http://www.velocitysoftware.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


NFS--z/OS--VM/Linux

2009-04-01 Thread Ron Wells
Anyone having problems with VM/Linus using NFS to z/OS 1.9...
Only seems to work if I turn security off on z/OS... the Linux mvslogin
hangs

--
Email Disclaimer
This  E-mail  contains  confidential  information  belonging to the sender, 
which  may be legally privileged information.  This information is intended 
only  for  the use of the individual or entity addressed above.  If you are not 
 the  intended  recipient, or  an  employee  or  agent responsible for 
delivering it to the intended recipient, you are hereby notified that any 
disclosure,  copying, distribution, or the taking of any action in reliance on 
the contents of the E-mail or attached files is strictly prohibited.

--
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: swappiness drop_caches ?

2009-04-01 Thread Ayer, Paul W
For swappiness  it seems that it would be set by each system and what they are 
doing from what I am reading..

For the cache I have found that you MUST enter the command sync first then it 
all works fine and a free display shows lower after .. without entering the 
sync command first they system just hangs up ... very true ...

Thanks,
Paul

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Rob van 
der Heij
Sent: Wednesday, April 01, 2009 3:43 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: swappiness  drop_caches ?

On Wed, Apr 1, 2009 at 9:20 PM, Ayer, Paul W pwa...@statestreet.com wrote:
 Good afternoon all,

 Just wondering if anyone has some input (good, bad, warnings  ...) or
 has had to used the following two items  we are running VM5.4 and
 RHEL4.x and 5.x sles 9 and 10 systems



 1)      Setting swappiness to other than the default of 60 ?

                 Echo nn  /proc/sys/vm/swappiness

This really is a desktop thingy but may turn out useful for us as
well. It defines an amount of page cache to retain even when that
means Linux would need to swap things. You would want it large enough
to hold relevant program binaries and shared libraries, etc.
The nasty part is that it is expressed as a percentage of total memory
resources rather than a fixed amount. So you need to come up with a
right setting each time you change the virtual machine size.
In theory, for largish virtual machines you would want to lower the
swappiness. However, when the application does shared memory that
lives in page cache (for example the Oracle SGA) then you want to make
sure you also leave room for that. Setting it too low will not leave
room for the good stuff.

 2)      dropping caches ?


                Echo 1 or 2 or 3  /proc/sys/vm/drop_caches

The Linux server died when the customer tried this. I told him it
should return after completion, but did not in 5 minutes. Does that
count as bad? ;-)

Obviously, if it works well then this is just temporary relief. Linux
will immediately start to load stuff in page cache again. The other
problem is that z/VM is not aware that the pages have been freed and
will be re-used, so they will still be backed by z/VM real page frames
or paging space. And by just touching and re-arrange of the pages you
may actually make things worse.
Instead, you could use CMM-1 and inflate the balloon by the amount
that you want to drop from the cache. It will use the same criteria to
select pages, but this time it *will* tell z/VM to drop the
corresponding real storage. Although the amount may be a bit harder to
determine, the advantage is that you don't disturb the usage patterns
of the portion that you want to retain.

Rob
-- 
Rob van der Heij
Velocity Software
http://www.velocitysoftware.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 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: swappiness drop_caches ?

2009-04-01 Thread Marcy Cortes
We found that with the default vm.swapiness setting of 60, our biggest
production WAS app would slowly fill up all of his swap space, run out
after 5 days or so, and crash.  Setting it to 20 made that problem go
away .  With 20, it doesn't even creep up at all, or even use much if
any.  Why this happened has yet to be explained (and we had problems
opened with both IBM and Novell), but because of that, we are leaving it
to 20 as the default on all server builds.

Seems like 60=bug to me, but oh well!  We're happy at 20.

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-...@vm.marist.edu] On Behalf Of
Ayer, Paul W
Sent: Wednesday, April 01, 2009 12:20 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] swappiness  drop_caches ?

Good afternoon all,

Just wondering if anyone has some input (good, bad, warnings  ...) or
has had to used the following two items  we are running VM5.4 and
RHEL4.x and 5.x sles 9 and 10 systems



1)  Setting swappiness to other than the default of 60 ?

 Echo nn  /proc/sys/vm/swappiness



2)  dropping caches ?

 
Echo 1 or 2 or 3  /proc/sys/vm/drop_caches


Thanks,
Paul

--
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: swappiness drop_caches ?

2009-04-01 Thread r.stricklin

On Apr 1, 2009, at 1:32 PM, Marcy Cortes wrote:


We found that with the default vm.swapiness setting of 60, our biggest
production WAS app would slowly fill up all of his swap space, run out
after 5 days or so, and crash.  Setting it to 20 made that problem go
away .



I'm pretty unhappy with the way Linux has been managing memory,
especially w/rt the block caches being allowed to page out process
data. I was hopeful that we could affect some semblance of sane
behavior by twiddling vm.swappiness.

My experience doing so, however, was that it opened us up to
situations where I would start to see processes get pranged by the out-
of-memory desperation kill feature, even though there was quite a
bit of memory still sitting unused.

It was pretty frustrating.

ok
bear

--
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: swappiness drop_caches ?

2009-04-01 Thread Rob van der Heij
On Wed, Apr 1, 2009 at 10:19 PM, Ayer, Paul W pwa...@statestreet.com wrote:

 For swappiness  it seems that it would be set by each system and what they 
 are doing from what I am reading..

Right, to be determined for each system separately, and reviewed when
the application or configuration changes. I was just trying to explain
why it would not be helpful to yell now we think 17 is a good number
for swappiness

 For the cache I have found that you MUST enter the command sync first then it 
 all works fine and a free display shows lower after .. without entering the 
 sync command first they system just hangs up ... very true ...

That would be ugly if it would simply drop a page even when dirty and
thus hang the system (and hard to believe on any day but today).
Obviously between you typing synch and the next command, new dirty
pages could be created... You care for some Russian Roulette maybe?
Some reading shows there are lockup scenarios when using drop_caches
(and the Bugzilla is against RHEL).

As for the need to sync first: I read the should sync first as
that it is more effective when you first tell Linux to write out any
dirty pages or you would be left later with the clean pages that are
still in cache.

But as said, when drop_caches does not reduce your memory requirement
on z/VM, then I would not know why you would want to do it (apart as
diagnostics to understand the baseline requirement for your page cache
so that you can compute the swappiness).

Rob
-- 
Rob van der Heij
Velocity Software
http://www.velocitysoftware.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


Re: swappiness drop_caches ?

2009-04-01 Thread Saulo Silva
Hi Paul ,

The drop_caches is a command itself . To have it working you should create a
cron job to issue the command all the time what is not so good .
About the swappiness it  works in my case because that parameters change the
schedule about the swap out . The trick is the server will swap out but only
if it really needed .

That will not solve the problem of the file cache but helps . If any one
found the file cache solution please let me know .

Saulo Augusto Silva


2009/4/1 Ayer, Paul W pwa...@statestreet.com

 Good afternoon all,

 Just wondering if anyone has some input (good, bad, warnings  ...) or
 has had to used the following two items  we are running VM5.4 and
 RHEL4.x and 5.x sles 9 and 10 systems



 1)  Setting swappiness to other than the default of 60 ?

 Echo nn  /proc/sys/vm/swappiness



 2)  dropping caches ?


Echo 1 or 2 or 3  /proc/sys/vm/drop_caches


 Thanks,
 Paul

 --
 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: SUSE on Native LPAR

2009-04-01 Thread Mark Post
 On 4/1/2009 at  1:55 PM, Martin, Larry D ldmar...@co.pg.md.us wrote: 
 I have made no progress.  I do the initial load from the HMC and all is well. 
  I specify NFS and point to a Linux desktop via IP address.
 
 On the desktop I have /sles10sp1/cd1 (..cd2; ..cd3; ..cd4)and I have started 
 the NFS Server and exported /sles10sp1.
 
 All that I can get is an error = -1 in return.  I have tried both with punch 
 a hole in the firewall and without with the results being identical.  I have 
 looked in /var/log but do not see anything that makes any sense to me.

Is the firewall running on the SLES10 desktop?  If so, try shutting it down.  
If that makes things work, then use YaST to allow NFS as one of the permitted 
services.

 Do I need to export the sub-directories?

You should not have to, unless you have multiple file systems (or CD images) 
mounted below the top-level directory.

-snip-
 I would appreciate any advice (but please remember that I am a Linux novice 
 and do not understand all of the jargon).

Are you able to use a protocol other than NFS?  I personally prefer using HTTP 
when I'm having problems getting to my install server.

If not, then try doing an SSH install.  Before starting YaST, try pinging the 
installation server.  If that doesn't work, then you need to fix that.  Once 
that does work, then try to telnet to port 111 on the installation server.  
Repeat as needed.


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


Re: swappiness drop_caches ?

2009-04-01 Thread Andrew Wiley
On Wed, Apr 1, 2009 at 4:16 PM, r.stricklin b...@typewritten.org wrote:


 My experience doing so, however, was that it opened us up to
 situations where I would start to see processes get pranged by the out-
 of-memory desperation kill feature, even though there was quite a
 bit of memory still sitting unused.


OOM can be disabled with
# echo 0  /proc/sys/vm/oom-kill

I know this sort of situation can happen with you're running 32 bit linux
with large amounts of RAM (with Highmem enabled in the kernel) because linux
splits the RAM into low memory (used by the kernel to track memory
allocations and by applications) and high memory (used exclusively by
applications), and when it runs out of low memory, it starts killing things,
even if all the high memory is unused. 64 bit kernels don't have this
problem because all memory is low memory. Enabling Hugemem in the kernel
helps on 32 bit systems.

I should note that OOM handling and memory overcommitting behavior have
changed in newer kernels, and I'm not sure how it's handled now.

Andrew

--
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: swappiness drop_caches ?

2009-04-01 Thread Rob van der Heij
On Wed, Apr 1, 2009 at 11:16 PM, r.stricklin b...@typewritten.org wrote:

 I'm pretty unhappy with the way Linux has been managing memory,
 especially w/rt the block caches being allowed to page out process
 data. I was hopeful that we could affect some semblance of sane
 behavior by twiddling vm.swappiness.

Yes, you should be able to, like Marcy experienced. If you can
determine the setting.
As I understand the motivation for swappiness was the other way
around. Desktop users would want to protect some of the cache and swap
out some unwanted stuff.

 My experience doing so, however, was that it opened us up to
 situations where I would start to see processes get pranged by the out-
 of-memory desperation kill feature, even though there was quite a
 bit of memory still sitting unused.

You mean unused as free tells you, or what you think would be
available when it would give up page cache and/or buffers?  If it's in
page cache then it could be that it really needed it, or that pages
were dirty or not written out fast enough?
And you were not playing with CMM? I do recall an issue with CMM where
the pages in the balloon were incorrectly believed unused and thus no
replenishment was triggered.

Rob
--
Rob van der Heij
Velocity Software
http://www.velocitysoftware.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


Re: Solaris v. Linux

2009-04-01 Thread Raymond Higgs
Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 04/01/2009 12:55:10
PM:

 On 4/1/09 11:36 AM, Kirk Wolf k...@dovetail.com wrote:
 
  What about GPL-licensed code using proprietary (closed) instructions
and
  hipervisor features (DIAG, etc)?
  Aren't micro/millicode and zVM hipervisor vectors the new OCO  with
  respect to Linux and Solaris on z?

 Thus the complete lack of comments in the QDIO code in Linux and the
minimal
 formatting. Just this side of closed-source.

 --
 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

I work on channel firmware.  I haven't looked at the zfcp/qeth/cio code,
but I have some experience writing linux device drivers.  In my
experiences, I have found that comments in the linux kernel are sparse
everywhere.  Are there really less comments in this code than other parts
of the kernel?

Ray Higgs
System z FCP Development
Bld. 706, B24
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.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


Re: Solaris v. Linux

2009-04-01 Thread David Boyes
On 4/1/09 9:13 PM, Raymond Higgs rayhi...@us.ibm.com wrote:

 Linux on 390 Port LINUX-390@VM.MARIST.EDU wrote on 04/01/2009 12:55:10
 PM:

 Thus the complete lack of comments in the QDIO code in Linux and the
 minimal
 formatting. Just this side of closed-source.

 I work on channel firmware.  I haven't looked at the zfcp/qeth/cio code,
 but I have some experience writing linux device drivers.  In my
 experiences, I have found that comments in the linux kernel are sparse
 everywhere.  Are there really less comments in this code than other parts
 of the kernel?

Yes. There are no comments at all, and the code is visually and logically
structured in such a way to give as little information about what it's doing
as possible and to make it as difficult to understand as possible. In some
ways it looks like it was deliberately obscured in terms of function names,
variables, etc. The networking driver in OpenSolaris shares some of the same
problems, for what I suspect are a lot of the same -- non-technical --
reasons.

Let me be clear: I'm not blaming the folks in the German labs who wrote it
-- it was probably the only compromise they could strike with the lawyers to
get the source out there -- but boy, is that code hard to follow for
something that is essentially setting up a shared memory buffer and managing
toggling access to that buffer between the QDIO device and main CPUs using
an undocumented instruction. The whole thing seems designed to make
understanding what that undocumented instruction does hard, even though
there are articles in the publically available IBM Systems Journal that
describe it's behavior in detail.

It'll be interesting to see if Linux and/or VM TCPIP gets a DIAG2A8
interface driver at some point. If so, a lot of that code ugliness could go
away, as that interface IS documented. The other code will probably have to
stick around to deal with the run-in-LPAR requirement, though.

You know, some day if you're bored, it'd be really cool if all you folks get
together and teach DIAG250 how to directly play nice with SCSI, and then all
the current QDIO device interfaces would use documented interfaces. Life
Would Be Good. 

But there I go causing trouble again...

-- db

--
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


backups on Red hat

2009-04-01 Thread Jan de Wet - Business Connexion
Hi
 
I am implementing our first production Linux on the mainframe
We are looking at backups
What commercial backup systems have agents that can run on Red Hat on
the Mainframe
Our system of choice is Legato, but they do not seem to support this
environment
 
thank you
 

Jan de Wet
Deployment (Business Connexion), Services Building, Midrand, South
Africa
Cell:   +27 (0)82 902 1996
Office: +27 (0)11 990 1695

Fax:+27 (0)86 572 5720

e-mail: jan.de...@bcx.co.za

Jesus Christ is my Lord

 

--
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: backups on Red hat

2009-04-01 Thread Scott Rohling
TSM - IBM's Tivoli Storage Manager.

Scott

On Wed, Apr 1, 2009 at 10:21 PM, Jan de Wet - Business Connexion 
jan.de...@bcx.co.za wrote:

 Hi

 I am implementing our first production Linux on the mainframe
 We are looking at backups
 What commercial backup systems have agents that can run on Red Hat on
 the Mainframe
 Our system of choice is Legato, but they do not seem to support this
 environment

 thank you


 Jan de Wet
 Deployment (Business Connexion), Services Building, Midrand, South
 Africa
 Cell:   +27 (0)82 902 1996
 Office: +27 (0)11 990 1695

 Fax:+27 (0)86 572 5720

 e-mail: jan.de...@bcx.co.za

 Jesus Christ is my Lord



 --
 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