Yes, we actually worked with our account team from IBM and they brought in
some of the IBM experts to help us take a closer look at this. It was
determined that the additional memory was needed due to the database change
between the two versions. Given enough memory, I think it would work fine.
Thanks for posting this problem Craig. We were about to obtain some new
hardware as part of our upgrade plans including TSM on zLinux. It doesn't
sound like this is worth pursuing in light of your problems. But, I have
to say it is not entirely unexpected. It seems like one part of IBM doesn't
QETH_PORTNO=1
in /etc/sysconfig/hardware/hwcfg-qeth-bus-ccw-0.0.1200 was the trick.
Chuck Tribolet
trib...@almaden.ibm.com (IBM business)
trib...@garlic.com (Personal)
http://www.almaden.ibm.com/cs/people/triblet
From: Chuck Tribolet/Almaden/IBM
To: linux-...@www2.marist.edu
Date:
On Tuesday, 03/08/2011 at 11:06 EST, Mark Post mp...@novell.com wrote:
On 3/8/2011 at 09:08 PM, Chuck Tribolet trib...@almaden.ibm.com
wrote:
PORTNO=1
ETHTOOL_OPTIONS=''
LLADDR=''
MTU=''
NAME=''
REMOTE_IPADDR=''
USERCONTROL='no'
What am I missing?
Try QETH_PORTNO.
Mark,
I am having a problem with cloning zLinux systems ( use DirMaint clonedisk
command to create the 201 disk for our cloned zlinux guests)
This is a SuSE10 sp2 system we run the cloning process from
My process will create a single clone without problem.
vmcp link userid 201 20f mr
chccwdev -e 20f
Linking the same disk r/w twice will likely destroy the disk.
Link it RR instead.
Marcy
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Gary Detro
Sent: Wednesday, March 09, 2011 10:03 AM
To: LINUX-390@vm.marist.edu
Subject: [LINUX-390] Cloning
Gary --
There is nothing in the kernel that cares if two disks have identical
content unless you mount by label, which you did not. (And I am
counting PV stamps as labels.)
I gotta wonder if your second 'vmcp link' acquired a RO link instead
of a RW link? You were right to use the mr token,
Oh ... yeah ... she's right (of course).
Did userid change from the first to the second? Guessing it did,
but if it did not ... that would explain the problem.
-- R;
Rick Troth
Velocity Software
http://www.velocitysoftware.com/
On Wed, Mar 9, 2011 at 13:18, Marcy Cortes
Sorry I didn't make it clear the 20f and 20e are not he same disk.
link linux73 201 20f mr
link linux77 201 20e mr
Thanks,
Gary L. Detro
Senior IT Specialist 1177 S. Belt Line Rd; Coppell, TX 75019
Internal Mail Stop: 77-01-3001O; Coppell, TX
Phone: 469-549-8174 (t/l 603-8174); Fax:
What do you get from:
lsdasd
file -s /dev/disk/by-path/ccw-0.0.020e
file -s /dev/disk/by-path/ccw-0.0.020e-part1
On Wed, Mar 9, 2011 at 1:24 PM, Gary Detro de...@us.ibm.com wrote:
Sorry I didn't make it clear the 20f and 20e are not he same disk.
link linux73 201 20f mr
link linux77 201
No - you can mount 2 separate DASD's as long as they aren't LVM volumes
- no problem.
So - does that file exist?(the config for the 4220) ..if not, why
not?Need more info about your clones..
Also - are you sure it's /dev/dasdc1 ? Did you do an lsdasd to confirm?
Scott Rohling
I don't know what cloning process you're using, but if it is a shell
script and if it uses hard-coded names for its work files ... just a
guess.
-- R;
Rick Troth
Velocity Software
http://www.velocitysoftware.com/
On Wed, Mar 9, 2011 at 13:02, Gary Detro de...@us.ibm.com wrote:
I am
yes the lsdasd showed both dasdb and dasdc ...
but when I examine the directory /dasdc it is empty
Thanks,
Gary L. Detro
Senior IT Specialist 1177 S. Belt Line Rd; Coppell, TX 75019
Internal Mail Stop: 77-01-3001O; Coppell, TX
Phone: 469-549-8174 (t/l 603-8174); Fax: 469-549-8235 (t/l
I did a google search for QETH_PORTNO in PDF files only. The only hits
were from Debian. ;-)
Chuck Tribolet
trib...@almaden.ibm.com (IBM business)
trib...@garlic.com (Personal)
http://www.almaden.ibm.com/cs/people/triblet
From: Alan Altmark/Endicott/IBM@IBMUS
To:
Odd.. it must have a empty filesystem on it or it wouldn't mount..DIRM
CLONEDISK is doing a physical copy. Unless the CLONEDISK failed (and there
was a previous empty filesystem on the disk), I'm not sure why you're seeing
an empty directory. Maybe show us a 'df -h' command as well as an
None of the commands you've given us here would add anything onto /dasdc
How was it supposed to have gotten populated with files?
Marcy Cortes
Operating Systems Engineer, z/VM and Linux on System z
Enterprise Hosting Services, Mainframe/Midrange Services
Wells Fargo Bank | 201 Third Street |
Make that 'df -Th' it would be good to see the filesystem types too..
Scott Rohling
On Wed, Mar 9, 2011 at 12:03 PM, Scott Rohling scott.rohl...@gmail.comwrote:
Odd.. it must have a empty filesystem on it or it wouldn't mount..
DIRM CLONEDISK is doing a physical copy. Unless the
sigh Gary did you per chance get DATAMOVEd? Can you check
dirmaint/datamove logs? Is the workunit hanging around?
David
Original Message
Subject: Re: Cloning question for zLinux
From: Scott Rohling scott.rohl...@gmail.com
Date: Wed, March 09, 2011 2:05 pm
To:
When the scripts are running I can see Dirmaint creating the disks (using
flashcopy, so I don't have to wait until the copy completes). The process
also does a lsdasd and shows the disks that are online (in the failing
case, both targets are online and have been mounted without any error
It's not necessarily true that you don't need to wait until the copy
completes... if the FLASHCOPY gets an RC0 - ok -- but if it gets a RC
indicating for example - that there are already pending flashcopies for the
device -- I'm not sure offhand if DATAMOVE tries again or fails the
workunit.
On 3/9/2011 at 12:17 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
Try QETH_PORTNO.
Mark, where is this mechanism documented? The Device Driver book (even
for SLES 11) does not refer to such.
It's not that I know of. Since this is a parm that was only used in SLES10, it
wouldn't be
On Wednesday, 03/09/2011 at 05:40 EST, Mark Post mp...@novell.com wrote:
On 3/9/2011 at 12:17 PM, Alan Altmark alan_altm...@us.ibm.com
wrote:
Try QETH_PORTNO.
Mark, where is this mechanism documented? The Device Driver book
(even
for SLES 11) does not refer to such.
It's not that I
It seems the goal 'would' be to document 'every last thing that can be put
in those files' to me as well.. Why code for it if you're not going to
document it? 'Mystery features' and 'hacks' are for games ;-)
Scott Rohling
On Wed, Mar 9, 2011 at 4:02 PM, Alan Altmark
On 3/9/2011 at 06:02 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
Strange. Then what would be the equivalent for SLES 11? Doesn't changing
it create a compatibility/upgrade problem?
That would be a udev rule under /etc/udev/rules.d/. You _really_ don't want
people editing those by
On 3/9/2011 at 06:06 PM, Scott Rohling scott.rohl...@gmail.com wrote:
It seems the goal 'would' be to document 'every last thing that can be put
in those files' to me as well.. Why code for it if you're not going to
document it? 'Mystery features' and 'hacks' are for games ;-)
I don't
Ok - I thought this was a distro specific issue -- RHEL and SLES use
entirely different files to configure network devices ... I just thought the
end result was supposed to be what is documented in Device Drivers (a
resulting /sys setting...). I thought RHEL and SLES made up the
configuration
On Wednesday, 03/09/2011 at 06:12 EST, Mark Post mp...@novell.com wrote:
On 3/9/2011 at 06:02 PM, Alan Altmark alan_altm...@us.ibm.com
wrote:
Strange. Then what would be the equivalent for SLES 11? Doesn't
changing
it create a compatibility/upgrade problem?
That would be a udev rule
On 3/9/2011 at 06:27 PM, Alan Altmark alan_altm...@us.ibm.com wrote:
I'm expressing my ignorance now. I thought that the startup scripts that
read config files and construct the ifconfig commands were provided by the
distro and are not part of Linux, per se.
That's true. (Of course, not
28 matches
Mail list logo
