Problems with upgrade to z/vm

[Keith Gooding]

I attempted to post this to the ibmvm list but have had some problems 
subscribing to that list so I am hoping that someone here can help.
 I have used the “upgrade” path to upgrade from 6.3 to 6.4 and have started 
stage 2 using “instupgr stage2 (commit”.
There were instructions to shut down non-essential VMs and unfirtunately I shut 
down the file pool server VMSYSP. instupgr now fails because it needs that 
fileserv.
After some messing about I re-ipled z/vm and logged on to MIGMAINT again but it 
cannot start CMS because a saved segment is missing.
The backout is to restore from the backup taken before stage2 (it is a 
flashcopy  taken with DFDSS using CPVOLUME option which I understood to have 
been tested as part of DR but I found out that a different VM is used for DR.
I have DDR backups from before stage1 which are over a week old so I would 
prefer to fix the problem if possible.
Keith Gooding


--
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: Problems with SCSI-over-FCP after machine upgrade

[Keith Gooding]

We have fixed this problem but made more than one change so we do not know the 
cause - it would be nice to know who to blame !

Thanks for all the advice. I followed up Scott's suggestion of creating an exec 
to delete the EDEV' s paths and to do SET EDEV  CLEAR so that I could vary 
the CHPIDs offline. (I found that to redefine the EDEVs I had to use 'SET EDEV 
' providing the   Type, Attributes, FCP_dev, wwpn and LUN without the text 
'ADD PATH' for the first path and with the text 'add path' for the other paths).
There is no zoning or LUN masking involved and the NPIV wwpns had not changed 
(the physical NPIVs had changed - they contains the new PCHIPID ids). We had 
already tried switching everything in the paths off/on.

 The changes which we made to resolve the problem were: - switch firmware was 
upgraded from 6.1.1a to 6.3.0d . Neither had been qualified for zBC12. (We 
later upgraded to 7.0.0d)- removed the link between the two SAN switches. The 
SAN Volume Controller documentation says that the fibre networks should be 
independent. When I disconnected the link I found that one of the SFPs came out 
too - it had not 'clicked' into place.- cleaned the z12 end of the fibre links.
All of the zlinuxes then came up and stayed up, except for some which relied on 
the ISL being in place. ie the LOADDEV parameters (for loading from  chpid 18) 
specified an SVC wwpn which was now accessible only from the other CHPID, which 
was easily fixed.
Maybe the problem was due to FCP channel microcode in z12 (or z114/196). Or 
maybe there were some fabric errors which were exacerbated by the faster z12 
IFLs.
Keith


  


 On Monday, 8 June 2015, 15:39, Raymond Higgs  wrote:
   

 Hi Keith,

Please check zoning and lun masking. I think the SVC management interface calls 
them hosts.  If youdidn't do an MES upgrade, then the WWPNs of your channels 
changed.

Regards,

Ray Higgs
System z FCP Firmware Development
Bld. 706, B42
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com



From:       Keith Gooding 
To:       LINUX-390@VM.MARIST.EDU
Date:       06/04/2015 04:23 PM
Subject:       Problems withSCSI-over-FCP after machine upgrade
Sent by:       Linux on 390Port 



This may not be the proper forum but maybe someonecan help.
 We have a small number of linux systems (<32) under z/VM 6.3 whichuse SCSI 
connections to LUNs on a SAN Volume Controller via a couple ofIBM SAN24B 
switches (the equivalent of Brocade 300). There are also somesystems which use 
EDEVs on the same SVC. This had worked on z10 BC forabout 5 years without 
problems.
 Last week the z10 was upgraded to a zBC12, retaining the same FICON 
cards(4Gbs), but not necessarily associated with the same CHPIDs. Since thena 
number of the LUN connections have been 'lost', cauing linux systemsto fail. 
SCSIDISC displays eg "HCPRXS975I Virtual FCP device 1A05ignored because the 
adapter was not able to connect to the fibre channelnetwork". It is then not 
possible to rebot the linux system.

Restarting 'everything' - ie SVC nodes, SAN switches, CHIPD vary off/on-  
cleared the problem for a while.
Any ideas where to start looking ?. I have discovered that we have >32 FCP 
subchannels defined on the CHPID (but highest used unit addressis 1f, and there 
are only about a dozen in use). Also the switch has notbeen 'qualified' for use 
on z12 (but it appears that it was not qualifiedfor z10 either).
Any advice greatly appreciated !
 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 orvisit
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/

Problems with SCSI-over-FCP after machine upgrade

[Keith Gooding]

This may not be the proper forum but maybe someone can help.
 We have a small number of linux systems (<32) under z/VM 6.3 which use SCSI 
connections to LUNs on a SAN Volume Controller via a couple of IBM SAN24B 
switches (the equivalent of Brocade 300). There are also some systems which use 
EDEVs on the same SVC. This had worked on z10 BC for about 5 years without 
problems.
 Last week the z10 was upgraded to a zBC12, retaining the same FICON cards 
(4Gbs), but not necessarily associated with the same CHPIDs. Since then a 
number of the LUN connections have been 'lost', cauing linux systems to fail. 
SCSIDISC displays eg "HCPRXS975I Virtual FCP device 1A05 ignored because the 
adapter was not able to connect to the fibre channel network". It is then not 
possible to rebot the linux system.

Restarting 'everything' - ie SVC nodes, SAN switches, CHIPD vary off/on -  
cleared the problem for a while.
Any ideas where to start looking ?. I have discovered that we have > 32 FCP 
subchannels defined on the CHPID (but highest used unit address is 1f, and 
there are only about a dozen in use). Also the switch has not been 'qualified' 
for use on z12 (but it appears that it was not qualified for z10 either).
Any advice greatly appreciated !
 

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

Creating a linux 'live DVD' for system z

[Keith Gooding]

Hi all,
I seem to recall that someone asked some time ago whether it was possible to 
create DVD which could be used from the HMC to IPL a z/VM system into an LPAR 
(in the same way that the z/VM installer works). I think the answer was that it 
was not possible (other than for IBM) because it required some internal z/VM 
knowledge and/or code changes.
Are there any tools to create a similar DVD to boot a linux system ?. I am 
thinking in terms of a linux 'appliance' which could be booted into a tape-less 
'bare metal' z system and be used to restore 3390 disk images from an NFS 
server. (I was reminded of this question when I recently restored a zPDT 
system, including z/VM and z/OS ADCDs, from a 1TB SSD the size of an iphone and 
compared this with the prospect of a new storage rack + FICON-attached tape 
controller and tape drive to do the same on a 'real' mainframe')
Keith Gooding  

--
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: KVM in Linux for system z capabilities

[Keith Gooding]

Thanks Mark. That is more or less what I thought. BTW I only just noticed that 
the IBM-speak in the SOD in the z13 announcement said 'IBM intends to 
**support** a Kernel-based Virtual Machine (KVM) offering for z Systems' (my 
highlighting). ie 'support' not 'deliver'. 
Keith


 On Monday, 16 February 2015, 18:04, Mark Post  wrote:
   

 >>> On 2/16/2015 at 12:40 PM, Keith Gooding  wrote: 
> Can anyone help resolve this difference of opinion with colleagues ?
> 
>  I have always assumed from what I have read that the QEMU and KVM, offered 
> as a 'technology preview' in for instance SUSE 11 SP3 or SUSE 12 will only 
> run zLinux guests and its purpose is to provide an alternative to z/VM (some 
> day). Colleages say that it will emulate Intel so that you will be able to 
> run x386_64 Linux guests. Who is correct (maybe both ?).

While qemu is _capable_ of emulating other architectures, that's not how we 
build it or ship it.  The intent is not to provide an alternative to z/VM, 
however.  The intent is to help new-to-the-mainframe customers get started with 
virtualization on the platform using a tool they probably already know pretty 
well.  Lowering the barriers to entry in order to help convince them that 
mainframes really are a good idea.  I envision people using KVM on System z 
eventually deciding they want to upgrade to z/VM for the better capabilities 
and manageability it provides.

> Also does anyone have any guesses about IBMs Statement of Direction about 
> KVM that was in the z13 announcement. Will it be z13 only ?.  An IBM product 
> like z/VM ?. Will it emulate Intel ?

My pure, unadulterated, WAG is that it will be z13 (or later) only, a priced 
IBM product, and that it will not emulate Intel.  That just feels how IBM would 
approach things given their history.


Mark Post



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

KVM in Linux for system z capabilities

[Keith Gooding]

Can anyone help resolve this difference of opinion with colleagues ?

 I have always assumed from what I have read that the QEMU and KVM, offered as 
a 'technology preview' in for instance SUSE 11 SP3 or SUSE 12 will only run 
zLinux guests and its purpose is to provide an alternative to z/VM (some day). 
Colleages say that it will emulate Intel so that you will be able to run 
x386_64 Linux guests. Who is correct (maybe both ?).
Also does anyone have any guesses about IBMs Statement of Direction about KVM 
that was in the z13 announcement. Will it be z13 only ?.  An IBM product like 
z/VM ?. Will it emulate Intel ?
TIAKeith Gooding

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

Re: Where to put Z/VM tools and utilities

[Keith Gooding]

Thanks everyone.
I will set up a user to own the tools as suggested and use VMLINK. I am the 
only z/VM user except for a couple of people in the company who used VM many 
years ago and have an id for nostalgic reasons (and who could be useful if I am 
not around) so I will just update the PROFILE EXECs rather than tinker with 
SYSPROF EXEC. SFS looks attractive but I have no knowledge of it so I will 
stick with  minidisks for now. Ditto for nicknames.
Keith
 

 On Monday, 12 January 2015, 15:58, Rick Troth  
wrote:
   

 On 01/12/2015 09:20 AM, Robert J Brenneman wrote:
> Mother's rule of z/VM Service number 1: Never change anything IBM sends you
> Mother's rule of z/VM Service number 2: Never mix your stuff with IBM's stuff.

Amen! But see below for an exception.


> In my shop we create a user in the directory named after our department and
> set the PW to NOLOG. We give that new user a 191 disk ...

This, plus what Sam said about using VMLINK.
VMLINK is your friend. And when using VMLINK, you can selectively put
some things on minidisk and other things into SFS (like Alan suggested)
as needed, without having to be wholly in one mode or the other.

As a help when servicing, I like to have an ID for each product (or tool
or package). Lock it down, but allow logon-by for maint.

For minidisk, there must be an ID (see prior paragraph) to own the
storage. Rather than 191, I recommend v/r/m for three or four levels.
This is fun, though less flexible than SFS. For example, my copy of
Arty's IUCVTRAP is at "FIX19". I could have a user "IUCVTRAP" with disk
019 or F19. People would link that disk. (Using 'VMLINK' of course!) For
each dotted level, you get 0 to 15 (last six in hex).

SFS is simpler. For z/OS people on your team (or if it's just you), SFS
might feel more natural, and that's a plus.

Exception to Mother's rule #1:
At a previous site, we had a small (read that as "easy to maintain") mod
to SYSPROF EXEC to conditionally drive LCLPROF EXEC. The latter then did
as little as possible, but arranged for our local stuff to be quickly
on-hand without keeping everyone's private PROFILE EXEC in synch. Sounds
like you have a small enough team (just you? or others too?) that you
might be able to get by with just doing it in PROFILE EXEC.

Repeating what Sam said: more art than science. You'll get a handle on it.



--

Rick Troth
Senior Software Developer

Velocity Software Inc.
Mountain View, CA 94041
Main: (877) 964-8867
Direct: (614) 594-9768
ri...@velocitysoftware.com 

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



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

Re: Adding a zfcp LUN to root file system logical volume

[Keith Gooding]

Hi Steffen,
 
fstab shows that /boot is on a physical partition (/dev/sda1 has label /boot):
 
/dev/VolGroup00/LogVol00 /   ext3    defaults    1 1
LABEL=/boot /boot   ext3    defaults    1 2
 
I mis-read your reply about the restrictions when using  logical volumes for 
the boot device - I assumed it meant that the root file system had to be on the 
first PV of the LV. So running mkinitrd and zipl from another system should be 
OK, as you suggest. However I decided to go down another path - move some data 
off the LV, then use pvmove and pvremove to remove the second PV so that I 
could boot the system without it. pvmove is still saying that the first PV is 
full, but that is another problem. Maybe the unix guy can fix this when he 
returns next week. Meanwhile I am going to create a new system (these are test 
systems of course, but we need to have various levels of both RH and SUSE to 
test our software).
 
Keith
On Wednesday, 21 May 2014, 19:13, Steffen Maier  
wrote:
  


Hi Keith,

On 05/21/2014 02:05 PM, Keith Gooding wrote:
> Thank you to everyone who responded. No, we did not run mkinitrd and
> zipl after adding the second LUN to the root file system. When we
> have added LUNs in the past it has been unnecessary because they were
> not needed during boot - I started to understand this just after I
> posted my question. (My linux knowledge is not very good - I
> understand z/OS and system z in general and do the 'z' parts of
> installing zLinux. A colleage who knows little about system z then
> takes over. There seems to be a big gap in our combined knowledge,
> but I have now learned something about the boot process - at least I
> now understand that 'rd' in initrd stands for 'ram disk').
>
> Unfortunately the volume groups in all of our systems are called
> 'VolGroup00' so I was not able to vgimport the group into a RH 5
> system so I accessed it from a SUSE system which does not LVs so that
> I could rename it. I was just about to import it into a RH 5 system
> so that I could run initmkd and zipl under chroot when I read
> Steffen's refernce to the restrictions with LVs in RH 5. The reason
> for adding the second PV was that the first was full, so it is
> possible that any new boot image will be created on the new physical
> volume. I think this is getting too difficult.

I'm missing some setup information to make a valid statement here.
What does your /etc/fstab look like?

Since RHEL5 most likely does not support /boot (whether separately or
included in the root-fs) on multipathing or LVM (or any non-physical
block device(s)), don't you already have /boot separately on some
single-path /dev/sdXYNM ?
If so, adding PVs to your root-fs should not be a problem at all.

> Re-installing with a
> later release is probably more productive.
>
> Incidentally I spent some time yesterday in attempting to enter
> kernel parameters using the SCPDATA option of LOADDEV in zVM V5.
> (a). I assumed that the parameters have to be in ascii so I entered
> them in hexadecimal. (b). Is this method actually available for RH 5?

Linux kernel support for SCPDATA only appeared via upstream with kernel
2.6.32, so it's not available for RHEL5, but e.g. with SLES11 SP1 /
RHEL6 or later.

http://www.ibm.com/developerworks/linux/linux390/kernel-2.6.32.html

Summary:
kernel: Extra kernel parameter for SCSI IPL
Description:
When booting from a SCSI boot device, you can now specify kernel
parameters in addition to the existing kernel parameters that are used
by your boot configuration. To specify kernel parameters, use the
SCPDATA option of the CP LOADDEV command or enter kernel parameters in
the 'Operating system specific load parameters' panel when IPLing a
system from the HMC.

Please refer to the 'Device Drivers, Features, and Commands' manual
(Documentation), Chapter 'Booting Linux', section 'Providing additional
kernel parameters when booting'.


It seems parameters have to be ASCII characters (not hex), otherwise
SCPDATA is ignored.
The used setting can be read from /sys/firmware/ipl/scp_data in the
IPLed kernel (where you could also reconfigure for an upcoming reboot
under /sys/firmware/reipl/fcp/scp_data).
It works for both a regular IPL as well as for an IPL of the SCSI
standalone dumper (zfcpdump).

I'd recommend to pick the device drivers book matching your distribution
from
http://www.ibm.com/developerworks/linux/linux390/distribution_hints.html
to get matching customized documentation.
You might look into more recent minor release books in case there were
documentation fixes.

> - I found the reference in the RH 6 documentation. (c). If  SCPDATA
> can be used with RH 5, what is the syntax of the zfcp options. I
> asssumed that it was "zfcp.device=0.0.,,&quo

Re: Adding a zfcp LUN to root file system logical volume

[Keith Gooding]

Thank you to everyone who responded. No, we did not run mkinitrd and zipl after 
adding the second LUN to the root file system. When we have added LUNs in the 
past it has been unnecessary because they were not needed during boot - I 
started to understand this just after I posted my question. (My linux knowledge 
is not very good - I understand z/OS and system z in general and do the 'z' 
parts of installing zLinux. A colleage who knows little about system z then 
takes over. There seems to be a big gap in our combined knowledge, but I have 
now learned something about the boot process - at least I now understand that 
'rd' in initrd stands for 'ram disk').
 
Unfortunately the volume groups in all of our systems are called 'VolGroup00' 
so I was not able to vgimport the group into a RH 5 system so I accessed it 
from a SUSE system which does not LVs so that I could rename it. I was just 
about to import it into a RH 5 system so that I could run initmkd and zipl 
under chroot when I read Steffen's refernce to the restrictions with LVs in RH 
5. The reason for adding the second PV was that the first was full, so it is 
possible that any new boot image will be created on the new physical volume. I 
think this is getting too difficult. Re-installing with a later release is 
probably more productive.
 
Incidentally I spent some time yesterday in attempting to enter kernel 
parameters using the SCPDATA option of LOADDEV in zVM V5.  (a). I assumed that 
the parameters have to be in ascii so I entered them in hexadecimal. (b). Is 
this method actually available for RH 5? - I found the reference in the RH 6 
documentation. (c). If  SCPDATA can be used with RH 5, what is the syntax of 
the zfcp options. I asssumed that it was "zfcp.device=0.0.,," 
but also tried the "rd.zfcp" format from RH 7. Should it be 'rh_zfcp" as in RH 
6 or is it not available at all ?
 
Keith
On Wednesday, 21 May 2014, 11:21, Steffen Maier  
wrote:
  


Hi Keith,

On 05/20/2014 02:36 PM, Keith Gooding wrote:
> We installed a RH 5.2 system where the root file system is on a
> logical volume comprising a single physical volume which is on zFCP LUN.
> Later we added another zFCP LUN, updated zfcp.conf and added the
> physical volume to the LV. This appeared to be OK until we had a
> scheduled reboot of the system.

Did you run mkinitrd and then zipl after having changed /etc/zfcp.conf?
RHEL5 simply copies activation statements of all entries of zfcp.conf 
into the initrd (whether those LUNs are needed for the root-fs or not, 
so it's at least sufficient to activate all LUNs for the root-fs).

> The boot starts OK until:
>
> Scanning logical volumes
> Reading all physical volumes.
> This may take a while...
> Couldn't find device with uuid 'YD0yYY-Ty0J-I303-2jqQ-4bYs-SSFx-QyzQzc'.
> Found volume group "VolGroup00" using metadata type lvm2
>
> Eventually it gives up because it cannot mount the root file system
> because the logical volume is incomplete.I was able to access both
> LUNs from another system and I ran vgimport on that system to check
> the zfcp.conf. It seems to be OK. Does anyone know if I need some
> entries in the zipl.conf file for the zfcp LUNs?.  The RHEL 7 (beta)
> documentation states that if the root file system is on a logical
> volume using zFCP then entries are needed in zipl.conf but I cannot
> find any instructions for RHEL 5, or indeed any documentation of the
> syntax for zipl.conf.  The zipl.conf which was generated by the RHEL
> 5 installer does not have any zfcp entries in zipl.conf.We could just
> install a new system with a larger root file system but I would like
> to be able to fix this if possible.Keith Gooding

This procedure is only different starting with RHEL6 (including RHEL7, 
where the syntax of rd_ZFCP= changed slightly to rd.zfcp=).
It's dracut (successor of mkinitrd) does not (depending on dracut 
config) copy activation statements from zfcp.conf into the initramfs, 
but the user (or anaconda during installation) has to use explicit 
rd.zfcp= statements as pseudo kernel boot parameters to activate LUNs of 
all paths required for the root-fs.
[https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ap-s390info-Adding_FCP-Attached_LUNs-Persistently.html
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html/Installation_Guide/sect-post-installation-fcp-attached-luns-persistent-s390.html]

Everything else, such as all data volumes (even /boot if it's not 
included in the root-fs) or scsi tapes only go into /etc/zfcp.conf.
[https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ap-s390info-Adding_FCP-Attached_LUNs-Persistently-Not_part_of_root_file_system.html
https://access.redhat.com/si

Adding a zfcp LUN to root file system logical volume

[Keith Gooding]

Hi all,
 
We installed a RH 5.2 system where the root file system is on a logical volume 
comprising a single physical volume which is on zFCP LUN. Later we added 
another zFCP LUN, updated zfcp.conf and added the physical volume to the LV. 
This appeared to be OK until we had a scheduled reboot of the system.
 
The boot starts OK until:
Scanning logical
volumes      
Reading all physical volumes.  This may
take a while... 
   Couldn't find device with uuid
'YD0yYY-Ty0J-I303-2jqQ-4bYs-SSFx-QyzQzc'.    Found volume group
"VolGroup00" using metadata type
lvm2   Eventually it gives up because it cannot mount the root file 
system because the logical volume is incomplete.I was able to access both LUNs 
from another system and I ran vgimport on that system to check the zfcp.conf. 
It seems to be OK. Does anyone know if I need some entries in the zipl.conf 
file for the zfcp LUNs?.  The RHEL 7 (beta) documentation states that if the 
root file system is on a logical volume using zFCP then entries are needed in 
zipl.conf but I cannot find any instructions for RHEL 5, or indeed any 
documentation of the syntax for zipl.conf.  The zipl.conf which was generated 
by the RHEL 5 installer does not have any zfcp entries in zipl.conf.We could 
just install a new system with a larger root file system but I would like to be 
able to fix this if possible.Keith Gooding 

--
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: PAV and FBA dasd emulated on SCSI

[Keith Gooding]

Thank you for your clear and comprehensive reply, Alan. I conclude that if I am 
concerned about possible I/O queuing with emulated FBA I should consider 
spreading the I/Os for a particular linux guest across mini-disks but it is OK 
to have a large SCSI LUNs shared with other guests because CP may perform 
parallel SCSI I/Os. (and I may want to consider the arrangement of the LUNs in 
relation to the physical disk arrays and controllers of course). Yes, I know 
that there is some overhead in using emulated FBA rather than linux native SCSI 
but it is so much more convenient, especially for test systems.

Keith Gooding


On Thu, 20/3/14, Alan Altmark  wrote:

 Subject: Re: [LINUX-390] PAV and FBA dasd emulated on SCSI
 To: "Keith Gooding" 
 Date: Thursday, 20 March, 2014, 20:54
 
 On Thursday, 03/20/2014 at 12:34 EDT,
 Keith Gooding 
 
 wrote:
 > I understand that without PAV an ECKD volume cannot
 have have multiple 
 I/O
 > operations in progress and therefore the operating
 system (or is it the 
 channel
 > ?) may have to queue I/Os to a volume. I know that this
 applies to z/OS 
 and I
 > assume that it also applies to z/VM and linux, and may
 be a reason to 
 avoid
 > using very large ECXD volumes.
 >
 > Does the same apply to a traditional channel-attached
 FBA volume (ie not
 > FCP-over-SCSI) ?.
 >
 > For mini-disks on z/VM emulated FBA on SCSI, I assume
 that at the z/VM 
 can
 > issue several simultaneous SCSI IOs to the LUN but will
 each linux guest 
 still
 > limit itself to one I/O per mini-disk ?.
 > Does the use of DIAG access to the mini-disk make any
 difference ?
 
 You are correct that PAV is needed to concurrently start
 more than one I/O 
 to the same volume.  The I/O queues are in the OS, not
 in the channel.  In 
 fact, it's the channel subsystem that rejects a second I/O
 to a device 
 that has an outstanding I/O.
 
 This I/O architecture applies to ECKD and FBA, virtual or
 real.   For 
 FBA-on-SCSI, the guest can do only one I/O, but as you
 suggest, CP can do 
 multiple I/Os to the SCSI LUN if he
 wishes.   Whether the guest uses SSCH 
 or DIAG, the rules are the same.
 
 That's half the equation.  Not only does the
 channel-attached FBA I/O 
 architecture have to be updated to support PAV, the host
 would have to be 
 updated to deal with it.  CP will not do PAV or
 advanced copy services on 
 FBA devices, even if they are modified to support it. 
 CP and other parts 
 of VM assume that real FBA devices are of 1980s vintage.
 
 Alan Altmark
 
 Senior Managing z/VM and Linux Consultant
 IBM System Lab Services and Training 
 ibm.com/systems/services/labservices 
 office: 607.429.3323
 mobile; 607.321.7556
 alan_altm...@us.ibm.com
 IBM Endicott
 

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

PAV and FBA DASD emulated on SCSI

[Keith Gooding]

I understand that without PAV an ECKD volume cannot have have multiple I/O 
operations in progress and therefore the operating system (or is it the channel 
?) may have to queue I/Os to a volume. I know that this applies to z/OS and I 
assume that it also applies to z/VM and linux, and may be a reason to avoid 
using very large ECXD volumes.


Does the same apply to a traditional channel-attached FBA volume (ie not 
FCP-over-SCSI) ?.

For mini-disks on z/VM emulated FBA on SCSI, I assume that at the z/VM can 
issue several simultaneous SCSI IOs to the LUN but will each linux guest still 
limit itself to one I/O per mini-disk ?.
Does the use of DIAG access to the mini-disk make any difference ?

Keith

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

PAV and FBA dasd emulated on SCSI

[Keith Gooding]

I understand that without PAV an ECKD volume cannot have have multiple I/O 
operations in progress and therefore the operating system (or is it the channel 
?) may have to queue I/Os to a volume. I know that this applies to z/OS and I 
assume that it also applies to z/VM and linux, and may be a reason to avoid 
using very large ECXD volumes.


Does the same apply to a traditional channel-attached FBA volume (ie not 
FCP-over-SCSI) ?.

For mini-disks on z/VM emulated FBA on SCSI, I assume that at the z/VM can 
issue several simultaneous SCSI IOs to the LUN but will each linux guest still 
limit itself to one I/O per mini-disk ?.
Does the use of DIAG access to the mini-disk make any difference ?

Keith

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

Performance effect of multiple virtual processors

[Keith Gooding]

Hi all,
 
Suppose I have a linux zVM guest with n virtual IFLs running in a z/VM LPAR 
which has n dedicated IFLs. If the guest is dormant and becomes eligible to run 
again ( eg I/O completes) does the zVM scheduler wait for all n  real IFLs to 
be free before dispatching it ?. I thought I saw  something a long time ago 
that said it does indeed wait for all of the required CPUs to become available 
but I cannot find any information about it now. 
 
TIA
Keith Gooding 

--
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: Cloning SUSE 11 SP2 SAN Volume Controller LUN

[Keith Gooding]

Thanks Mark. I think I understand (I am really a z/OS person).
 
Since my first post I did manage to IPL a cloned system: I booted up with 
kernel parameter "root=/dev/mapper/360050768018f030ee04c_part2" to 
override "root=/dev/mapper/360050768018f030ee04b_part2".  Then I 
was able to put the new UUID into the zipl.conf and fstab files and it seemed 
to reboot OK (after running zipl). 
 
I can see (now that I understand the problem better) that your suggestion of 
using alias names would make it simpler. Incidentally the installer did not 
create /etc/multipath.conf. Is this something that we have to create if we want 
any non-standard definitions ?  .
 
Keith Gooding



From: Mark Post 
To: Keith Gooding  
Sent: Thursday, 3 January 2013, 19:07
Subject: Re: Cloning SUSE 11 SP2 SAN Volume Controller LUN

>>> On 1/3/2013 at 08:22 AM, Keith Gooding  wrote: 
> For SUSE 11 SP2 a colleague has installed using multipath for the root. I 
> copied the vdisk as before. I am able to boot a new linux VM from the new 
> vdisk but start-up does not complete. Does anyone know if it is possible to 
> clone using this method when multipath is used ?

Yes, but as you can tell it's going to involve more work, since the device 
names are going to be different for each clone you make.  Perhaps the simplest 
method would be to use /etc/multipath.conf to create alias names for the 
multipath devices and use those in places such as /etc/zipl.conf, and 
/etc/fstab.  Then, when you clone, you would need to update multipath.conf with 
the new "wwid" values and (probably) recreate the initrd on the clone.


Mark Post

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

Cloning SUSE 11 SP2 SAN Volume Controller LUN

[Keith Gooding]

In the past we have created a number of linux 'golden images' of various linux 
releases, each on a single IBM SAN Volume Controller virtual disk accessed with 
native zFCP. Multipath was not used. They could be cloned by making a copy of 
the SVC vdisk using SVC facilities and mapping to the new host using the same 
LUN number (0x0001 ie LUN 1). The new host was booted and its IP 
address/hostname could then be edited for the new system.

For SUSE 11 SP2 a colleague has installed using multipath for the root. I 
copied the vdisk as before. I am able to boot a new linux VM from the new vdisk 
but start-up does not complete. Does anyone know if it is possible to clone 
using this method when multipath is used ?

The copy has a different UUID of course.  The original vdisk has a UUID ending 
'...04b' and the copy has UUID ending '.04c'. I 
get these messages before the start-up is abandoned and it exits to a recovery 
shell:

Setup multipath devices: Jan 03 12:04:46 | 360050768018f030ee04c: 
failed to set dev_loss_tmo: error 22    
>Jan 03 12:04:46 | 360050768018f030ee04c: failed to set 
>dev_loss_tmo: error 22 
>Jan 03 12:04:46 | 360050768018f030ee04c: failed to set 
>dev_loss_tmo: error 22 
>Jan 03 12:04:46 | 360050768018f030ee04c: failed to set 
>dev_loss_tmo: error 22 
>ok.
>   
>Trying manual resume from /dev/mapper/360050768018f030ee04b_part1  
>   
>resume device /dev/mapper/360050768018f030ee04b_part1 not found 
>(ignoring)    
>Trying manual resume from /dev/mapper/360050768018f030ee04b_part1  
>   
>resume device /dev/mapper/360050768018f030ee04b_part1 not found 
>(ignoring)    
>Waiting for device /dev/mapper/360050768018f030ee04b_part2 to 
>appear: ..Could not find
>/dev/mapper/360050768018f030ee04b_part2.   
>   
>Want me to fall back to /dev/mapper/360050768018f030ee04b_part2? 
>(Y/n) 
>y
>Waiting for device /dev/mapper/360050768018f030ee04b_part2 to 
>appear: ..not found -- ex
>iting to /bin/sh   
 regards,
Keith Gooding
In /dev/mapper we have:
360050768018f030ee04c -> ../dm-0  
360050768018f030ee04c_part1 -> ../dm-1
360050768018f030ee04c_part2 -> ../dm-2 


--
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: Installing SLES 10 SP3 on z/VM emulated FBA disks

[Keith Gooding]

Thanks to everyone who responded. I have now managed to install onto FBA 
mini-disks. 

Having understood the information about FBA disks not requiring formatting, and 
that there could be only one partition on a disk, I used 'Edit' on the 
Partitioner panel to specify mount point for the partions. I also found that I 
had to select 'format' within the Edit dialogue and set the file system to ext3 
(although ext3 was the only one I tried). The installer presumably then did the 
'pseudo partitioning' which was mentioned in one of the posts. The install 
failed if I left the default 'Do not format' option - I cannot remember the 
error codes/messages. 


Keith Gooding

 




From: martin roby 
To: LINUX-390@VM.MARIST.EDU
Sent: Tue, 31 August, 2010 21:29:34
Subject: Re: Installing SLES 10 SP3 on z/VM emulated FBA disks

I installed using eckd disks. I had a hard time. My install would hang.

Then I went into the mini install shell and used dasdfmt and then
fdisk to create
just twm partitions (/boot and /) on the drive. The next reboot worked
fine. I did not use lvm,

I ended up doing the whole install onto one partition.


On Tue, Aug 31, 2010 at 1:00 PM, Keith Gooding  wrote:
> Has anyone had any success in installing SLES 10 onto z/VM emulated 9336
> mini-disks ?.  I have been trying to follow the IBM 'SLES 10 SP2 Cookbook'
> Redbook, but using emulated FBA (9336) mini-disks instead ECKD disks. But the
> installer only appears to support CKD disks or iSCSI (or ZFCP?) disks.
>
> Or should I give up and use CKD for the system and emulated FBA for other file
> systems ?
>
> Keith
>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

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





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

Re: Installing SLES 10 SP3 on z/VM emulated FBA disks

[Keith Gooding]

Thank you for you quick reply Mark.

I am not using AutoYast so it must be a manual install - I just created the 
parmfile and used the sample VM exec provided with the Redbook to punch the 
kernel+parmfile+intrdr and ipl from the card reader. I can see the FBA devices 
on the DASD Disk Management screen and they appear as type 9336 with 
'formatted=yes' after I click 'activate'. The install fails if I try to format 
them. On the subsequent 'Installations Settings' panel under "Partitioning" 
there is a red message "No automatic proposal possible.Specify mount points in 
the 'Partitioner' dialogue". It seems to think there is a full-volume partition 
/dev/dasda1 etc on each volume (I have not created any partitions) and an 
attempt to delete the partition results in message 'Operation not permitted on 
disk /dev/dasda. The partitioning on your disk is either not readable by partd 
or is not supported by this tool. etc. I used 'expert' mode to delete the 
partition before adding new ones but eventually the install filed with 
'unsupported disk type'.

Maybe I should consider Autoyast as a way to set up (near) clones. I found that 
using native FCP was awkward when making clones and VM EDEVICES seemed to 
provide an easier method (I am not sure how inefficient edevices are but in 
many 
cases it does not matter)

Keith Gooding





From: Mark Post 
To: LINUX-390@VM.MARIST.EDU
Sent: Tue, 31 August, 2010 18:11:44
Subject: Re: Installing SLES 10 SP3 on z/VM emulated FBA disks

>>> On 8/31/2010 at 01:00 PM, Keith Gooding  wrote: 
> Has anyone had any success in installing SLES 10 onto z/VM emulated 9336 
> mini-disks ?.  I have been trying to follow the IBM 'SLES 10 SP2 Cookbook' 
> Redbook, but using emulated FBA (9336) mini-disks instead ECKD disks. But 
> the 
> installer only appears to support CKD disks or iSCSI (or ZFCP?) disks.
> 
> Or should I give up and use CKD for the system and emulated FBA for other 
> file 
> systems ?

Are you trying to use AutoYaST, or are you doing a manual install?  If a manual 
install, you should be seeing the FBA devices in the activation screen.  If an 
AutoYaST install, then you might have run into Bug 591601 - Unable to get 
AutoYaST to successfully use FBA DASD for LVM PVs.


Mark Post

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





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

Installing SLES 10 SP3 on z/VM emulated FBA disks

[Keith Gooding]

Has anyone had any success in installing SLES 10 onto z/VM emulated 9336 
mini-disks ?.  I have been trying to follow the IBM 'SLES 10 SP2 Cookbook' 
Redbook, but using emulated FBA (9336) mini-disks instead ECKD disks. But the 
installer only appears to support CKD disks or iSCSI (or ZFCP?) disks.

Or should I give up and use CKD for the system and emulated FBA for other file 
systems ?

Keith




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

Installing Redhat 5.3 on zVM emulated 9336 FBA - HCPVMI232E IPL UNIT ERROR

[Keith Gooding]

 (IBM Hi All,

I have been following the zVM 5.4 "Getting Started with Linux on System z" 
guide to install RH 5.3, but using SCSI-attached disks (IBM SVC) via 
9336-emulation for both the target linux system  minidisks and the CMS 
mini-disk which contains the redhat.conf file.

After booting from the kernel image it lists the parm file contents but appears 
to ignore the conf file so I reply to the install prompts. After the yoiu may 
safely reboot your system' message I get:

HCPVMI232E IPL UNIT ERROR; IRB 00404017 0010 0020 0080

which I think means that there is no boot record on the disk.

Does anyone know if this is supposed to work ?.  

Keith




--
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: Using non-IBM SCSI disks with zLinux and zVM

[Keith Gooding]

Hi all,

Thank you for your replies. I think it is clear now that the Sun 3510 FC 'JBOD' 
box cannot work with zseries FCP (the JBOD version has no controller so it is 
just an FC-AL string). A standard 3510 may work. Looking at other posts I see 
that some of the Clariion devices do work although not officially supported by 
EMC.

 I am still interested to hear of any details of specific configurations of 
'mid-range' disk systems which are working successfully with zFCP, even if not 
officially supported i.e. not EMC Symmetrix, IBM DS6000/DS8000, Sun Storagetek 
9900 or other system which supports zseries native FICON and CKD disks in 
addition to FCP. (Reply off-list in confidence if you wish). 

The a development shop which has lots of different platforms and OS 
versions/releases for testing purposes. The usual zseries reilience 
requirements do not apply and of course we have pukka zseries DASD for the 
important stuff.

Keith





From: Raymond Higgs 
To: LINUX-390@VM.MARIST.EDU
Sent: Thu, 3 December, 2009 22:56:57
Subject: Re: Using non-IBM SCSI disks with zLinux and zVM

Linux on 390 Port  wrote on 12/02/2009 08:57:45
AM:

> Keith Gooding 
> Sent by: Linux on 390 Port 
>
> 12/02/2009 08:57 AM
>
> Please respond to
> Linux on 390 Port 
>
> To
>
> LINUX-390@VM.MARIST.EDU
>
> cc
>
> Subject
>
> Using non-IBM SCSI disks with zLinux and zVM
>
> Hi ... Does anyone have any experience of using FCP-attached non-IBM
> disks with zseries linux and/or VM ?.
>
> The IBM documentation I can find says that certain IBM and Hitachi
> disks are supported. Other manufacturers have disks systems
> specifically designed for zseries, which tend to be expensive.
> Presentations on zseries SCSI over FCP often say that 'other disks
> may work but are not supported' . I would like to try out SCSI over
> FCP point-to-point with some some disks which have been used with a
> Sun unix server - specifically Sun Storedge 3510FC in a JBOD
> configuration. When I activate the channel there is a 'sequence
> time-out'. I would like to know if anyone has used  'unsupported'
> SCSI disks in this way. The zseries machine is for development use
> only and I am not concerned with the usual zseries resilience issues.
>
> keith
>
>
>
>
> --
> 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

Keith,

We haven't tested Sun Storedge 3510 FC, in fact I've never seen one.
Anyway, I'd double check these:

Make sure that the optics and fibre are consistent.  Either all long wave,
or all short wave.  No mixing.
Make sure that the channel is really connected to the sun storage.  I
know, I know it sounds obvious, but when fibres disappear under the floor,
or go through patch panels, it can be confusing.
Make sure that the pchid that you think is fcp is really defined as fcp in
the IOCDS, and not ficon.
Use the "analyze link error statistics block" panel on the SE to see if
you're getting a bunch of bit errors.
There are 2 flavors of point-to-point out there in the wild.  We support
the official point-to-point topology defined in fc-fs.  We do not support
that special case of arbitrated loop where there are 2 nl_ports.

There isn't any firmware to prevent you from using unsupported storage. We
don't usually hear about unsupported storage configs., but the little bit
that we have heard is mostly EMC Clariion.

Regards,

Ray Higgs
System z FCP Development
Bld. 706, B24
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com

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





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

Re: Using non-IBM SCSI disks with zLinux and zVM

[Keith Gooding]

Thank you Jakub. DMX is 'high-end' storage and is supported for linux on 
zseries according to the EMC compatibility matrix document. But I can see no 
mention of zseries anywhere in the Clariion documents. So if you are working OK 
with an FCP attachment to Clariion it does suggest that zlinux FCP will work 
with 'industry standard' mid-range disks. 

Keith





From: Szefler Jakub - Hurt TP 
To: LINUX-390@VM.MARIST.EDU
Sent: Thu, 3 December, 2009 11:24:48
Subject: Re: Using non-IBM SCSI disks with zLinux and zVM

Hi,
We have some experience . We attach over FCP to zlinux EMC matrix (clarion
and dmx) and it is supported.


Jakub Szefler
Administrator Mainframe



-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Keith
Gooding
Sent: Wednesday, December 02, 2009 2:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Using non-IBM SCSI disks with zLinux and zVM

Hi ... Does anyone have any experience of using FCP-attached non-IBM disks
with zseries linux and/or VM ?. 

The IBM documentation I can find says that certain IBM and Hitachi disks are
supported. Other manufacturers have disks systems specifically designed for
zseries, which tend to be expensive. Presentations on zseries SCSI over FCP
often say that 'other disks may work but are not supported' . I would like
to try out SCSI over FCP point-to-point with some some disks which have been
used with a Sun unix server - specifically Sun Storedge 3510FC in a JBOD
configuration. When I activate the channel there is a 'sequence time-out'. I
would like to know if anyone has used  'unsupported'  SCSI disks in this
way. The zseries machine is for development use only and I am not concerned
with the usual zseries resilience issues.

keith




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

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




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

Using non-IBM SCSI disks with zLinux and zVM

[Keith Gooding]

Hi ... Does anyone have any experience of using FCP-attached non-IBM disks with 
zseries linux and/or VM ?. 

The IBM documentation I can find says that certain IBM and Hitachi disks are 
supported. Other manufacturers have disks systems specifically designed for 
zseries, which tend to be expensive. Presentations on zseries SCSI over FCP 
often say that 'other disks may work but are not supported' . I would like to 
try out SCSI over FCP point-to-point with some some disks which have been used 
with a Sun unix server - specifically Sun Storedge 3510FC in a JBOD 
configuration. When I activate the channel there is a 'sequence time-out'. I 
would like to know if anyone has used  'unsupported'  SCSI disks in this way. 
The zseries machine is for development use only and I am not concerned with the 
usual zseries resilience issues.

keith




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