s390 Debian with root mounted on a LVM's zFCP device

[Wiggins, Mark]

I just want to ask a simple yes or no question (of course only respond if the 
answer is yes), has anyone successfully booted either Debian Etch or Lenny in 
s390 with root residing on a LVM, multipathed zFCP device? If someone has, than 
I will at least know that it's possible.

--
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: How many virtual servers per IFL?

[Wiggins, Mark]

I wanted to chime in on this discussion, but it has taken me a day or two to 
both find the time to write this and get everything said the way that I want it 
said. We've been running z/Linux here at UConn from pretty much the beginning. 
We had (I'll explain "had" in a moment) about 45 (prod/test) servers running on 
a z/890 up until about 6 months ago when we purchased our new z/10 BC. The 45 
servers that ran on our z890 were things like LDAP, CAS, FTP, Listserv, WEB 
servers, Proxy, DNS, SAMBA, etc., all "reasonably" medium to small (2G-500M 
memory) servers. At times, we definitely maxed out our z/890, but this was 
usually due to an errant process running out of control or a large email 
delivery on Listserv. For the most part we hovered between 45-65% CPU with a 
2.1:1 virtual:real memory ratio with 18G central and 2G expanded storage on 1 
IFL. We purchased the new z/10 hoping to migrate our 9672, z/OS system and 
z/890, z/VM and z/Linux LPAR's to one box. We've completed the migration of our 
z/890 to a z/10 BC, so we're currently running z/VM 5.4 on a GP and z/VM 6.1 
with 36 prod/test z/Linux servers running on 1 IFL with 24G central and 3G 
expanded storage. Our current virtual:real memory ratio is 0.8:1, we run 
somewhere around 20-30% CPU and we "never" peak any more. The "your mileage may 
vary" statement should be included here, but I just wanted to show you what we 
had done.

Now on to the "bad" part of this conversation, where I explain the reason why 
we have reduced the number of z/Linux servers from 45 to 36 (remember when I 
said "I'll explain "had" in a moment"). The reason for the reduction is because 
we also started buying Blade servers, running VMWare at the same time that we 
purchased our new z/10 and many of our z/Linux servers have either moved or are 
planned to be moved to this environment instead. So you're asking, why would 
you buy a new z/10 just to migrate all of your z/Linux servers somewhere else? 
Our initial decision to get the z/10 was to move our z/OS system, the IFL (and 
z/Linux) was just an added bonus, "at least for me"! I could get into why we've 
decided to migrate off of z/Linux to Blades/VMWare/Linux, but it's all of the 
same old story (application certification, application inoperability with 
anything other than Sun Java, and the ole classic, "it's not Intel"). Anyway, 
the main purpose of this response was to show you how many servers "can" run, 
effectively, on 1 IFL for your comparison...


Mark Wiggins
University of Connecticut



-Original Message-
From: John Cousins [mailto:john.cous...@bristol.gov.uk]
Sent: Monday, December 06, 2010 12:08 PM
Subject: How many virtual servers per IFL?

Here we go again!
Without success, we've been trying to get the IT department here to adopt 
z/Linux since 2003!

Our zVM licence has been recently cancelled, and I have just had a request from 
our Enterprise Architects for some costing for z/Linux as they need to compare 
server virtualisation costs with VMware!

One problem of trying to get a cost per virtual server was always trying to 
estimate how many servers an IFL will support. We had a 13 SuSe servers defined 
in a z800 IFL but as they were hardly used we couldn't measure a thing!

So are there any rules of thumb out there on how many production virtual 
servers would run on a Z10 IFL? Obviously it will depend on server utilisation, 
guess that will need to be estimated as well?

Another question is where do the bulk of the savings come from? From my 
investigations over the years other success stories suggest most savings come 
from software licensing, e.g Oracle, Tivoli etc. but also from networking 
infra-structure by the use of virtual switches. Are there any other areas that 
provide benefits?

Any ideas or constructive suggestions would be gratefully received!

Best regards

John



John Cousins
Senior IT Officer
Central Support Services ICT Division
Bristol City Council
Romney House
Romney Avenue
PO Box 1380
Bristol BS7 9TB

Tel : 0117 922 4705
Fax: 0117 922 3983
e-mail: john.cous...@bristol.gov.uk

__
'Do it online' with our growing range of online services - 
http://www.bristol.gov.uk/services

Sign-up for our email bulletin giving news, have-your-say and event information 
at: http://www.bristol.gov.uk/newsdirect

View webcasts of Council meetings at http://www.bristol.gov.uk/webcast

Bristol is the UK's first Cycling City. Visit www.betterbybike.info to join 
thousands of others getting around by bike.

--
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: Question about booting root on a multipathed, LVM'd volume on Debian 390.

[Wiggins, Mark]

(initramfs) ps -ef
ps -ef
  PID  Uid VmSize Stat Command
1 0   680 S   /bin/sh /init
2 0   SW  Ýmigration/0¨
3 0   SWN Ýksoftirqd/0¨
4 0   SW< Ýevents/0¨
5 0   SW< Ýkhelper¨
6 0   SW< Ýkthread¨
8 0   SW< Ýkblockd/0¨
   28 0   SW< Ýcio¨
   29 0   SW< Ýcio_notify¨
   30 0   SW< Ýkslowcrw¨
   60 0   SW< Ýappldata¨
   75 0   SW  Ýpdflush¨
   76 0   SW  Ýpdflush¨
   77 0   SW< Ýkswapd0¨
   78 0   SW< Ýaio/0¨
   99 0   SW< Ýkmcheck¨
  179 0   SW< Ýkmirrord¨
  192 0   SW< Ýkmpathd/0¨
  264 0   532 S < udevd --daemon
  938 0   708 R   /bin/sh -i
  939 0   636 R   ps -ef
(initramfs)

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Richard 
Troth
Sent: Tuesday, December 07, 2010 8:31 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about booting root on a multipathed, LVM'd volume on 
Debian 390.

Is 'udev' started?
You listed the contents of /proc/modules.  Can you also show the
output of 'ps -ef'?

-- R;=A0=A0 <><
Rick Troth
Velocity Software
http://www.velocitysoftware.com/








On Mon, Dec 6, 2010 at 16:04, Wiggins, Mark  wrote:
> Back in October I asked a question about multipathing in z/Debian. I've s=
ince resolved my problem with getting the multipathing device definitions t=
o hold across an IPL, but now I'm having trouble booting with root mounted =
on a multipathed, LVM'd volume on z/Debian. It appears to be within the ord=
er of things. Of course, multipathing should come first, then LVM, then the=
 mounting of root, but what I always get is the message "mounting root on /=
dev/mapper/system-ROOT" (in other words, I've coded /etc/zipl.conf correctl=
y), then unable to find volume group "system", then it drops into initramfs=
. I try to issue a "vgchange -ay system", but it can't find the volume grou=
p "system", nor can it find the multipath'd volume (/dev/mapper/mpath0 or m=
path1) to use as its PV's.
>
> ALERT! /dev/mapper/system-ROOT does not exist. Dropping into shell!
>
> cat /proc/cmdline
> root=3D/dev/mapper/system-ROOT ro rootdelay=3D10 BOOT_IMAGE=3D0
>
> cat /proc/modules
> dasd_eckd_mod
> zfcp
> scsi_transport_fc
> scsi_mod
> dasd_fba_mod
> dasd_mod
> dm_multipath
> dm_snapshot
> dm_mirror
> dm_mod
>
> How do I get my multipath definitions and LVM configuration to run before=
 root is mounted?
>
> Mark Wiggins
> University of Connecticut
>
>
> --
> 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/

Question about booting root on a multipathed, LVM'd volume on Debian 390.

[Wiggins, Mark]

Back in October I asked a question about multipathing in z/Debian. I've since 
resolved my problem with getting the multipathing device definitions to hold 
across an IPL, but now I'm having trouble booting with root mounted on a 
multipathed, LVM'd volume on z/Debian. It appears to be within the order of 
things. Of course, multipathing should come first, then LVM, then the mounting 
of root, but what I always get is the message "mounting root on 
/dev/mapper/system-ROOT" (in other words, I've coded /etc/zipl.conf correctly), 
then unable to find volume group "system", then it drops into initramfs. I try 
to issue a "vgchange -ay system", but it can't find the volume group "system", 
nor can it find the multipath'd volume (/dev/mapper/mpath0 or mpath1) to use as 
its PV's.

ALERT! /dev/mapper/system-ROOT does not exist. Dropping into shell!

cat /proc/cmdline
root=/dev/mapper/system-ROOT ro rootdelay=10 BOOT_IMAGE=0

cat /proc/modules
dasd_eckd_mod
zfcp
scsi_transport_fc
scsi_mod
dasd_fba_mod
dasd_mod
dm_multipath
dm_snapshot
dm_mirror
dm_mod

How do I get my multipath definitions and LVM configuration to run before root 
is mounted?

Mark Wiggins
University of Connecticut


--
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: Question about multipathing on zDebian (Lenny)

[Wiggins, Mark]

Okay first, I had already changed my 
/etc/sysconfig/hardware/config-ccw-0.0.a200 to the way that you suggested based 
on a recommendation from David Straub.

So on to the "lszfcp" commands. Before and after reboot are the same for 
"lszfcp -HV" command
# lszfcp -HV
/sys/devices/css0/0.0.0006/0.0.a200
/sys/class/fc_host/host0
/sys/class/scsi_host/host0
/sys/devices/css0/0.0.0007/0.0.a300
/sys/class/fc_host/host1
/sys/class/scsi_host/host1

But the "# lszfcp -DV" command shows *nothing* after reboot and shows this 
before the reboot,
# lszfcp -DV

/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035ee/0x001f

/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-0/target0:0:0/0:0:0:31
/sys/block/sda /sys/class/scsi_generic/sg0

/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035ee/0x001f

/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-0/target1:0:0/1:0:0:31
/sys/block/sdc /sys/class/scsi_generic/sg2

/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035ee/0x0020

/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-0/target0:0:0/0:0:0:32
/sys/block/sde /sys/class/scsi_generic/sg4

/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035ee/0x0020

/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-0/target1:0:0/1:0:0:32
/sys/block/sdg /sys/class/scsi_generic/sg6

/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035d9/0x001f

/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-1/target0:0:1/0:0:1:31
/sys/block/sdb /sys/class/scsi_generic/sg1

/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035d9/0x001f

/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-1/target1:0:1/1:0:1:31
/sys/block/sdd /sys/class/scsi_generic/sg3

/sys/devices/css0/0.0.0006/0.0.a200/0x50050768014035d9/0x0020

/sys/devices/css0/0.0.0006/0.0.a200/host0/rport-0:0-1/target0:0:1/0:0:1:32
/sys/block/sdf /sys/class/scsi_generic/sg5

/sys/devices/css0/0.0.0007/0.0.a300/0x50050768011035d9/0x0020

/sys/devices/css0/0.0.0007/0.0.a300/host1/rport-1:0-1/target1:0:1/1:0:1:32
/sys/block/sdh /sys/class/scsi_generic/sg7

Obviously, that is an issue. So what do you think that I'm missing? It still 
seems that I'm missing a configuration file, maybe it's not 
/etc/sysconfig/hardware/config-ccw-0.0.a200 in Debian??? I've read through 
IBM's "Device Drivers, Features, and Commands" (amongst a hundred other 
documents), but haven't found anything there either. It shows you how to 
configure the devices (echo 0x001f > 
0.0.a200/0x50050768011035d9/unit_add) but doesn't suggest where to put those 
configuration parameters to make them permanent. I'm grateful for any help that 
you can provide.


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Steffen 
Maier
Sent: Wednesday, October 06, 2010 5:15 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about multipathing on zDebian (Lenny)

On 10/05/2010 07:35 PM, Wiggins, Mark wrote:
> I'm trying to
> add some multipath'd devices to a Debian(Lenny)  instance. I can get
> the devices configured properly,

> I just can't get these definitions to hold across a reboot. I've

In order to narrow down which activation step does not work correctly,=20
it would be interesting to know if the following holds true after the=20
boot process finished:
- zfcp adapters for each path are online
   # lszfcp -HV
- all fcp luns for each path and disk are online
   # lszfcp -DV
Those would be the prerequisites to have the necessary SCSI disks for=20
device-mapper multipath to work with. After that, dm-mp might have=20
problems. However, I'm not particular familiar with that and its config=20
file (incl. blacklists/whitelists).

> My /etc/sysconfig/hardware/config-ccw-0.0.a200 looks like this,
> # Configured zfcp disks
> ZFCP_LUNS=3D"0x50050768014035ee:0x001f"
> ZFCP_LUNS=3D"0x50050768014035d9:0x001f"
> ZFCP_LUNS=3D"0x50050768014035ee:0x0020"
> ZFCP_LUNS=3D"0x50050768014035d9:0x0020"

This seems to overwrite the ZFCP_LUNS shell variable three times and the =

last one will win. So I guess only the FCP LUN 0x0020 on=20
WWPN 0x50050768014035d9 will be set online and you're missing the other=20
three LUNs (or at least the second path to the same LUN).

This looks very much like the SLES syntax and IIRC, you have to use one=20
ZFCP_LUNS variable assignment and put each WWPN:LUN pair on a separate=20
line within the same double quotes on the right hand side of the=20
assigment, i.e.:

# Configure

FW: Question about multipathing on zDebian (Lenny)

[Wiggins, Mark]

I guess what I'm really looking for is the equivalent to mkinitrd on Debian. 
Again, I can configure the two LUNS to be multipath'd,

mpath1 (360050768019281af7153) dm-1 IBM ,2145
[size=3D3.7G][features=3D0][hwhandler=3D0]
\=5F round-robin 0 [prio=3D0][active]
 \=5F 0:0:0:32 sde 8:64  [active][undef]
 \=5F 0:0:1:32 sdf 8:80  [active][undef]
 \=5F 1:0:0:32 sdg 8:96  [active][undef]
 \=5F 1:0:1:32 sdh 8:112 [active][undef]

mpath0 (360050768019281af7152) dm-0 IBM ,2145
[size=3D3.7G][features=3D0][hwhandler=3D0]
\=5F round-robin 0 [prio=3D0][active]
 \=5F 0:0:0:31 sda 8:0   [active][undef]
 \=5F 0:0:1:31 sdb 8:16  [active][undef]
 \=5F 1:0:0:31 sdc 8:32  [active][undef]
 \=5F 1:0:1:31 sdd 8:48  [active][undef]

I just can't get the definitions to hold across a reboot, as in with SuSE after 
you've run mkinitrd and zipl. I found the command "update-initramfs" which 
seems to be the equivalent to mkinitrd, but it stills doesn't work for me. 
Debian doesn't appear to use mkinitrd command...

-----Original Message-
From: Wiggins, Mark
Sent: Tuesday, October 05, 2010 3:20 PM
To: 'Linux on 390 Port'
Subject: RE: Question about multipathing on zDebian (Lenny)

Ohhh, I thought that you might have it, but unfortunately, the hwup-ccw-zfcp 
command (the only one the I can find), looks for config-ccw, not config-zfcp, 
thanks though. Also, the zfcp, dm_multipath, and some various scsi_ modules are 
all properly loaded as well.


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Sterling 
James
Sent: Tuesday, October 05, 2010 3:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about multipathing on zDebian (Lenny)

I'm not familiar with zDebian (Lenny); but if it's suse-like should that
be;
/etc/sysconfig/hardware/config-zfcp-0.0.a200
vs
/etc/sysconfig/hardware/config-ccw-0.0.a200

In Redhat, you need a /etc/zfcp.conf and
/etc/modprobe.conf needs to contains "alias scsi_hostadapter zfcp"

Both need the mkinitrd and zipl.
Thx

-
Please consider the environment before printing this email and any
attachments.

This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law.  If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender.  If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.

--
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: Question about multipathing on zDebian (Lenny)

[Wiggins, Mark]

Ohhh, I thought that you might have it, but unfortunately, the hwup-ccw-zfcp 
command (the only one the I can find), looks for config-ccw, not config-zfcp, 
thanks though. Also, the zfcp, dm_multipath, and some various scsi_ modules are 
all properly loaded as well.


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Sterling 
James
Sent: Tuesday, October 05, 2010 3:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about multipathing on zDebian (Lenny)

I'm not familiar with zDebian (Lenny); but if it's suse-like should that
be;
/etc/sysconfig/hardware/config-zfcp-0.0.a200
vs
/etc/sysconfig/hardware/config-ccw-0.0.a200

In Redhat, you need a /etc/zfcp.conf and
/etc/modprobe.conf needs to contains "alias scsi_hostadapter zfcp"

Both need the mkinitrd and zipl.
Thx

-
Please consider the environment before printing this email and any
attachments.

This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law.  If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender.  If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.

--
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: Question about multipathing on zDebian (Lenny)

[Wiggins, Mark]

I don't even get to the stage of mounting these devices, we're talking straight 
"multipath -l" command, they are there when I come down and not when I come 
back up. I've been successful both with SuSE and Redhat, just can't seem to 
figure it out in Debian. As far as mkinitrd, I think the "update-initramfs" 
command is the comparable command in Debian, zipl stays the same across the 3 
mentioned though. I know that when I add a DASD device to a Debian instance, I 
first "touch /etc/sysconfig/hardware/config-ccw-0.0.0200", then I issue "hwup 
0.0.0200" and from then on, the DASD device is available. I guess what I'm 
looking for is the same kind of thing for a multipath'd zfcp device, which I 
thought was as simple as coding the config-ccw-0.0.a200 file that I listed in 
my first email (at the bottom). When I then issue the "hwup-ccw-zfcp 0.0.a200" 
command, it says "Configuring device 0.0.a200: online. ok." but still, nothing 
when I issue the "multipath -l" command.

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Emmett 
O'Grady
Sent: Tuesday, October 05, 2010 1:57 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about multipathing on zDebian (Lenny)

--=_related 0062A15E852577B3_=
Content-Type: multipart/alternative; boundary="=_alternative 0062A161852577B3_="


--=_alternative 0062A161852577B3_=
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

You should be able to set them up in /etc/multipath.conf

I had issues mounting the filesystems across reboots on an xSeries.
 Red Hat recommended using the /dev/mapper/ as opposed to /dev/mpath##

[ . . . snip from /etc/fstab . . . ]

/dev/mapper/LnP  /LnP=5FFTPext3 acl 1 2
/dev/mapper/100GBno1 /ftpdata2   ext3 acl 1 2
# this is the 16GB LUN Slice below
/dev/mapper/16GBno1  /DigMedNetPgm   ext3 acl 1 2

Seems that there was NO consistency as to how multipath would select path=20
numbers. I would always get dropped into maintenance mode
This recommendation fixed my issues since changing fstab to=20
/dev/mapper/



Emmett O'Grady=20
Mercedes-Benz USA, LLC.=20





jnsch...@us.ibm.com=20
Sent by: LINUX-390@VM.MARIST.EDU
10/05/2010 01:45 PM
Please respond to
LINUX-390@VM.MARIST.EDU


To
LINUX-390@VM.MARIST.EDU
cc

Subject
Re: Question about multipathing on zDebian (Lenny)







Mark,

  I am not familiar with Debian, but if this was a SUSE or REDHAT=20
instance,
I would say you need to run mkinitrd and zipl before your reboot.


John





From:   "Wiggins, Mark" 
To: LINUX-390@vm.marist.edu
Date:   10/05/2010 01:37 PM
Subject:Question about multipathing on zDebian (Lenny)
Sent by:Linux on 390 Port 



I hate to come and ask what I know is going to be a simple answer, but=20
I've
beat my head against the wall for long enough. I'm trying to add some
multipath'd devices to a Debian(Lenny)  instance. I can get the devices
configured properly,


mpath1 (360050768019281af7153) dm-1 IBM ,2145

[size=3D3.7G][features=3D0][hwhandler=3D0]

\=5F round-robin 0 [prio=3D0][active]

 \=5F 0:0:0:32 sde 8:64  [active][undef]

 \=5F 0:0:1:32 sdf 8:80  [active][undef]

 \=5F 1:0:0:32 sdg 8:96  [active][undef]

 \=5F 1:0:1:32 sdh 8:112 [active][undef]

mpath0 (360050768019281af7152) dm-0 IBM ,2145

[size=3D3.7G][features=3D0][hwhandler=3D0]

\=5F round-robin 0 [prio=3D0][active]

 \=5F 0:0:0:31 sda 8:0   [active][undef]

 \=5F 0:0:1:31 sdb 8:16  [active][undef]

 \=5F 1:0:0:31 sdc 8:32  [active][undef]
 \=5F 1:0:1:31 sdd 8:48  [active][undef]

I just can't get these definitions to hold across a reboot. I've tried
creating /etc/sysconfig/hardware/config-ccw-0.0.a200
files,/usr/share/initramfs-tools/hooks/multipath=5Fhook file, zipl commands,
update-initramfs commands, etc., but I haven't found what it takes to make
these definitions hold across a reboot. What am I missing besides writing
some kind of a script that has to run after every reboot?

Mark Wiggins
University of Connecticut

My /etc/sysconfig/hardware/config-ccw-0.0.a200 looks like this,

#!/bin/sh

#

# hwcfg-zfcp-bus-ccw-0.0.a200

#

# Configuration for the zfcp adapter at CCW ID 0.0.a200

#

STARTMODE=3D"auto"

MODULE=3D"zfcp"

MODULE=5FOPTIONS=3D""

# Scripts to be called for the various events.

# If called manually the event is set to 'up'.

SCRIPTUP=3D"hwup-ccw"

SCRIPTUP=5Fccw=3D"hwup-ccw"

SCRIPTUP=5Fscsi=5Fhost=3D"hwup-zfcp"

SCRIPTDOWN=3D"hwdown-scsi"

SCRIPTDOWN=5Fscsi=3D"hwdown-zfcp"

# Configured zfcp disks

ZFCP=5FLUNS=3D"0x50050768014035ee:0x001f"

ZFCP=5FLUNS=3D"0x50050768014035d9:0x001f000

Question about multipathing on zDebian (Lenny)

[Wiggins, Mark]

I hate to come and ask what I know is going to be a simple answer, but I've 
beat my head against the wall for long enough. I'm trying to add some 
multipath'd devices to a Debian(Lenny)  instance. I can get the devices 
configured properly,


mpath1 (360050768019281af7153) dm-1 IBM ,2145

[size=3.7G][features=0][hwhandler=0]

\_ round-robin 0 [prio=0][active]

 \_ 0:0:0:32 sde 8:64  [active][undef]

 \_ 0:0:1:32 sdf 8:80  [active][undef]

 \_ 1:0:0:32 sdg 8:96  [active][undef]

 \_ 1:0:1:32 sdh 8:112 [active][undef]

mpath0 (360050768019281af7152) dm-0 IBM ,2145

[size=3.7G][features=0][hwhandler=0]

\_ round-robin 0 [prio=0][active]

 \_ 0:0:0:31 sda 8:0   [active][undef]

 \_ 0:0:1:31 sdb 8:16  [active][undef]

 \_ 1:0:0:31 sdc 8:32  [active][undef]
 \_ 1:0:1:31 sdd 8:48  [active][undef]

I just can't get these definitions to hold across a reboot. I've tried creating 
/etc/sysconfig/hardware/config-ccw-0.0.a200 
files,/usr/share/initramfs-tools/hooks/multipath_hook file, zipl commands, 
update-initramfs commands, etc., but I haven't found what it takes to make 
these definitions hold across a reboot. What am I missing besides writing some 
kind of a script that has to run after every reboot?

Mark Wiggins
University of Connecticut

My /etc/sysconfig/hardware/config-ccw-0.0.a200 looks like this,

#!/bin/sh

#

# hwcfg-zfcp-bus-ccw-0.0.a200

#

# Configuration for the zfcp adapter at CCW ID 0.0.a200

#

STARTMODE="auto"

MODULE="zfcp"

MODULE_OPTIONS=""

# Scripts to be called for the various events.

# If called manually the event is set to 'up'.

SCRIPTUP="hwup-ccw"

SCRIPTUP_ccw="hwup-ccw"

SCRIPTUP_scsi_host="hwup-zfcp"

SCRIPTDOWN="hwdown-scsi"

SCRIPTDOWN_scsi="hwdown-zfcp"

# Configured zfcp disks

ZFCP_LUNS="0x50050768014035ee:0x001f"

ZFCP_LUNS="0x50050768014035d9:0x001f"

ZFCP_LUNS="0x50050768014035ee:0x0020"

ZFCP_LUNS="0x50050768014035d9:0x0020"



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

Using "update" instead of "install" - has anyone been successful going from SLES9 to SLES10?

[Wiggins, Mark]

Before I start posting all of the error messages and problems that I've
had with trying to "update" a SLES9 image to a SLES10 image, I thought
I'd first ask and see if anyone has had success with this yet? I have
successfully installed SLES10 from scratch, but haven't been able to
"update" an image yet. I continually get errors when it tries to install
the boot loader and installing zipl... 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

IBM WebSphere Application Server Community Edition

[Wiggins, Mark]

On to my next question...
 
The "IBM WebSphere Application Server Community Edition" appears to be a
free download, but is it available for s390? It only shows Linux/Intel
and Linux/PPC.
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: Question about sysctl.conf

[Wiggins, Mark]

Ok, I put the command "sysctl -p" in my boot.local file and that worked
fine. Thanks to everyone for their input. 

Mark

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Neubert, Kevin (DIS)
Sent: Tuesday, May 23, 2006 11:59 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about sysctl.conf


Issue chkconfig boot.sysctl on or consider using /etc/init.d/boot.local
instead.

Regards,

Kevin

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Wiggins, Mark
Sent: Tuesday, May 23, 2006 8:41 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about sysctl.conf

Ya, unfortunately I guess, that's what I've got.
boot.sysctl No  B=09

=20

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Dell Harris
Sent: Tuesday, May 23, 2006 11:22 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about sysctl.conf


Bring up YaST2 -> System -> Runlevel EditorClick on expert mode.
Scroll down to boot.sysctl and ensure that the 'B' box is checked.

>>> "Meanor, Tim" <[EMAIL PROTECTED]> 05/23/06 9:13 AM >>>
What makes you think sysctl.conf isn't being read at boot time?  It
should be.  I don't have a SLES system in front of me, but on Red Hat,
the /etc/rc.sysinit script applies the settings in sysctl.conf to the
running kernel.  SLES probably has a similar init script.

- Original Message-----
From: Linux on 390 Port [mailto:LINUX- [EMAIL PROTECTED] On Behalf Of
Wiggins, Mark
Sent: Tuesday, May 23, 2006 11:00 AM
To: LINUX- [EMAIL PROTECTED]
Subject: Question about sysctl.conf


So, way back when we made a decision to turn on the timer patch for
all
of our SuSE SLES9 images running on z/VM 5.1. Recently, I noticed
(after
all this time) that the /etc/sysctl.conf file does not get read at
boot
time and therefore, we've been running with the timer patch off. This
now generates a few questions...

1) If the timer patch has been off for all of this time, is it worth
turning on now? We haven't had any significant performance issues to
date so how much difference would it really make now? In looking at
the
average CPU for 2 test images (1 with the patch on, 1 with it off)
over
the course of a day or so, the one with the "timer patch on" ran at an
average of 0.17% CPU while doing nothing, and the one with the "timer
patch off" ran at an average of 0.19% CPU. I could see this possibly
mattering with hundreds of images, but we're somewhere between 30- 40.


2) If we decide to turn the patch on, how do you get it to stay on
across an IPL. I've included "kernel.hz_timer=3D0" in the sysctl.conf,
but
it doesn't appear to be read after boot. What are other people doing
with this?

3) Are there any particular instances where you wouldn't turn the
patch
on? E.g. a time server or maybe a mail server??? I don't know... Only
test servers??? Etc...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860- 486- 2792

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

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

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

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

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

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

Re: Question about sysctl.conf

[Wiggins, Mark]

Ya, unfortunately I guess, that's what I've got.
boot.sysctl No  B   

 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Dell Harris
Sent: Tuesday, May 23, 2006 11:22 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about sysctl.conf


Bring up YaST2 -> System -> Runlevel EditorClick on expert mode.
Scroll down to boot.sysctl and ensure that the 'B' box is checked.

>>> "Meanor, Tim" <[EMAIL PROTECTED]> 05/23/06 9:13 AM >>>
What makes you think sysctl.conf isn't being read at boot time?  It
should be.  I don't have a SLES system in front of me, but on Red Hat,
the /etc/rc.sysinit script applies the settings in sysctl.conf to the
running kernel.  SLES probably has a similar init script.

- Original Message-
From: Linux on 390 Port [mailto:LINUX- [EMAIL PROTECTED] On Behalf Of
Wiggins, Mark
Sent: Tuesday, May 23, 2006 11:00 AM
To: LINUX- [EMAIL PROTECTED]
Subject: Question about sysctl.conf


So, way back when we made a decision to turn on the timer patch for
all
of our SuSE SLES9 images running on z/VM 5.1. Recently, I noticed
(after
all this time) that the /etc/sysctl.conf file does not get read at
boot
time and therefore, we've been running with the timer patch off. This
now generates a few questions...

1) If the timer patch has been off for all of this time, is it worth
turning on now? We haven't had any significant performance issues to
date so how much difference would it really make now? In looking at
the
average CPU for 2 test images (1 with the patch on, 1 with it off)
over
the course of a day or so, the one with the "timer patch on" ran at an
average of 0.17% CPU while doing nothing, and the one with the "timer
patch off" ran at an average of 0.19% CPU. I could see this possibly
mattering with hundreds of images, but we're somewhere between 30- 40.


2) If we decide to turn the patch on, how do you get it to stay on
across an IPL. I've included "kernel.hz_timer=0" in the sysctl.conf,
but
it doesn't appear to be read after boot. What are other people doing
with this?

3) Are there any particular instances where you wouldn't turn the
patch
on? E.g. a time server or maybe a mail server??? I don't know... Only
test servers??? Etc...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860- 486- 2792

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

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

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

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

Re: Question about sysctl.conf

[Wiggins, Mark]

The reason that I don't think that it gets read is because if I do a
"sysctl -a", kernel.hz_timer=1, although I have it kernel.hz_timer=0 in
my /etc/sysctl.conf file. If I issue "sysctl -p" the setting is changed
to what I have in my /etc/sysctl.conf file. There is a boot.sysctl
script in /etc/init.d/ that looks like it would do the trick, but when I
issue a "chkconfig -a boot.sysctl" nothing happens. 
 
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Meanor, Tim
Sent: Tuesday, May 23, 2006 11:14 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Question about sysctl.conf


What makes you think sysctl.conf isn't being read at boot time?  It
should be.  I don't have a SLES system in front of me, but on Red Hat,
the /etc/rc.sysinit script applies the settings in sysctl.conf to the
running kernel.  SLES probably has a similar init script.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Wiggins, Mark
Sent: Tuesday, May 23, 2006 11:00 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Question about sysctl.conf


So, way back when we made a decision to turn on the timer patch for all
of our SuSE SLES9 images running on z/VM 5.1. Recently, I noticed (after
all this time) that the /etc/sysctl.conf file does not get read at boot
time and therefore, we've been running with the timer patch off. This
now generates a few questions...
=20
1) If the timer patch has been off for all of this time, is it worth
turning on now? We haven't had any significant performance issues to
date so how much difference would it really make now? In looking at the
average CPU for 2 test images (1 with the patch on, 1 with it off) over
the course of a day or so, the one with the "timer patch on" ran at an
average of 0.17% CPU while doing nothing, and the one with the "timer
patch off" ran at an average of 0.19% CPU. I could see this possibly
mattering with hundreds of images, but we're somewhere between 30-40.=20
=20
2) If we decide to turn the patch on, how do you get it to stay on
across an IPL. I've included "kernel.hz_timer=3D0" in the sysctl.conf, =
but
it doesn't appear to be read after boot. What are other people doing
with this?
=20
3) Are there any particular instances where you wouldn't turn the patch
on? E.g. a time server or maybe a mail server??? I don't know... Only
test servers??? Etc...
=20
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

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

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

Question about sysctl.conf

[Wiggins, Mark]

So, way back when we made a decision to turn on the timer patch for all
of our SuSE SLES9 images running on z/VM 5.1. Recently, I noticed (after
all this time) that the /etc/sysctl.conf file does not get read at boot
time and therefore, we've been running with the timer patch off. This
now generates a few questions...
 
1) If the timer patch has been off for all of this time, is it worth
turning on now? We haven't had any significant performance issues to
date so how much difference would it really make now? In looking at the
average CPU for 2 test images (1 with the patch on, 1 with it off) over
the course of a day or so, the one with the "timer patch on" ran at an
average of 0.17% CPU while doing nothing, and the one with the "timer
patch off" ran at an average of 0.19% CPU. I could see this possibly
mattering with hundreds of images, but we're somewhere between 30-40. 
 
2) If we decide to turn the patch on, how do you get it to stay on
across an IPL. I've included "kernel.hz_timer=0" in the sysctl.conf, but
it doesn't appear to be read after boot. What are other people doing
with this?
 
3) Are there any particular instances where you wouldn't turn the patch
on? E.g. a time server or maybe a mail server??? I don't know... Only
test servers??? Etc...
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: Problem with RMFPMS and the recent time change

[Wiggins, Mark]

Alright, when I go to YaST - "Clock and Time Zone Configuration", I see
"Hardware clock set to UTC", I see "Region = USA" and "Time Zone =
Eastern". Are we talking about a different hardware clock here? 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Alan Altmark
Sent: Thursday, April 27, 2006 12:27 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problem with RMFPMS and the recent time change


On Thursday, 04/27/2006 at 11:47 AST, "Wiggins, Mark"
<[EMAIL PROTECTED]> wrote:
> My hardware clock is set to UTC (USA/Eastern).

Which?  UTC is not USA/Eastern.  UTC is GMT.  The h/w clock should be
set
to UTC/GMT+0.  Use timezones in the operating systems to get the correct
local time.  Not doing this causes many apps (e.g. e-mail) to send the
wrong timestamps as they try to convert from local time to GMT and vice
versa.

Alan Altmark
z/VM Development
IBM Endicott

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

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

Re: Problem with RMFPMS and the recent time change

[Wiggins, Mark]

My hardware clock is set to UTC (USA/Eastern). Each Linux image itself
maintains the correct time across a time change, it was only the rmfpms
reporting process that is not effected unless restarted. Maybe I'm not
explaining that right, but when I go to the Performance Toolkit and go
to say the "Linux Performance Data Selection" screen, the date reported
here will either be Interval "11:39:00-11:42:00, on 2006/04/27" or
"Interval 10:39:00-10:42:00, on 2006/04/27" depending on whether or not
that particular Linux image's rmfpms process was restarted or not. It's
really not a big deal, I could just cron a restart of the process for
each time change, I was just looking for another option.

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Fargusson.Alan
Sent: Thursday, April 27, 2006 11:23 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problem with RMFPMS and the recent time change


The way you put this makes me think you set your hardware clock to local
=
time.  This is the wrong approach with Linux (and z/OS actually).

If you set your hardware clock to GMT or UTC then use the correct =
timezone setting the adjustment for daylight savings time is automatic.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Thursday, April 27, 2006 8:07 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Problem with RMFPMS and the recent time change


When we set the clocks ahead a couple of weeks ago, we noticed that each
Linux image using rmfpms to report to the Performance Toolkit was
reporting the wrong time. Restarting the process in Linux resolved the
problem, but we'd rather not have to restart these processes on all of
our images every time the time changes. Is there a way to get around
this?
=20
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

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

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

Problem with RMFPMS and the recent time change

[Wiggins, Mark]

When we set the clocks ahead a couple of weeks ago, we noticed that each
Linux image using rmfpms to report to the Performance Toolkit was
reporting the wrong time. Restarting the process in Linux resolved the
problem, but we'd rather not have to restart these processes on all of
our images every time the time changes. Is there a way to get around
this?
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: After run command "shutdown -r now"...

[Wiggins, Mark]

We just started having this problem too. Our problems started once we
migrated to the 2.6.5-7.244-s390x kernel. In reading through the PTF
(UM31428) as quoted by "Heiko Carstens", it suggests that this PTF
resolves an issue with a DIAG 308. We ran a DIAG TRACE and never saw
DIAG 308 get issued during a "shutdown -r now". We did reach the same
point in the reboot process

=
md: stopping all md devices
md: md0 switched to read-only mode.
Restarting system.
==

And our TRACE seemed to show a DIAG 44 loop. A lot of CPU getting used
with no I/O. Again as stated in the original post, a #CP IPL brought the
server back up successfully. 

Is the UM31428 PTF really the correct PTF for this issue? We're
currently running SLES9 64bit for zSeries under z/VM v5.1 too.

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792




-Original Message-
From: Heiko Carstens [mailto:[EMAIL PROTECTED] 
Sent: Friday, January 13, 2006 5:49 AM
Subject: Re: After run command "shutdown -r now"...


Hi,

> Please teach me.
> I use SLES9 64bit applied SP3 for zSeries under z/VM v5.1.
>
> After I run command "shutdown -r now", z/Linux was
> shutting down normally.
> But next message was displayed in 3270 screen, the system
> didn't start.
>
> =
> md: stopping all md devices
> md: md0 switched to read-only mode.
> Restarting system.
> ==
>
> After the system displayed "Restarting system." in 3270
> screen, system is not receive any commands.
>
> After logoff from z/VM, logon to z/VM again, and I run the
> command " IPL 100 CL", the system is starting normally.
>
> Please teach me solutions.

Depending on your z/VM version you need to install one of the
PTFs for APAR VM63742 in order to fix this:

- z/VM 4.4: UM31426
- z/VM 5.1: UM31428

Heiko

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

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

Off list conversation about Sendmail

[Wiggins, Mark]

Are there any big Sendmail users out here that would be willing to have
a conversation off-list about a problem that I'm having trying to
implement LDAP routing in Sendmail? Just briefly, I keep getting
"Mldap_init/ldap_bind failed to ldaps://ldapauthnz.uconn.edu:636 in map
ldapmh: Protocol error". I'm using Sendmail 8.13.5 on Debian 2.4.21.
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: LVM does not see 2nd LVM on reboot

[Wiggins, Mark]

Did you run mkinitrd and zipl afterwards?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kenneth Libutti
Sent: Friday, September 02, 2005 1:11 PM
To: LINUX-390@VM.MARIST.EDU
Subject: LVM does not see 2nd LVM on reboot


This is a SLES9 sp2 on z/vm.  We have created two lvm groups and then
our required mount points.  We then successfully mount the new slices.
When we reboot the second LVM is not seen nor mounted.  This is all done
through yast.

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

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

Re: Samba

[Wiggins, Mark]

> David Boyes wrote;
> it's got
> about 5 TB of FCP SCSI disk attached.

David, can you (or someone else on the list) talk more about these FCP
devices connected? Basically my question (and I know that I've asked the
same type of question(s) before), revolves around the difference between
natively attached SCSI and emulated SCSI. In the document referenced by
Carsten Otte
(http://www-128.ibm.com/developerworks/linux/linux390/perf/index.html),
I don't see any distinction in how the FCP devices are connected. Maybe
it's implied?

How are your previously mentioned FCP devices connected? 
If natively, do you have redundant paths to these devices? 
If natively, are these redundant paths managed by EVMS or something
else? 

The reason that I ask these questions are because in the document
mentioned above, in the section "FICON and FCP performance", they don't
mention whether or not these devices are natively attached SCSI or
emulated (9336) devices. If they are emulated devices, then I understand
that CP manages the multiple paths (2 and 4 CHPID scenarios), but if
they're natively attached, there's no mention (under "Test environment")
of what manages the multiple paths. Is it EVMS managing them on Linux? 

That's where my real questions come from

What are people using more, emulated or native?
If native, do you use multiple paths to connect these devices?
If yes, do you use EVMS to manage those multiple paths or something else
(what else)? 
And finally, can anyone see any true performance savings or hits from
either way? 

Truthfully, emulated is much easier for me to manage, but if there's a
big performance hit, then I might reconsider. Feel free to use your
biggest bat to beat this in to my head, if you or anyone else feels as
if they've answered these questions before. 

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792




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

Re: TSM 64bit API install problem

[Wiggins, Mark]

First, a hypothetical question directed at I guess IBM (Tivoli),
shouldn't the 64bit version be named TIVsm-API.s390x.rpm and not
TIVsm-API64.s390.rpm? 

Never the less, we use the 32bit versions TIVsm-API.s390.rpm
(TIVsm-API-5.3.0-0) and TIVsm-BA.s390.rpm (TIVsm-BA-5.3.0-0) on our
64bit system (suse 2.6.5-7.193-s390x) and they work fine.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter Rothman
Sent: Thursday, August 18, 2005 9:51 AM
To: LINUX-390@VM.MARIST.EDU
Subject: TSM 64bit API install problem


Anybody experience this and know how to get around it?
32bit install works ok.




sdatztpf1:/tsm # rpm -i TIVsm-API64.s390.rpm
Postinstall of the API

IBM TSM Linux API installation complete.

Be sure to set up the configuration files!

sdatztpf1:/tsm # rpm -i TIVsm-BA.s390.rpm
error: Failed dependencies:
TIVsm-API = 5.3.0 is needed by TIVsm-BA-5.3.0-0
libApiDS.so is needed by TIVsm-BA-5.3.0-0

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

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

Re: Online update using yast

[Wiggins, Mark]

Chances are there was a kernel update included. If so, you would have to
run "mkinitrd" and "zipl" afterwards...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Noll, Ralph
Sent: Wednesday, July 20, 2005 1:50 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Online update using yast


 
How can I do the suse online update
And it leave my system in very bad shape.


I have suse sles9..

I ran the online update yesterday... Cause haven't done it
In about 2-3 months..

Now I can't even get the ethernet to ping.. Network unreachable..

What could I have done.. Or update have done??

Can't recognize my fibre card.. To be able to get to the shark..

Any help or ideas would be greatly appreciated



Ralph Noll 
Operations Manager 
City of Little Rock 

Phone (501) 371-4884 
Fax   (501) 918-5304
mailto:[EMAIL PROTECTED]

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

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

Is sdb.suse.de down???

[Wiggins, Mark]

Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that
didn't work either. Is there anywhere else that I can download updates
from? The address is pingable but not accessible...
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: Is sdb.suse.de down???

[Wiggins, Mark]

I'm just not able to perform an "online update" from
http://sdb.suse.de/download like I've always been able to do in the
past. I've been away for 2 weeks and thought maybe something had
changed. 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Tom Driscoll
Sent: Monday, July 18, 2005 4:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Is sdb.suse.de down???


I can get to it for SLES9 updates but not SLES8. Any ideas? Maybe YAST
differences?
Thanks.



"Wiggins, Mark" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port 
07/18/2005 01:11 PM
Please respond to
Linux on 390 Port 


To
LINUX-390@VM.MARIST.EDU
cc

Subject
Is sdb.suse.de down???






Is the sdb.suse.de site is down. I tried sbd2.suse.de too and that
didn't work either. Is there anywhere else that I can download updates
from? The address is pingable but not accessible...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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


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

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

Re: Am I missing something in SLES8 install?

[Wiggins, Mark]

Thanks, but you can't run dasdfmt command against an FBA device. Also,
the "insmod dasd_mod dasd=0200-0204" partitions the disks. I could run
fdisk against them to partition them and then mke2fs. 

Ok, tried that too and that didn't work either. Again my question falls
back to "can you put the base system on 9336 emulated devices"? These
troubles lead me to think not... 

 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Michael Farmer
Sent: Thursday, June 30, 2005 3:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


It has been awhile but I remember that I had to format it using dasdfmt
and
then mkefs before YAST would allow me to create mountpoints for the
disk. I
had to do this even though it was formatted it by CMS


Michael S Farmer
Systems Programmer
AAA of Missouri
314-523-7350



 "Wiggins, Mark"
 <[EMAIL PROTECTED]
 nn.edu>
To
 Sent by: Linux on LINUX-390@VM.MARIST.EDU
 390 Port
cc
 <[EMAIL PROTECTED]
 IST.EDU>
Subject
   Re: Am I missing something in
SLES8
   install?
 06/30/2005 01:58
 PM


 Please respond to
 Linux on 390 Port
 <[EMAIL PROTECTED]
 IST.EDU>






Anyone else out there have any ideas???

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 2:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


**slam**

Chris hitting the knowledge barrier.  It hurts when that happens.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 1:00 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Did you see that they are 9336 FBA devices? I wouldn't think that they
would
show up on this screen because they're not ECKD devices, but when I do
enter
in the dasd= parameter in yast, they still don't show up.
Clicking on the "accept" button does nothing so my only alternative at
this
point is to click on the "abort" button.



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 1:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


On the yast screen, enter "dasd=xxxx-" etc.  then click accept.
they
should pop up.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Well, that at least created /proc/dasd/devices and an lsmod command
shows
that all of the appropriate modules are loaded, yet I still get the
"YAST2 -
DASD Module Parameter Setting" screen to which I have to "abort" out of
and
receive an error suggesting that "there are no DASD devices active".
This
then takes me to the "Installation Settings"
screen where the "Software" screen with "not enough disk space", etc...

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 12:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


my usual pattern is thus

insmod dasd_mod "dasd=-"
insmod dasd_eckd
etc.

then run the install.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 11:32 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Ok, I insmod dasd_mod, dasd_eckd_mod, dasd_diag_mod and dasd_fba_mod.
Then I run "modprobe dasd_mod dasd=0200-0204,0222". I get nothing back
and
/proc/dasd/devices does not get updated. I end up in the small spot.
Am I missing an appropriate mod or is my modprobe command incomplete?


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 11:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


Known bug with SLES 8.  open a ssh session and manually insmod the dasd
modules and device parameters before beginning the installation.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 9:55 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Am I missing something in SLES8 install?

We have a need to install SLES8 as opposed to SLES9 like we normally do,
so
this is my first attempt at a SLES8 install.

When I get to the "YAST2 - DASD Module Parameter Settings" screen, I
ent

Re: Am I missing something in SLES8 install?

[Wiggins, Mark]

Anyone else out there have any ideas???

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 2:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


**slam**

Chris hitting the knowledge barrier.  It hurts when that happens.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 1:00 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Did you see that they are 9336 FBA devices? I wouldn't think that they
would
show up on this screen because they're not ECKD devices, but when I do
enter
in the dasd= parameter in yast, they still don't show up.
Clicking on the "accept" button does nothing so my only alternative at
this
point is to click on the "abort" button.



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 1:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


On the yast screen, enter "dasd=-" etc.  then click accept.
they
should pop up.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Well, that at least created /proc/dasd/devices and an lsmod command
shows
that all of the appropriate modules are loaded, yet I still get the
"YAST2 -
DASD Module Parameter Setting" screen to which I have to "abort" out of
and
receive an error suggesting that "there are no DASD devices active".
This
then takes me to the "Installation Settings"
screen where the "Software" screen with "not enough disk space", etc...

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 12:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


my usual pattern is thus

insmod dasd_mod "dasd=-"
insmod dasd_eckd
etc.

then run the install.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 11:32 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Ok, I insmod dasd_mod, dasd_eckd_mod, dasd_diag_mod and dasd_fba_mod.
Then I run "modprobe dasd_mod dasd=0200-0204,0222". I get nothing back
and
/proc/dasd/devices does not get updated. I end up in the small spot.
Am I missing an appropriate mod or is my modprobe command incomplete?


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 11:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


Known bug with SLES 8.  open a ssh session and manually insmod the dasd
modules and device parameters before beginning the installation.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 9:55 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Am I missing something in SLES8 install?

We have a need to install SLES8 as opposed to SLES9 like we normally do,
so
this is my first attempt at a SLES8 install.

When I get to the "YAST2 - DASD Module Parameter Settings" screen, I
enter
"dasd=0200-0204,0222" and click on the "Load Module" button. We're using
9336 emulated FBA devices which I CMS formatted. From the VM console I
can
see where /proc/dasd/devices is set up and each device is allocated to a
device letter (e.g. /dev/dasda, /dev/dasdb, etc). At this point I have
to
"Abort" from the "DASD Module screen", I'm assuming because I don't have
any
ECKD devices, only FBA devices??? Anyway, this then takes me to the
"Installation Settings" screen where I'm able to set up the partitioning
of
all of my disk.

This is where the real problem starts. In SLES9 after I set up all of my
partitioning and exit the "YAST2 - Partitioner" screen, the "Software"
screen knows what I've just done and allows me to choose what software I
want based on how much space I have just allocated. In SLES8, this
doesn't
happen and the "YAST2 - Software" screen shows "NOT ENOUGH DISK SPACE
EVEN
FOR A MINIMAL INSTALLATION". What am I doing wrong? Can I not install
the
base SLES8 system on 9336 devices?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

-

Re: Am I missing something in SLES8 install?

[Wiggins, Mark]

Did you see that they are 9336 FBA devices? I wouldn't think that they
would show up on this screen because they're not ECKD devices, but when
I do enter in the dasd= parameter in yast, they still don't show up.
Clicking on the "accept" button does nothing so my only alternative at
this point is to click on the "abort" button.



-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 1:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


On the yast screen, enter "dasd=-" etc.  then click accept.
they
should pop up.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 12:30 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Well, that at least created /proc/dasd/devices and an lsmod command
shows
that all of the appropriate modules are loaded, yet I still get the
"YAST2 -
DASD Module Parameter Setting" screen to which I have to "abort" out of
and
receive an error suggesting that "there are no DASD devices active".
This
then takes me to the "Installation Settings"
screen where the "Software" screen with "not enough disk space", etc...

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 12:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


my usual pattern is thus

insmod dasd_mod "dasd=-"
insmod dasd_eckd
etc.

then run the install.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 11:32 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Ok, I insmod dasd_mod, dasd_eckd_mod, dasd_diag_mod and dasd_fba_mod.
Then I run "modprobe dasd_mod dasd=0200-0204,0222". I get nothing back
and
/proc/dasd/devices does not get updated. I end up in the small spot.
Am I missing an appropriate mod or is my modprobe command incomplete?


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 11:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


Known bug with SLES 8.  open a ssh session and manually insmod the dasd
modules and device parameters before beginning the installation.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 9:55 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Am I missing something in SLES8 install?

We have a need to install SLES8 as opposed to SLES9 like we normally do,
so
this is my first attempt at a SLES8 install.

When I get to the "YAST2 - DASD Module Parameter Settings" screen, I
enter
"dasd=0200-0204,0222" and click on the "Load Module" button. We're using
9336 emulated FBA devices which I CMS formatted. From the VM console I
can
see where /proc/dasd/devices is set up and each device is allocated to a
device letter (e.g. /dev/dasda, /dev/dasdb, etc). At this point I have
to
"Abort" from the "DASD Module screen", I'm assuming because I don't have
any
ECKD devices, only FBA devices??? Anyway, this then takes me to the
"Installation Settings" screen where I'm able to set up the partitioning
of
all of my disk.

This is where the real problem starts. In SLES9 after I set up all of my
partitioning and exit the "YAST2 - Partitioner" screen, the "Software"
screen knows what I've just done and allows me to choose what software I
want based on how much space I have just allocated. In SLES8, this
doesn't
happen and the "YAST2 - Software" screen shows "NOT ENOUGH DISK SPACE
EVEN
FOR A MINIMAL INSTALLATION". What am I doing wrong? Can I not install
the
base SLES8 system on 9336 devices?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

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

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

-

Re: Am I missing something in SLES8 install?

[Wiggins, Mark]

Well, that at least created /proc/dasd/devices and an lsmod command
shows that all of the appropriate modules are loaded, yet I still get
the "YAST2 - DASD Module Parameter Setting" screen to which I have to
"abort" out of and receive an error suggesting that "there are no DASD
devices active". This then takes me to the "Installation Settings"
screen where the "Software" screen with "not enough disk space", etc...

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 12:36 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


my usual pattern is thus

insmod dasd_mod "dasd=-"
insmod dasd_eckd
etc.

then run the install.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 11:32 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?

Ok, I insmod dasd_mod, dasd_eckd_mod, dasd_diag_mod and dasd_fba_mod.
Then I run "modprobe dasd_mod dasd=0200-0204,0222". I get nothing back
and
/proc/dasd/devices does not get updated. I end up in the small spot.
Am I missing an appropriate mod or is my modprobe command incomplete?


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 11:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


Known bug with SLES 8.  open a ssh session and manually insmod the dasd
modules and device parameters before beginning the installation.

-Original Message-
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 9:55 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Am I missing something in SLES8 install?

We have a need to install SLES8 as opposed to SLES9 like we normally do,
so
this is my first attempt at a SLES8 install.

When I get to the "YAST2 - DASD Module Parameter Settings" screen, I
enter
"dasd=0200-0204,0222" and click on the "Load Module" button. We're using
9336 emulated FBA devices which I CMS formatted. From the VM console I
can
see where /proc/dasd/devices is set up and each device is allocated to a
device letter (e.g. /dev/dasda, /dev/dasdb, etc). At this point I have
to
"Abort" from the "DASD Module screen", I'm assuming because I don't have
any
ECKD devices, only FBA devices??? Anyway, this then takes me to the
"Installation Settings" screen where I'm able to set up the partitioning
of
all of my disk.

This is where the real problem starts. In SLES9 after I set up all of my
partitioning and exit the "YAST2 - Partitioner" screen, the "Software"
screen knows what I've just done and allows me to choose what software I
want based on how much space I have just allocated. In SLES8, this
doesn't
happen and the "YAST2 - Software" screen shows "NOT ENOUGH DISK SPACE
EVEN
FOR A MINIMAL INSTALLATION". What am I doing wrong? Can I not install
the
base SLES8 system on 9336 devices?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

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

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

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

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

Re: Am I missing something in SLES8 install?

[Wiggins, Mark]

Ok, I insmod dasd_mod, dasd_eckd_mod, dasd_diag_mod and dasd_fba_mod.
Then I run "modprobe dasd_mod dasd=0200-0204,0222". I get nothing back
and /proc/dasd/devices does not get updated. I end up in the small spot.
Am I missing an appropriate mod or is my modprobe command incomplete?


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Little, Chris
Sent: Thursday, June 30, 2005 11:06 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Am I missing something in SLES8 install?


Known bug with SLES 8.  open a ssh session and manually insmod the dasd
modules and device parameters before beginning the installation.

-Original Message-----
From: Wiggins, Mark [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 30, 2005 9:55 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Am I missing something in SLES8 install?

We have a need to install SLES8 as opposed to SLES9 like we normally do,
so
this is my first attempt at a SLES8 install.

When I get to the "YAST2 - DASD Module Parameter Settings" screen, I
enter
"dasd=0200-0204,0222" and click on the "Load Module" button. We're using
9336 emulated FBA devices which I CMS formatted. From the VM console I
can
see where /proc/dasd/devices is set up and each device is allocated to a
device letter (e.g. /dev/dasda, /dev/dasdb, etc). At this point I have
to
"Abort" from the "DASD Module screen", I'm assuming because I don't have
any
ECKD devices, only FBA devices??? Anyway, this then takes me to the
"Installation Settings" screen where I'm able to set up the partitioning
of
all of my disk.

This is where the real problem starts. In SLES9 after I set up all of my
partitioning and exit the "YAST2 - Partitioner" screen, the "Software"
screen knows what I've just done and allows me to choose what software I
want based on how much space I have just allocated. In SLES8, this
doesn't
happen and the "YAST2 - Software" screen shows "NOT ENOUGH DISK SPACE
EVEN
FOR A MINIMAL INSTALLATION". What am I doing wrong? Can I not install
the
base SLES8 system on 9336 devices?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

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

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

Am I missing something in SLES8 install?

[Wiggins, Mark]

We have a need to install SLES8 as opposed to SLES9 like we normally do,
so this is my first attempt at a SLES8 install. 
 
When I get to the "YAST2 - DASD Module Parameter Settings" screen, I
enter "dasd=0200-0204,0222" and click on the "Load Module" button. We're
using 9336 emulated FBA devices which I CMS formatted. From the VM
console I can see where /proc/dasd/devices is set up and each device is
allocated to a device letter (e.g. /dev/dasda, /dev/dasdb, etc). At this
point I have to "Abort" from the "DASD Module screen", I'm assuming
because I don't have any ECKD devices, only FBA devices??? Anyway, this
then takes me to the "Installation Settings" screen where I'm able to
set up the partitioning of all of my disk. 
 
This is where the real problem starts. In SLES9 after I set up all of my
partitioning and exit the "YAST2 - Partitioner" screen, the "Software"
screen knows what I've just done and allows me to choose what software I
want based on how much space I have just allocated. In SLES8, this
doesn't happen and the "YAST2 - Software" screen shows "NOT ENOUGH DISK
SPACE EVEN FOR A MINIMAL INSTALLATION". What am I doing wrong? Can I not
install the base SLES8 system on 9336 devices? 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: sles9 and evms

[Wiggins, Mark]

We've got a couple multipathed evms volumes up under SLES9. The best
document that I've found was 'Linux for zSeries Fibre Channel Protocol
Implementation Guide"
http://www.redbooks.ibm.com/redbooks/pdfs/sg246344.pdf. Chapter 9
"Multipath FCP on Suse SLES9".

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Herve Bonvin
Sent: Monday, June 06, 2005 10:49 AM
To: LINUX-390@VM.MARIST.EDU
Subject: sles9 and evms


Hi,

I am trying to install and test sles9 with evms and multipathing.

I can't find useful documentation about evms_mpathd. This deamon seems
to be started with evmsgui but it is not restarted after a reboot.

Is anyone using sles9 with multipathing in production ?

I don't have a good feeling about it. Multipathing with sles8 and lvm
was pretty simple.
evms seems complicated and not a lot documentations are available.

Best Regards,
Herve






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

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

Re: Problem installing Debian

[Wiggins, Mark]

Thank you for your reply... Could I maybe get that initrd2 file that you
mentioned? I tried both rc2 and rc3 but neither liked my 9336 devices. I
installed Debian before but I CTC connected it and then converted it to
QDIO. It just seemed like this should be easy enough to start with QDIO
connection, but I haven't had the best of luck. Thanks again for your
help.

Mark Wiggins

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Adam Thornton
Sent: Tuesday, May 03, 2005 3:37 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problem installing Debian


On May 3, 2005, at 2:29 PM, Wiggins, Mark wrote:

> Ok, I've beat my head against the wall for 2 days now, googled,
> searched
> archives, etc... I can't find this anywhere.
>
>  - I went out and downloaded the kernel.debian, initrd.debian and
> parmfile.debian files from
> ftp://ftp.us.debian.org/debian/dists/woody/main/disks-
> s390/3.0.23-2002-0
> 521/vmrdr/.
>  - I downloaded qdio-2.4.17-s390-7.tar.gz
> <http://awlinux1.alphaworks.ibm.com/developerworks/linux390/
> current2_4_x
> -august2001.shtml#ocos2417_20031205>  and qeth-2.4.17-s390-7.tar.gz
> <http://awlinux1.alphaworks.ibm.com/developerworks/linux390/
> current2_4_x
> -august2001.shtml#ocos2417_20031205>  from
> http://awlinux1.alphaworks.ibm.com/developerworks/linux390/
> current2_4_x-
> august2001.shtml#ocos2417_20031205.
>  - I downloaded the mkinitrd2.sh file from people.debian.org/
> ~sgybas and
> created the initrd2.debian file.
>  - I've ftp'd these files to VM (using all of the right ftp settings -
> bin, locsite fix 80, etc).
>  - I then execute my debian exec on z/VM 5.1.
>  - It comes up with option "4" (qeth: OSA-Express in QDIO mode /
> HiperSockets) but when I try to go from there I get
>
> Unresolved symbols show_trace in qeth.o
>
> Are these files not the latest? How do I get around this?
>
I suspect the problem is that those files are *too* recent.

Contact me offlist for an initrd2 known to work with Debian 3.0 Woody.

However, my *real* suggestion is to forget Woody and try installing
using Sarge and Debian-installer.  You'll get a much-closer-to-
current Debian system that way.

http://ftp.debian.org/debian/dists/testing/main/installer-s390/rc3/
images/

I haven't actually tried RC3 myself, but rc2 worked fine.  I've heard
some reports that virtual Hipersockets don't work but I have not been
able to reproduce that.

Adam

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

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

Problem installing Debian

[Wiggins, Mark]

Ok, I've beat my head against the wall for 2 days now, googled, searched
archives, etc... I can't find this anywhere.
 
 - I went out and downloaded the kernel.debian, initrd.debian and
parmfile.debian files from
ftp://ftp.us.debian.org/debian/dists/woody/main/disks-s390/3.0.23-2002-0
521/vmrdr/. 
 - I downloaded qdio-2.4.17-s390-7.tar.gz
  and qeth-2.4.17-s390-7.tar.gz
  from
http://awlinux1.alphaworks.ibm.com/developerworks/linux390/current2_4_x-
august2001.shtml#ocos2417_20031205. 
 - I downloaded the mkinitrd2.sh file from people.debian.org/~sgybas and
created the initrd2.debian file. 
 - I've ftp'd these files to VM (using all of the right ftp settings -
bin, locsite fix 80, etc).
 - I then execute my debian exec on z/VM 5.1.
 - It comes up with option "4" (qeth: OSA-Express in QDIO mode /
HiperSockets) but when I try to go from there I get 
 
Unresolved symbols show_trace in qeth.o
 
Are these files not the latest? How do I get around this?
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792
 
 
 

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

What file server are you running???

[Wiggins, Mark]

We've begun a file server migration project in hopes of replacing our
current Novell file servers. Our initial plan was to implement a Samba
server running on z/Linux/SLES9, integrated with Active Directory. We
ran into a view snags so we looked at AFS. AFS didn't seem to like
z/Linux very much so we're just wondering what are others out there
using? Is there anyone out there that is running a large file server on
z/Linux and if so, can you just send me (offline if you want) the brief
particulars (e.g. Linux distro, file server, authentication mechanism,
maybe a little sizing information, etc...), just so I can start with an
already "z/Linux" proven direction? I'm just to to get away from
re-inventing the wheel.
 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792
 

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

Re: Suse/s390 patches

[Wiggins, Mark]

This brings up an interesting question. I've set up a YOU server to
synchronize itself on a daily basis with SuSE. All of the rest of my
Linux instances do their "Online Updates" against my YOU server instead
of going over the wire to SuSE. If someone from outside of UConn were to
pull updates off of my YOU server, would this be a contractual no-no???
If so, how are others doing this? I guess checking the "SLP Registration
Enabled" box would be bad form in this scenario too?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Wolfe, Gordon W
Sent: Tuesday, April 19, 2005 3:00 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse/s390 patches


You can get them from the SuSE maintenance portal, but only if you've
paid SuSE for service and have an account there.

"A statesman is a dead politician.  Lord knows we need more statesmen!" 
--Berkeley Breathed
Gordon Wolfe, Ph.D.  Boeing Shared Services Group
Enterprise Servers VM Technical Services 425-865-5940

> --
> From: jason lowe
> Reply To: Linux on 390 Port
> Sent: Tuesday, April 19, 2005 11:45 AM
> To:   LINUX-390@VM.MARIST.EDU
> Subject:  Suse/s390 patches
> 
> Where on the Internet, can I get Suse/390 patches?
> 
> JL
> 
> Jason Lowe - Mainframe Systems  - Cornell Information Technologies
> [EMAIL PROTECTED]
> (607) 255-7851
> 
> The Supreme Court has surrendered.
>   It has destroyed the Civil Rights Bill, and converted the Republican
> party into a party of money rather than a party of morals.
> 
>
Frederick
> Douglass, 1894
> 
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to [EMAIL PROTECTED] with the message: INFO LINUX-390
or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> 
> 

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

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

Re: Problems with SUSE LINUX install

[Wiggins, Mark]

We had the same type of problems using FTP. When I used NFS instead,
problem was resolved. And I always use VNC at 256M with no problems,
512M should be fine...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
George Dranes
Sent: Wednesday, April 06, 2005 10:31 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Problems with SUSE LINUX install


I'm attempting to install SUSE LINUX Enterprise Server 9 (64 bit) for
IBM
zSeries on an LPAR.  I've assigned 512MB to the partition along with a
3390
mod3 as a swap partition.  I'm trying to install from an FTP server on
which
I've set up an installroot directory with core9 and sles9 directories
under
it as per Novell's online documentation.  I am able to connect to the
VNCSERVER and am using YAST to install.  I get to the Finishing Basic
Installation creating initrd 62% complete screen and it just appears to
hang
and installation never completes.  I was hoping someone out there has
run
into a similar issue with SUSE LINUX.  Any help would be appreciated.
Thanks.




University Information Management Systems
George Dranes
Manager-Technical Services
[EMAIL PROTECTED]
Morgan Hall 121
1 University Circle
Macomb, IL 61455-1390
tel: 309-298-1097 X261
fax: 309-298-1451


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

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

Pros and cons - emulated FBA or FCP-attached SCSI???

[Wiggins, Mark]

After reading the following
http://www.vm.ibm.com/perf/reports/zvm/html/scsi.html I became very
confused (like I wasn't already)... Anyway, we're trying to move along
with a file server project and because of strict time lines, I'm trying
to avoid reinventing the wheel. Below is a quick rundown of our system. 
 
We've got a z890 running z/VM 5.1 on one IFL. We're running several
instances of SLES9 in 64 bit mode. Our storage is on a shark and we have
one SAN defined with 2 fabrics. We define our devices in 3 ways, both in
an effort to have some redundancy;
 
- As your traditional 3390 device (not a part of this question).
- As an emulated FBA minidisk (9336) with two defined paths (one
through each fabric).  
- And as a FCP device, using EVMS on Linux to multipath through each
fabric.
 
My questions are about the latter two devices. The above document only
talks about single path connectivity. How would multipathing effect
these different devices? How does the multiple layers (e.g. EVMS, LVM,
etc...) effect these devices? In the document above it suggests a
substantial increase in CPU for an I/O operation to an FBA device as
opposed to an FCP device, how would multipathing effect this? How much
overhead is there with EVMS maintaining a multipathed FCP device?
Lastly, LVM1 is only available for an EVMS managed disk, is there a
noticeable increase in overhead between LVM1 and LVM2 (which can be used
with a FBA device)?
 
I guess I don't really need specific answers to these questions, just an
idea as to what others are doing. Like I said before, I'd rather not
reinvent the wheel. If anyone could shed some light on which one of
these devices (Emulated/multipathed/LVM2/FBA or EVMS/LVM1/FCP)
would/should perform better, that would be GREAT! 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792
 
 

 
 
 
 
 

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

Re: FW: SLES9 + OpenAFS Server

[Wiggins, Mark]

1.2.11-20.1

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kris Van Hees
Sent: Thursday, March 24, 2005 3:51 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FW: SLES9 + OpenAFS Server


On Thu, Mar 24, 2005 at 03:49:24PM -0500, Wiggins, Mark wrote:
> We bumped memory from 256M to 512M, should I keep going higher?

What version of OpenAFS are you trying?

Kris

> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Mark D Pace
> Sent: Thursday, March 24, 2005 3:26 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: FW: SLES9 + OpenAFS Server
>
>
> I'm not running OpenAFS, but typically a segfault is an indication of
> not
> enough memory.  Bump your Linux memory size or swap file size.
>
>
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
> 1700 Summit Lake Drive
> Tallahassee, FL. 32317
> Office: 850.219.5184
> Fax: 888.221.9862
> http://www.mainline.com
>
>
>
>  "Wiggins, Mark"
>  <[EMAIL PROTECTED]
>  nn.edu>
> To
>  Sent by: Linux on LINUX-390@VM.MARIST.EDU
>  390 Port
> cc
>  <[EMAIL PROTECTED]
>  IST.EDU>
> Subject
>FW: SLES9 + OpenAFS Server
>
>  03/24/2005 03:22
>  PM
>
>
>  Please respond to
>  Linux on 390 Port
>  <[EMAIL PROTECTED]
>  IST.EDU>
>
>
>
>
>
>
> I have installed the OpenAFS-server via YaST (and the dependency
> "OpenAFS") on SLES9.  Using README.SuSE as a guide, I
> issue /usr/sbin/bosserver -noauth, which immediately segfaults.  Is
> anyone successfully running OpenAFS Server on SLES9/s390x?  I have
> included an strace below.  Any thoughts on how to correct this are
much
> appreciated.
>
> execve("/usr/sbin/bosserver", ["/usr/sbin/bosserver"], [/* 50 vars
*/])
> = 0
> uname({sys="Linux", node="lnxzvm13", ...}) = 0
> brk(0)  = 0x80056000
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0)
> = 0x201a000
> open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.cache", O_RDONLY)  = 3
> fstat(3, {st_mode=S_IFREG|0644, st_size=23688, ...}) = 0
> mmap(NULL, 23688, PROT_READ, MAP_PRIVATE, 3, 0) = 0x201b000
> close(3)= 0
> open("/lib64/libresolv.so.2", O_RDONLY) = 3
> read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\26\0\0\0\1\0\0\0"...,
> 640) = 640
> fstat(3, {st_mode=S_IFREG|0755, st_size=99784, ...}) = 0
> mmap(NULL, 101280, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
> 0x2021000
> madvise(0x2021000, 101280, MADV_SEQUENTIAL|0x1) = 0
> mmap(0x2035000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED,
> 3, 0x13000) = 0x2035000
> mmap(0x2038000, 7072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
> MAP_ANONYMOUS, -1, 0) = 0x2038000
> close(3)= 0
> open("/lib64/tls/libc.so.6", O_RDONLY)  = 3
> read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\26\0\0\0\1\0\0\0"...,
> 640) = 640
> lseek(3, 624, SEEK_SET) = 624
> read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6"...,
32)
> = 32
> fstat(3, {st_mode=S_IFREG|0755, st_size=1542343, ...}) = 0
> mmap(NULL, 1331472, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
> 0x203a000
> madvise(0x203a000, 1331472, MADV_SEQUENTIAL|0x1) = 0
> mmap(0x215f000, 118784, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED,
> 3, 0x124000) = 0x215f000
> mmap(0x217c000, 12560, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|
> MAP_ANONYMOUS, -1, 0) = 0x217c000
> close(3)= 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0)
> = 0x218
> munmap(0x201b000, 23688)= 0
> geteuid()   = 0
> brk(0)  = 0x80056000
> brk(0x80077000) = 0x80077000
> brk(0)  = 0x80077000
> mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1,
> 0) = 0x2181000
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
>
>
>
> Matthew J. Smith
> University of Connecticut ITS
> This message sent at Thu Mar 24 14:52:29 2005
> PGP Key: http://web.uconn.edu/dotmatt/matt.asc
>
> 

Re: FW: SLES9 + OpenAFS Server

[Wiggins, Mark]

We bumped memory from 256M to 512M, should I keep going higher? 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark D Pace
Sent: Thursday, March 24, 2005 3:26 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FW: SLES9 + OpenAFS Server


I'm not running OpenAFS, but typically a segfault is an indication of
not
enough memory.  Bump your Linux memory size or swap file size.



Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
Office: 850.219.5184
Fax: 888.221.9862
http://www.mainline.com



 "Wiggins, Mark"
 <[EMAIL PROTECTED]
 nn.edu>
To
 Sent by: Linux on LINUX-390@VM.MARIST.EDU
 390 Port
cc
 <[EMAIL PROTECTED]
 IST.EDU>
Subject
   FW: SLES9 + OpenAFS Server

 03/24/2005 03:22
 PM


 Please respond to
 Linux on 390 Port
 <[EMAIL PROTECTED]
 IST.EDU>






I have installed the OpenAFS-server via YaST (and the dependency
"OpenAFS") on SLES9.  Using README.SuSE as a guide, I
issue /usr/sbin/bosserver -noauth, which immediately segfaults.  Is
anyone successfully running OpenAFS Server on SLES9/s390x?  I have
included an strace below.  Any thoughts on how to correct this are much
appreciated.

execve("/usr/sbin/bosserver", ["/usr/sbin/bosserver"], [/* 50 vars */])
= 0
uname({sys="Linux", node="lnxzvm13", ...}) = 0
brk(0)  = 0x80056000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x201a000
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)  = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=23688, ...}) = 0
mmap(NULL, 23688, PROT_READ, MAP_PRIVATE, 3, 0) = 0x201b000
close(3)= 0
open("/lib64/libresolv.so.2", O_RDONLY) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\26\0\0\0\1\0\0\0"...,
640) = 640
fstat(3, {st_mode=S_IFREG|0755, st_size=99784, ...}) = 0
mmap(NULL, 101280, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x2021000
madvise(0x2021000, 101280, MADV_SEQUENTIAL|0x1) = 0
mmap(0x2035000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x13000) = 0x2035000
mmap(0x2038000, 7072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0x2038000
close(3)= 0
open("/lib64/tls/libc.so.6", O_RDONLY)  = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\26\0\0\0\1\0\0\0"...,
640) = 640
lseek(3, 624, SEEK_SET) = 624
read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6"..., 32)
= 32
fstat(3, {st_mode=S_IFREG|0755, st_size=1542343, ...}) = 0
mmap(NULL, 1331472, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x203a000
madvise(0x203a000, 1331472, MADV_SEQUENTIAL|0x1) = 0
mmap(0x215f000, 118784, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x124000) = 0x215f000
mmap(0x217c000, 12560, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0x217c000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x218
munmap(0x201b000, 23688)= 0
geteuid()   = 0
brk(0)  = 0x80056000
brk(0x80077000) = 0x80077000
brk(0)  = 0x80077000
mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2181000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++



Matthew J. Smith
University of Connecticut ITS
This message sent at Thu Mar 24 14:52:29 2005
PGP Key: http://web.uconn.edu/dotmatt/matt.asc

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


This e-mail and files transmitted with it are confidential, and are
intended solely for the use of the individual or entity to whom this
e-mail
is addressed.  If you are not the intended recipient, or the employee or
agent responsible to deliver it to the intended recipient, you are
hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited.  If you are not one of the named
recipient(s) or otherwise have reason to believe that you received this
message in error, please immediately notify sender by e-mail, and
destroy
the original message.  Thank You.

--
For LINUX-390 subscribe / signof

FW: SLES9 + OpenAFS Server

[Wiggins, Mark]

I have installed the OpenAFS-server via YaST (and the dependency
"OpenAFS") on SLES9.  Using README.SuSE as a guide, I
issue /usr/sbin/bosserver -noauth, which immediately segfaults.  Is
anyone successfully running OpenAFS Server on SLES9/s390x?  I have
included an strace below.  Any thoughts on how to correct this are much
appreciated.

execve("/usr/sbin/bosserver", ["/usr/sbin/bosserver"], [/* 50 vars */])
= 0
uname({sys="Linux", node="lnxzvm13", ...}) = 0
brk(0)  = 0x80056000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x201a000
open("/etc/ld.so.preload", O_RDONLY)= -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)  = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=23688, ...}) = 0
mmap(NULL, 23688, PROT_READ, MAP_PRIVATE, 3, 0) = 0x201b000
close(3)= 0
open("/lib64/libresolv.so.2", O_RDONLY) = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\26\0\0\0\1\0\0\0"...,
640) = 640
fstat(3, {st_mode=S_IFREG|0755, st_size=99784, ...}) = 0
mmap(NULL, 101280, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x2021000
madvise(0x2021000, 101280, MADV_SEQUENTIAL|0x1) = 0
mmap(0x2035000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x13000) = 0x2035000
mmap(0x2038000, 7072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0x2038000
close(3)= 0
open("/lib64/tls/libc.so.6", O_RDONLY)  = 3
read(3, "\177ELF\2\2\1\0\0\0\0\0\0\0\0\0\0\3\0\26\0\0\0\1\0\0\0"...,
640) = 640
lseek(3, 624, SEEK_SET) = 624
read(3, "\0\0\0\4\0\0\0\20\0\0\0\1GNU\0\0\0\0\0\0\0\0\2\0\0\0\6"..., 32)
= 32
fstat(3, {st_mode=S_IFREG|0755, st_size=1542343, ...}) = 0
mmap(NULL, 1331472, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) =
0x203a000
madvise(0x203a000, 1331472, MADV_SEQUENTIAL|0x1) = 0
mmap(0x215f000, 118784, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED,
3, 0x124000) = 0x215f000
mmap(0x217c000, 12560, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0x217c000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0)
= 0x218
munmap(0x201b000, 23688)= 0
geteuid()   = 0
brk(0)  = 0x80056000
brk(0x80077000) = 0x80077000
brk(0)  = 0x80077000
mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2181000
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++



Matthew J. Smith
University of Connecticut ITS
This message sent at Thu Mar 24 14:52:29 2005
PGP Key: http://web.uconn.edu/dotmatt/matt.asc

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

Re: More CPU in SLES9

[Wiggins, Mark]

So I'm sure this has been asked before but I couldn't find much about
it. If the "default" is set to 1, is there a down side to setting it to
0? In other words, in what types of circumstances would you NOT want to
change this variable? 

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
John Schnitzler Jr
Sent: Wednesday, March 23, 2005 5:07 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: More CPU in SLES9


Sorry, You're right, I just googled it and the value should be 0.

The Novell/SUSE SLES 8 and SLES 9 distribution delivers the kernel with
the Timer Patch enabled. It can be disabled by the kernel config option
CONFIG_NO_IDLE_HZ=n and a kernel recompile.
Alternatively the Timer Patch can be activated and deactivated with the
following convenient method. Use the sysctl command to switch the
setting
in the proc file system:
1.  'sysctl -w kernel.hz_timer=1' enables the 100 Hz timer. The
Timer
Patch is deactivated.
2.  'sysctl -w kernel.hz_timer=0' disables the 100 Hz timer. The
Timer
Patch is activated.

Regards,
John


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

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

Re: CPINT Question

[Wiggins, Mark]

I wasn't following this thread real close so if I repeat something, I'm
sorry. I've found that the 

"/sbin/dasd_configure 0.0.0298 1 0"

command works the same as the old "echo add device range="
command used to in SLES8. 

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Ferguson, Neale
Sent: Friday, March 18, 2005 3:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: CPINT Question


Didn't you used to have echo "add dasd=298" >/proc/dasd/devices in
SLES8?

With udev and hotplug a script could probably automate this for you.

-Original Message-
chccwdev -e 0.0.0298
Setting device 0.0.0298 online
Done
lnx5:~ # cat /proc/dasd/devices
0.0.0292(ECKD) at ( 94: 0) is dasda   : active at blocksize:
4096, 90144
0 blocks, 3521 MB
0.0.0293(FBA ) at ( 94: 4) is dasdb   : active at blocksize:
512, 50
 blocks, 244 MB
0.0.0295(ECKD) at ( 94:12) is dasdd   : active at blocksize:
4096, 60084
0 blocks, 2347 MB
0.0.0298(ECKD) at ( 94:24) is dasdg   : basic

That seems to work.  Why do I have to do this in SLES9 when I didn't
have to in SLES8?

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

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

Re: How to dynamically add new DASD under sles9?

[Wiggins, Mark]

I've found the following works for me

/sbin/dasd_configure 0.0. 1 0

Of course, where  equals the device number. Something like this
should work the same as the old - echo "add device range=" command.
You can also go in through YaST2, hardware, DASD, select device,
activate --- works too!

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Peter E. Abresch Jr. - at Pepco
Sent: Saturday, February 19, 2005 2:49 PM
To: LINUX-390@VM.MARIST.EDU
Subject: How to dynamically add new DASD under sles9?


I though I have seen this mention a hundred times, but now that I need
it,
I cannot find it anywhere.

Under sles8, I was able to dynamically added dasd by issuing:

echo "add device range=191" >> /proc/dasd/devices

However, this does not appear to work under sles9. Can someone point me
in
the right direction? Thanks.

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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

LVM volume group isn't available after a reboot

[Wiggins, Mark]

We've got one test instance of SLES9 on z/VM 5.1 that has the following
disk layout
 
MDISK  200 3380   /dev/dasda1 /bootext3
defaults
MDISK  201 3380   /dev/dasdb1 /   reiserfsacl,user_xattr
MDISK  202 3380   /dev/dasdc1 /usrreiserfsacl,user_xattr

MDISK  203 3380   /dev/dasdd1 swapswappri=42
MDISK  204 3380   /dev/system/OPT  /opt reiserfs
defaults 
/dev/system/VAR  /var
reiserfs   defaults
/dev/system/SRV  /srv
reiserfs   defaults   
 
You'll notice that the 204 disk is running LVM with opt, var and srv
running on it. 
 
My question is that sometimes (and I mean about 80% of time), when you
issue a reboot (either reboot or shutdown -r), the instance is unable to
bring the LVM devices back up. If you shut it down all the way, it comes
back fine, only rebooting has trouble. It's unable to find the volume
group "system" and thus can't mount the lv's. 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


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

Re: EVMS question for FCP device

[Wiggins, Mark]

Thank you, that worked. I saw that reply earlier but when I searched the
logs I couldn't find it. This would also suggest that this is fixed with
SP1 then.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Robert J Brenneman
Sent: Thursday, January 27, 2005 3:25 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: EVMS question for FCP device


Try mounting /dev/evms/md/md0 with the barrier option turned off.

for reiser like this:  mount /dev/evms/md/md0 / -o
barrier=none

for ext3 like this: mount /dev/evms/md/md0 / -o barrier=0

Jay Brenneman

Linux Test and Integration Center

T/L:   295 - 7745
Extern: 845 - 435 - 7745
[EMAIL PROTECTED]





"Wiggins, Mark" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port 
27/01/2005 13:40
Please respond to
Linux on 390 Port


To
LINUX-390@VM.MARIST.EDU
cc

Subject
EVMS question for FCP device






I've been trying to get a multipath FCP device attach to my SLES9
instance on z/VM 5.1. I feel as though I've followed the directions
(Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up
getting either a "broken pipe" error when trying to mount it from
EVMSGUI and I get "wrong fs type, bad option, bad superblock on
/dev/evms/md/md0, or too many mounted file systems" when I try to mount
it on linux. Quickly, let me go through the steps and see if anyone can
see where I've went wrong.

ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP).
ATT A310 to LINUX1 in VM

>From YAST, HARDWARE, ZFCP, ADD
0.0.a210WWPN1LUN 502f
0.0.a310WWPN2LUN 502f
The WWPN's are different but the LUN's are the same. These are
defined correctly, because I've been able to use each path individual,
just not as multipath.

Then from EVMSGUI
- add DOS segment manager to a210
- select freespace object and create segment for a210
- create region MD Multipath Region Manager and select a210 and a310
- I skip the RAID0 part because I've only got 1 LUN
- create compatability volume
- Make filesystem (ReiserFS)
- Of course I've "saved" after each step as directed
- chkconfig evms.boot on

Actually, it will mount if I use EXT3 instead of ReiserFS, but I can
only get it to mount "read-only". With ReiserFS it won't mount at all.
In my searching I did notice suggestions of applying BD-Claim Patch,
which sounds like it might resolve my problem. In addition to that, is
this possibly fixed with SP1? I noticed a section in there stating "*
Added patches for OES to EVMS.", just wondering if that would help.


Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792






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


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

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

EVMS question for FCP device

[Wiggins, Mark]

I've been trying to get a multipath FCP device attach to my SLES9
instance on z/VM 5.1. I feel as though I've followed the directions
(Redbook 6344 - Chap. 9, Multipath FCP on SuSE SLES9) but I end up
getting either a "broken pipe" error when trying to mount it from
EVMSGUI and I get "wrong fs type, bad option, bad superblock on
/dev/evms/md/md0, or too many mounted file systems" when I try to mount
it on linux. Quickly, let me go through the steps and see if anyone can
see where I've went wrong.
 
ATT A210 to LINUX1 in VM (both are defined as TYPE=FCP).
ATT A310 to LINUX1 in VM
 
>From YAST, HARDWARE, ZFCP, ADD 
0.0.a210WWPN1LUN 502f
0.0.a310WWPN2LUN 502f
The WWPN's are different but the LUN's are the same. These are
defined correctly, because I've been able to use each path individual,
just not as multipath.
 
Then from EVMSGUI
- add DOS segment manager to a210
- select freespace object and create segment for a210
- create region MD Multipath Region Manager and select a210 and a310
- I skip the RAID0 part because I've only got 1 LUN
- create compatability volume
- Make filesystem (ReiserFS)
- Of course I've "saved" after each step as directed
- chkconfig evms.boot on
 
Actually, it will mount if I use EXT3 instead of ReiserFS, but I can
only get it to mount "read-only". With ReiserFS it won't mount at all.
In my searching I did notice suggestions of applying BD-Claim Patch,
which sounds like it might resolve my problem. In addition to that, is
this possibly fixed with SP1? I noticed a section in there stating "*
Added patches for OES to EVMS.", just wondering if that would help.
 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792
 
 
 
 
 

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

SLES install on z/VM 5.1

[Wiggins, Mark]

Well, after many calls to support and several notes to the list, I've
resolved my problem and thought that I might share my experience. I
don't know as to why this occurred but it did. When installing either
SLES8 or SLES9 on z/VM 5.1, I was unable to complete the install using
FTP. I was able to install SLES8 on z/VM 3.1 with FTP and then move it
over to 5.1 and today, I was finally successful in installing both SLES8
and SLES9 on 5.1 so long as I didn't use FTP to install it (I tried both
HTTP and NFS successfully). There seems to be a problem with FTP
transferring the final boot files to a 5.1 system. I've let my support
people know and they said that they would let IBM know. I just thought
that I would let the list (especially, I think Dave Jones who mentioned
failure when trying to use FTP) know that everything works out fine if
you don't use FTP.   
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: Suse 9.0 installation

[Wiggins, Mark]

No, I'm using an ftp server on a Debian instance that I've got. 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Lee Stewart
Sent: Tuesday, January 11, 2005 12:27 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 installation


Are you perhaps using a Windows FTP server?  I've seen that when I've
tried
to use a Windows server.  I don't know the details of what or why, but I
know you need a Linux or other *ix server...
Just my two cents worth...
Lee

At 09:47 AM 1/11/2005, you wrote:
>Ok, well I guess I've got a problem then. Once I've booted the system
>from the reader I go to VNC web and use YaST. I make it through all of
>the dasd allocations and formatting and YaST successfully installs
>sles9/CD1 and begins to install core9/CD1. It normally gets through
>about 20% of that CD when I get the following error
>
>Err: 11264: ERROR(Media:error)
>
>And it says something like "xx not found on media" where xx
>equals a different RPM almost every time. It might be "xfsprogs" one
>time and then "busybox" the next time etc. Sometimes it finds an RPM
and
>sometimes it doesn't but it always fails. I've done MD5SUM for each of
>the CD's and they all check out fine. The only difference that I see is
>that I've copied the isos to a Debian instance. I still mount them
using
>mkinstallroot script written by -Mike MacIsaac, IBM. I'll also say that
>I'm using the s390x RPM's for 64 bit z/VM. I'm at a loss... Tried
>everything that I can think of.
>
>-Original Message-
>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
>Marcy Cortes
>Sent: Monday, January 10, 2005 3:38 PM
>To: LINUX-390@VM.MARIST.EDU
>Subject: Re: Suse 9.0 installation
>
>
>Yes, we've successfully installed SLES9 on z/VM 5.1.  Mounted the .iso
>files on a SLES8 FTP server in the manner outlined in the release
notes.
>
>
>
>Marcy Cortes
>
>
>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:[EMAIL PROTECTED] On Behalf Of
>Wiggins, Mark
>Sent: Monday, January 10, 2005 12:27
>To: LINUX-390@VM.MARIST.EDU
>Subject: Re: [LINUX-390] Suse 9.0 installation
>
>So, have you successfully installed SLES9 on z/VM 5.1??? Actually, has
>anyone successfully installed SLES8 or SLES9 on z/VM 5.1? The reason
>that I ask is I can install SLES8 on our z/VM 3.1 system and then move
>it over to our 5.1 system and boot it up but I've yet to successfully
>install a new instance (SLES8 or SLES9) on our 5.1 system. It just
looks
>like Dave is having the same problem as I did and I used a script that
>is almost identical to the mkinstallroot script mentioned here and it
>didn't work either. I was really starting to think that it was a 5.1
>problem...
>
>Mark Wiggins
>University of Connecticut
>Operating Systems Programmer
>860-486-2792
>
>
>-Original Message-
>From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
>[EMAIL PROTECTED]
>Sent: Monday, January 10, 2005 1:05 PM
>To: LINUX-390@VM.MARIST.EDU
>Subject: Re: Suse 9.0 installation
>
>
>I know that this is late in the game, but the mkinstallroot script
>(supplied
>by Mark Post I believe) that was posted here worked great for me.  If
>you
>are going to install SLES9 it would be worth the effort to search the
>archives, and implement.
>
>-Original Message-
>From: Dave Jones [mailto:[EMAIL PROTECTED]
>Sent: Saturday, January 08, 2005 8:04 PM
>To: LINUX-390@VM.MARIST.EDU
>Subject: Re: Suse 9.0 installation
>
>
>I can add my experiences trying to install SLES9 on a z/VM 5.1
>system...and
>none of them are good.
>
>My installation server is an Intel box, running SuSE SLES9. The Intel
>box
>has a great deal of disk storage available, so I just put the 6 .iso
>files
>onto the server. I just do a simple mount -o loop -t iso9660 to make
the
>cd
>images available. So far, so good.
>
>After booting the initial SLES9 install VM kernel and ram disk, in a
>512M
>virtual machine and getting the networking setup and working (eth0 on a
>QDIO
>gLAN) without too much difficulty, I choose SSH and FTP for performing
>the
>basic installation, and I specify location of the install media as /CD1
>(where I

Re: Suse 9.0 installation

[Wiggins, Mark]

Ok, well I guess I've got a problem then. Once I've booted the system
from the reader I go to VNC web and use YaST. I make it through all of
the dasd allocations and formatting and YaST successfully installs
sles9/CD1 and begins to install core9/CD1. It normally gets through
about 20% of that CD when I get the following error 

Err: 11264: ERROR(Media:error)

And it says something like "xx not found on media" where xx
equals a different RPM almost every time. It might be "xfsprogs" one
time and then "busybox" the next time etc. Sometimes it finds an RPM and
sometimes it doesn't but it always fails. I've done MD5SUM for each of
the CD's and they all check out fine. The only difference that I see is
that I've copied the isos to a Debian instance. I still mount them using
mkinstallroot script written by -Mike MacIsaac, IBM. I'll also say that
I'm using the s390x RPM's for 64 bit z/VM. I'm at a loss... Tried
everything that I can think of. 

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Marcy Cortes
Sent: Monday, January 10, 2005 3:38 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 installation


Yes, we've successfully installed SLES9 on z/VM 5.1.  Mounted the .iso
files on a SLES8 FTP server in the manner outlined in the release notes.



Marcy Cortes


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:[EMAIL PROTECTED] On Behalf Of
Wiggins, Mark
Sent: Monday, January 10, 2005 12:27
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] Suse 9.0 installation

So, have you successfully installed SLES9 on z/VM 5.1??? Actually, has
anyone successfully installed SLES8 or SLES9 on z/VM 5.1? The reason
that I ask is I can install SLES8 on our z/VM 3.1 system and then move
it over to our 5.1 system and boot it up but I've yet to successfully
install a new instance (SLES8 or SLES9) on our 5.1 system. It just looks
like Dave is having the same problem as I did and I used a script that
is almost identical to the mkinstallroot script mentioned here and it
didn't work either. I was really starting to think that it was a 5.1
problem...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, January 10, 2005 1:05 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 installation


I know that this is late in the game, but the mkinstallroot script
(supplied
by Mark Post I believe) that was posted here worked great for me.  If
you
are going to install SLES9 it would be worth the effort to search the
archives, and implement.

-Original Message-
From: Dave Jones [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 08, 2005 8:04 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 installation


I can add my experiences trying to install SLES9 on a z/VM 5.1
system...and
none of them are good.

My installation server is an Intel box, running SuSE SLES9. The Intel
box
has a great deal of disk storage available, so I just put the 6 .iso
files
onto the server. I just do a simple mount -o loop -t iso9660 to make the
cd
images available. So far, so good.

After booting the initial SLES9 install VM kernel and ram disk, in a
512M
virtual machine and getting the networking setup and working (eth0 on a
QDIO
gLAN) without too much difficulty, I choose SSH and FTP for performing
the
basic installation, and I specify location of the install media as /CD1
(where I have mounted the CD1.iso file). I then log on, using SSH and
start
yast. After successfully creating the dasd partitions and making the
mount
points, yast reports the following error:

  Cannot read package data from installation media. Media error?

On the Intel SLES9 server, I can navigate and view the files on /CD1,
and
they all appear OK. Anybody got a clue as to what's wrong?

TIA.

DJ
Herczeg, Zoltan wrote:
> I can feel your pain. I ordered the SuSE sles9 evaluation and
> installed it via ftp from my windows desktop using war ftp server. It
> took me days just to get the ftp server set up properly for the
> initial install. Now after redoing things so many times and working
> with SuSE support on why my nic cards don't activate when linux boots
> a month has gone by and I have nothing to show for it. I am running
> MP3000, lpar with the nics on the MP3000.
>
> Zoltan
>
> -Original Message-
> From: Linux on 39

Re: Suse 9.0 installation

[Wiggins, Mark]

So, have you successfully installed SLES9 on z/VM 5.1??? Actually, has
anyone successfully installed SLES8 or SLES9 on z/VM 5.1? The reason
that I ask is I can install SLES8 on our z/VM 3.1 system and then move
it over to our 5.1 system and boot it up but I've yet to successfully
install a new instance (SLES8 or SLES9) on our 5.1 system. It just looks
like Dave is having the same problem as I did and I used a script that
is almost identical to the mkinstallroot script mentioned here and it
didn't work either. I was really starting to think that it was a 5.1
problem...

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, January 10, 2005 1:05 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 installation


I know that this is late in the game, but the mkinstallroot script
(supplied
by Mark Post I believe) that was posted here worked great for me.  If
you
are going to install SLES9 it would be worth the effort to search the
archives, and implement.

-Original Message-
From: Dave Jones [mailto:[EMAIL PROTECTED]
Sent: Saturday, January 08, 2005 8:04 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Suse 9.0 installation


I can add my experiences trying to install SLES9 on a z/VM 5.1
system...and
none of them are good.

My installation server is an Intel box, running SuSE SLES9. The Intel
box
has a great deal of disk storage available, so I just put the 6 .iso
files
onto the server. I just do a simple mount -o loop -t iso9660 to make the
cd
images available. So far, so good.

After booting the initial SLES9 install VM kernel and ram disk, in a
512M
virtual machine and getting the networking setup and working (eth0 on a
QDIO
gLAN) without too much difficulty, I choose SSH and FTP for performing
the
basic installation, and I specify location of the install media as /CD1
(where I have mounted the CD1.iso file). I then log on, using SSH and
start
yast. After successfully creating the dasd partitions and making the
mount
points, yast reports the following error:

  Cannot read package data from installation media. Media error?

On the Intel SLES9 server, I can navigate and view the files on /CD1,
and
they all appear OK. Anybody got a clue as to what's wrong?

TIA.

DJ
Herczeg, Zoltan wrote:
> I can feel your pain. I ordered the SuSE sles9 evaluation and
> installed it via ftp from my windows desktop using war ftp server. It
> took me days just to get the ftp server set up properly for the
> initial install. Now after redoing things so many times and working
> with SuSE support on why my nic cards don't activate when linux boots
> a month has gone by and I have nothing to show for it. I am running
> MP3000, lpar with the nics on the MP3000.
>
> Zoltan
>
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Tom Duerbusch
> Sent: Wednesday, January 05, 2005 12:26 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Suse 9.0 installation
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
>

--
Dave Jones
Houston, TX
281.578.7544
(speaking for myself only)

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

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

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

Re: FCP question

[Wiggins, Mark]

Ok, I guess I'll say never mind... I was just talking to one of the
Linux guys and told me that it looked to him as though LVM played an
important role in all of this. I went through the process of creating an
LVM vol and it looks as though that worked. Anyway, thank you (Cameron
Seader) for your help to date.

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Seader, Cameron
Sent: Wednesday, December 22, 2004 10:34 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


you are correct.
-Cameron

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Wednesday, December 22, 2004 08:32
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


Ok, so lets take this a step further. Is there a one-to-one correlation
between FCP channel on VM and WWPN on switch? In other words, this
works...

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300d08276 0x0:0x502f

This does not...

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa210 0x1:0x5005076300c28276 0x0:0x502f
0xa310 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300c28276 0x0:0x502f

Notice the difference in the WWPN's for each address.


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Seader, Cameron
Sent: Wednesday, December 22, 2004 9:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


This would be called multipathing.
-Cameron

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Wednesday, December 22, 2004 07:37
To: LINUX-390@VM.MARIST.EDU
Subject: FCP question


I've been reading through a lot of documentation and "Googled" the heck
out of this thing but have yet to run across what I want to do so I'm
questioning whether or not it's feasible. The question really revolves
around redundancy. In most references to connecting an FCP device to
Linux (we're running SuSE SLES8 on z/VM 5.1), they talk about connecting
1 FCP channel on VM, to 1 WWPN on a switch to multiple LUN's on the
shark. In other words, something like this
 
On VM
 
ATTACH a210-a211 TO LINUX1(Documentation suggested a QDIO
pair of addresses)
 
On Linux
 
rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f"
modprobe sd_mod

With the key word mentioned above, "REDUNDANCY", is it possible/feasible
to do the following?
 
On VM
 
ATTACH a210-a211 TO LINUX1
ATTACH a310-a311 TO LINUX1
 
On Linux
 
rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f;\
0xa210 0x2:0x5005076300c28276 0x0:0x502f;\
0xa310 0x3:0x5005076300d08276 0x0:0x502f;\
0xa310 0x4:0x5005076300c28276 0x0:0x502f"
modprobe sd_mod

Notice the 2 different WWPN's for the 2 different addresses (a210 and
a310). Am I completely missing something here???
 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

 

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



[INFO] -- Access Manager:
This transmission may contain information that is privileged,
confidential and/or exempt from disclosure under applicable law.  If you
are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED. If you
received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic
or hard copy format.  Thank you.   A2

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

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



[INFO] -- Access Manager:
This transmission may contain information that is privileged,
confidential and/or exempt from disclosure under applicable law.  If you
are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED. If yo

Re: FCP question

[Wiggins, Mark]

Here's what I think is the pertinent information

Here's my current zfcp.conf file

0xa210 0x01:0x5005076300d08276 0x00:0x502f
0xa310 0x01:0x5005076300c28276 0x00:0x502f

And here's the dmesg,

debug: qdio_trace: new level 2
zfcp: zfcp_module_init: driver version 0x3003c
debug: zfcp_lock: new level 4
debug: zfcp_req0xa210: new level 6
debug: zfcp_req0xa210: new level 3
debug: zfcp_erp0xa210: new level 6
debug: zfcp_req0xa310: new level 6
debug: zfcp_req0xa310: new level 3
debug: zfcp_erp0xa310: new level 6
scsi: limiting sg entries to 170
scsi0 : zfcp
scsi: limiting sg entries to 170
scsi1 : zfcp
  Vendor: IBM   Model: 2105F20   Rev: .129
  Type:   Direct-Access  ANSI SCSI revision: 03
  Vendor: IBM   Model: 2105F20   Rev: .129
  Type:   Direct-Access  ANSI SCSI revision: 03
Journalled Block Device driver loaded
dasd: initializing...
debug: dasd: new level 3
dasd: Registered successfully to major no 94
dasd: initialization finished
sd: allocated major 8
sd: find_free_slot ...<7>sd: ... found 08:00
Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
sd: find_free_slot ...<7>sd: ... found 08:10
Attached scsi disk sdb at scsi1, channel 0, id 1, lun 0
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for SCSI
Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status code 0x2
  0202  0020  
7600 0018  2900 0400    

SCSI device sda: 7812544 512-byte hdwr sectors (4000 MB)
 sda: sda1
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for SCSI
Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status code 0x2
  0202  0020  
7600 0018  2900 0400    

SCSI device sdb: 7812544 512-byte hdwr sectors (4000 MB)
 sdb: sdb1
zfcp: config: zfcp_unit_enqueue: Warning: A Unit with SCSI LUN 0x0
already exists. Skipping record.
zfcp: SCSI: zfcp_config_parse_record_add: warning: unable to add record:
0xa210 1:0x5005076300d08276 0:0x502f
zfcp: SCSI: zfcp_add_map_proc_write: Warning: One or several mapping
entries were not added to the module configuration.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.

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

Re: FCP question

[Wiggins, Mark]

Still getting same error. Changed to 

0xa210 0x01:0x5005076300d08276 0x00:0x502f
  0xa310 0x01:0x5005076300c28276 0x00:0x502f

And reran "mk_initrd" and "zipl" and "fdisk /dev/sda". The messages were
the same

sd: allocated major 8
sd: find_free_slot ...<7>sd: ... found 08:00
Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
sd: find_free_slot ...<7>sd: ... found 08:10
Attached scsi disk sdb at scsi1, channel 0, id 1, lun 0
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for
SCSI Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status
code 0x2
  0202  0020  
7600 0018  2900 0400  
 

SCSI device sda: 7812544 512-byte hdwr sectors (4000 MB)
 sda: sda1
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for
SCSI Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status
code 0x2
  0202  0020  
7600 0018  2900 0400  
 

SCSI device sdb: 7812544 512-byte hdwr sectors (4000 MB)
 sdb: sdb1
zfcp: config: zfcp_unit_enqueue: Warning: A Unit with SCSI LUN
0x0 already exists. Skipping record.
zfcp: SCSI: zfcp_config_parse_record_add: warning: unable to add
record: 0xa210 1:0x5005076300d08276 0:0x502f
zfcp: SCSI: zfcp_add_map_proc_write: Warning: One or several
mapping entries were not added to the moduleconfiguration.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Seader, Cameron
Sent: Thursday, December 23, 2004 11:07 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


YOu went wrong on the zfcp.conf configuration. you will notice that
where you put in the 0x1: you need to have a 0x01 and where you put in
the LUN # of 0x0: you need to have 0x00:, it is very picky. If you have
one thing wrong it won't work.
-Cameron

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Thursday, December 23, 2004 09:04
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


Last question I hope. I've since created an /etc/zfcp.conf file with the
following.

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300c28276 0x0:0x502f

I ran "mk_initrd" and zipl. Upon reboot a I noticed the following in the
logs,

sd: allocated major 8
sd: find_free_slot ...<7>sd: ... found 08:00
Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
sd: find_free_slot ...<7>sd: ... found 08:10
Attached scsi disk sdb at scsi1, channel 0, id 1, lun 0
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for
SCSI Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status
code 0x2
  0202  0020 
7600 0018  2900 0400  


SCSI device sda: 7812544 512-byte hdwr sectors (4000 MB)
sda: sda1
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for
SCSI Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status
code 0x2
  0202  0020 
7600 0018  2900 0400  


SCSI device sdb: 7812544 512-byte hdwr sectors (4000 MB)
 sdb: sdb1
zfcp: config: zfcp_unit_enqueue: Warning: A Unit with SCSI LUN
0x0 already exists. Skipping record.
zfcp: SCSI: zfcp_config_parse_record_add: warning: unable to add
record: 0xa210 1:0x5005076300d082760:0x502f
zfcp: SCSI: zfcp_add_map_proc_write: Warning: One or several
mapping entries were not added to the module   configuration.


It seems as though I am not "multipathing". Where did I go wrong???
SLES8/zVM 5.1.

Mark Wiggins


-

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

Re: FCP question

[Wiggins, Mark]

Last question I hope. I've since created an /etc/zfcp.conf file with the
following.

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300c28276 0x0:0x502f

I ran "mk_initrd" and zipl. Upon reboot a I noticed the following in the
logs,

sd: allocated major 8
sd: find_free_slot ...<7>sd: ... found 08:00
Attached scsi disk sda at scsi0, channel 0, id 1, lun 0
sd: find_free_slot ...<7>sd: ... found 08:10
Attached scsi disk sdb at scsi1, channel 0, id 1, lun 0
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for
SCSI Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status
code 0x2
  0202  0020 
7600 0018  2900 0400  


SCSI device sda: 7812544 512-byte hdwr sectors (4000 MB)
sda: sda1
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: status for
SCSI Command:
 
zfcp: FSF: zfcp_fsf_send_fcp_command_task_handler: SCSI status
code 0x2
  0202  0020 
7600 0018  2900 0400  


SCSI device sdb: 7812544 512-byte hdwr sectors (4000 MB)
 sdb: sdb1
zfcp: config: zfcp_unit_enqueue: Warning: A Unit with SCSI LUN
0x0 already exists. Skipping record.
zfcp: SCSI: zfcp_config_parse_record_add: warning: unable to add
record: 0xa210 1:0x5005076300d082760:0x502f
zfcp: SCSI: zfcp_add_map_proc_write: Warning: One or several
mapping entries were not added to the module   configuration.


It seems as though I am not "multipathing". Where did I go wrong???
SLES8/zVM 5.1.

Mark Wiggins


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Seader, Cameron
Sent: Wednesday, December 22, 2004 10:34 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


you are correct.
-Cameron

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Wednesday, December 22, 2004 08:32
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


Ok, so lets take this a step further. Is there a one-to-one correlation
between FCP channel on VM and WWPN on switch? In other words, this
works...

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300d08276 0x0:0x502f

This does not...

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa210 0x1:0x5005076300c28276 0x0:0x502f
0xa310 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300c28276 0x0:0x502f

Notice the difference in the WWPN's for each address.


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Seader, Cameron
Sent: Wednesday, December 22, 2004 9:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


This would be called multipathing.
-Cameron

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Wednesday, December 22, 2004 07:37
To: LINUX-390@VM.MARIST.EDU
Subject: FCP question


I've been reading through a lot of documentation and "Googled" the heck
out of this thing but have yet to run across what I want to do so I'm
questioning whether or not it's feasible. The question really revolves
around redundancy. In most references to connecting an FCP device to
Linux (we're running SuSE SLES8 on z/VM 5.1), they talk about connecting
1 FCP channel on VM, to 1 WWPN on a switch to multiple LUN's on the
shark. In other words, something like this

On VM

ATTACH a210-a211 TO LINUX1(Documentation suggested a QDIO
pair of addresses)

On Linux

rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f"
modprobe sd_mod

With the key word mentioned above, "REDUNDANCY", is it possible/feasible
to do the following?

On VM

ATTACH a210-a211 TO LINUX1
ATTACH a310-a311 TO LINUX1

On Linux

rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f;\
0xa210 0x2:0x5005076300c28276 0x0:0x502f;\
0xa310 0x3:0x5005076300d08276 0x0:0x502f;\
0xa310 0x4:0x5005076300c28276 0x0:0x502f"
modprobe sd_mod

Notice the 2 different WWPN's for the 2 different addresses (a210 and
a310). Am I completely missing something here???


Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792



--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http:

Re: FCP question

[Wiggins, Mark]

Ok, so lets take this a step further. Is there a one-to-one correlation
between FCP channel on VM and WWPN on switch? In other words, this
works...

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300d08276 0x0:0x502f

This does not...

0xa210 0x1:0x5005076300d08276 0x0:0x502f
0xa210 0x1:0x5005076300c28276 0x0:0x502f
0xa310 0x1:0x5005076300d08276 0x0:0x502f
0xa310 0x1:0x5005076300c28276 0x0:0x502f

Notice the difference in the WWPN's for each address.


-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Seader, Cameron
Sent: Wednesday, December 22, 2004 9:40 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: FCP question


This would be called multipathing.
-Cameron

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Wednesday, December 22, 2004 07:37
To: LINUX-390@VM.MARIST.EDU
Subject: FCP question


I've been reading through a lot of documentation and "Googled" the heck
out of this thing but have yet to run across what I want to do so I'm
questioning whether or not it's feasible. The question really revolves
around redundancy. In most references to connecting an FCP device to
Linux (we're running SuSE SLES8 on z/VM 5.1), they talk about connecting
1 FCP channel on VM, to 1 WWPN on a switch to multiple LUN's on the
shark. In other words, something like this
 
On VM
 
ATTACH a210-a211 TO LINUX1(Documentation suggested a QDIO
pair of addresses)
 
On Linux
 
rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f"
modprobe sd_mod

With the key word mentioned above, "REDUNDANCY", is it possible/feasible
to do the following?
 
On VM
 
ATTACH a210-a211 TO LINUX1
ATTACH a310-a311 TO LINUX1
 
On Linux
 
rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f;\
0xa210 0x2:0x5005076300c28276 0x0:0x502f;\
0xa310 0x3:0x5005076300d08276 0x0:0x502f;\
0xa310 0x4:0x5005076300c28276 0x0:0x502f"
modprobe sd_mod

Notice the 2 different WWPN's for the 2 different addresses (a210 and
a310). Am I completely missing something here???
 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

 

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



[INFO] -- Access Manager:
This transmission may contain information that is privileged,
confidential and/or exempt from disclosure under applicable law.  If you
are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution, or use of the information contained
herein (including any reliance thereon) is STRICTLY PROHIBITED. If you
received this transmission in error, please immediately contact the
sender and destroy the material in its entirety, whether in electronic
or hard copy format.  Thank you.   A2

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

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

FCP question

[Wiggins, Mark]

I've been reading through a lot of documentation and "Googled" the heck
out of this thing but have yet to run across what I want to do so I'm
questioning whether or not it's feasible. The question really revolves
around redundancy. In most references to connecting an FCP device to
Linux (we're running SuSE SLES8 on z/VM 5.1), they talk about connecting
1 FCP channel on VM, to 1 WWPN on a switch to multiple LUN's on the
shark. In other words, something like this
 
On VM
 
ATTACH a210-a211 TO LINUX1(Documentation suggested a QDIO
pair of addresses)
 
On Linux
 
rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f"
modprobe sd_mod

With the key word mentioned above, "REDUNDANCY", is it possible/feasible
to do the following?
 
On VM
 
ATTACH a210-a211 TO LINUX1
ATTACH a310-a311 TO LINUX1
 
On Linux
 
rmmod zfcp
modprobe qdio
modprobe scsi_mod
insmod zfcp loglevel=0 map="\
0xa210 0x1:0x5005076300d08276 0x0:0x502f;\
0xa210 0x2:0x5005076300c28276 0x0:0x502f;\
0xa310 0x3:0x5005076300d08276 0x0:0x502f;\
0xa310 0x4:0x5005076300c28276 0x0:0x502f"
modprobe sd_mod

Notice the 2 different WWPN's for the 2 different addresses (a210 and
a310). Am I completely missing something here???
 
 
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

 

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

Re: Using VSWITCH and OSA

[Wiggins, Mark]

<[EMAIL PROTECTED]> wrote:
>> -- note --
>> This means that your backup ports can be in use on other guests, or
on other VSWITCHes.
>> -- note --

My question to this is, in the following scenario (which are some
"query" commands on our v5.1 system), how can OSA 0A00 be used elsewhere
if it needs to be attached to the VSWITCH as a BACKUP?

VSWITCH SYSTEM VSW1 Type: VSWITCH Connected: 4Maxconn: INFINITE
  PERSISTENT  RESTRICTEDNONROUTER Accounting: OFF
  VLAN Unaware
  State: Ready
  IPTimeout: 5 QueueStorage: 8
  Portname: UNASSIGNED RDEV: 0800 Controller: VSWCTRL1 VDEV:  0800
  Portname: UNASSIGNED RDEV: 0A00 Controller: VSWCTRL1 VDEV:  0A00
BACKUP

q 800-802
OSA  0800 ATTACHED TO VSWCTRL1 0800
OSA  0801 ATTACHED TO VSWCTRL1 0801
OSA  0802 ATTACHED TO VSWCTRL1 0802

q a00-a02
OSA  0A00 ATTACHED TO VSWCTRL1 0A00
OSA  0A01 ATTACHED TO VSWCTRL1 0A01
OSA  0A02 ATTACHED TO VSWCTRL1 0A02

In other words, if 0800 were to fail, the VSWITCH would switch to 0A00
automatically (we've tested this successfully). If 0A00 were not
attached to the VSWITCH, would the VSWITCH controller be able to detach
it from whatever it was attached too, attach it to the VSWITCH and then
switch from the failing OSA 0800 to 0A00? If not, how can something else
use this OSA if it is already attached to the VSWITCH as a backup?

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

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

Re: SuSE SLES8 and z/VM 5.1 problem

[Wiggins, Mark]

I am able to boot from the reader and go through most of the install
process, sorry for any confusion there. My problem is with writing out
to the defined /boot disk. I've run the machine at 128M, 256M and 512M,
all to no avail. I use FTP and VNC/web to install.

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Post
Sent: Thursday, December 09, 2004 6:13 PM
To: [EMAIL PROTECTED]
Subject: Re: SuSE SLES8 and z/VM 5.1 problem


You say you're not able to boot SLES8 from the virtual reader, but then
you
say you get all the way through the install, but the writing of the IPL
text
fails.  That's a little confusing.

I've seen various programs through out "bus errors" in the past when
there
wasn't enough virtual storage on the system.  How much virtual storage
does
this guest have defined, and which installation method (VNC, SSH,
whatever)
are you using?


Mark Post

-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Wiggins, Mark
Sent: Wednesday, December 08, 2004 9:56 AM
To: [EMAIL PROTECTED]
Subject: SuSE SLES8 and z/VM 5.1 problem


OK, brief history and then my question. We just purchased a z890, moved
our
current z/VM 3.1.0 system to the GP and installed z/VM 5.1 on the IFL. I
moved over 2 different flavors of Linux (Debian and Redhat) to the IFL
and
they work great. With the purchase of our new box we received SuSE
licensing.

Here's my question:
I'm able to bring SuSE SLES8 up on z/VM 3.1 and it works fine. I'm able
to
move the instance to the z/VM 5.1 system and it works fine there. What
I'm
not able to do is boot SLES8 from the reader on z/VM 5.1. I go through
most
of the install process in YAST right up to the point of "Prepare system
for
initial boot". It won't write out the IPL records to my boot disk. I
receive
the below error on the VM console and I end up with an non-IPL'able disk
on
VM. When I look at it with DDR, I don't see the first 2 "IPL" records
that I
see on other Linux boot disks.

User process fault: interruption code 0x60038 ,

CPU: 0 Tainted: P ,

Process y2base (pid: 666, task: 0789, ksp: 07893b88)
,

User PSW : 0705e0018000 01077f5e ,

User GPRS: 0001 0101f6d0 7865637574652063
01ffce18 ,

010e0de8 012d6902 01ffd098
01ffd1e8 ,

01ffcee8 80009250 
80043cc0 ,

01016e88 010ccb20 01077f3e
01ffce18 ,

User ACRS: 0100 002e5720   ,

    ,

    ,

    ,

User Code: e3 40 20 00 00 04 a7 3b 00 d0 e3 10 40 20 00 04 0d e1 c0 30 ,

/usr/lib/YaST2/bin/YaST2: line 296: 666 Bus error y2base "$modulename"

$moduleargs qt -style=platinum -fn $Y2_XFONT ,

-geometry 800x600+1+1 -no-wm $qt_bg"

umount: /var/adm/mount: not mounted"

Dec 1 21:32:15 suse sshd]182(: Received signal 15; terminating.""

"]0;37;40m

*** An error occurred during the installation!



Has anyone seen this before? I've tried writing to 3380, 3390 and 9336
disks. I've tried formatting them in VM, in Linux, on the 3.1 system,
all to
no avail. Any help would be greatly appreciated. One last note, the
"interruption code" changes depending (I think) on which type of device
I'm
trying to write too.

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792






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

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

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

SuSE SLES8 and z/VM 5.1 problem

[Wiggins, Mark]

OK, brief history and then my question. We just purchased a z890, moved our 
current z/VM 3.1.0 system to the GP and installed z/VM 5.1 on the IFL. I moved 
over 2 different flavors of Linux (Debian and Redhat) to the IFL and they work 
great. With the purchase of our new box we received SuSE licensing. 
 
Here's my question:
I'm able to bring SuSE SLES8 up on z/VM 3.1 and it works fine. I'm able to move 
the instance to the z/VM 5.1 system and it works fine there. What I'm not able 
to do is boot SLES8 from the reader on z/VM 5.1. I go through most of the 
install process in YAST right up to the point of "Prepare system for initial 
boot". It won't write out the IPL records to my boot disk. I receive the below 
error on the VM console and I end up with an non-IPL'able disk on VM. When I 
look at it with DDR, I don't see the first 2 "IPL" records that I see on other 
Linux boot disks.
 
User process fault: interruption code 0x60038 ,

CPU: 0 Tainted: P ,

Process y2base (pid: 666, task: 0789, ksp: 07893b88) ,

User PSW : 0705e0018000 01077f5e ,

User GPRS: 0001 0101f6d0 7865637574652063 01ffce18 ,

010e0de8 012d6902 01ffd098 
01ffd1e8 ,

01ffcee8 80009250  
80043cc0 ,

01016e88 010ccb20 01077f3e 
01ffce18 ,

User ACRS: 0100 002e5720   ,

    ,

    ,

    ,

User Code: e3 40 20 00 00 04 a7 3b 00 d0 e3 10 40 20 00 04 0d e1 c0 30 ,

/usr/lib/YaST2/bin/YaST2: line 296: 666 Bus error y2base "$modulename" 

$moduleargs qt -style=platinum -fn $Y2_XFONT ,

-geometry 800x600+1+1 -no-wm $qt_bg" 

umount: /var/adm/mount: not mounted" 

Dec 1 21:32:15 suse sshdÝ182¨: Received signal 15; terminating.""

"Ý0;37;40m 

*** An error occurred during the installation! 

 

Has anyone seen this before? I've tried writing to 3380, 3390 and 9336 disks. 
I've tried formatting them in VM, in Linux, on the 3.1 system, all to no avail. 
Any help would be greatly appreciated. One last note, the "interruption code" 
changes depending (I think) on which type of device I'm trying to write too.

Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792

 

 


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