As of this morning, the SUSE_SLES-SP3-migration patch is still not available,
at least for s390x.
Chris
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Leland
Lucius
Sent: Wednesday, July 03, 2013 10:05 AM
To: LINUX-390@VM.MARIST.EDU
Subject:
On 7/8/2013 9:37 AM, Will, Chris wrote:
As of this morning, the SUSE_SLES-SP3-migration patch is still not available,
at least for s390x.
Weird...I went through an upgrade on one of my play servers and it's now
at 11.3. I did kind of rush through it just to satisfy that instant
Here is the patch for going to SP2 that was in the SLES11-SP1-Updates channel.
I don't see anything similar in the SLES11-SP2-Updates channel. As I recall,
it was a few weeks after the SP2 announcement when this showed up. We use SMT
for pulling patches from Novell.
On 7/8/2013 at 10:37 AM, Will, Chris cw...@bcbsm.com wrote:
As of this morning, the SUSE_SLES-SP3-migration patch is still not available,
at least for s390x.
It should be released before very long. It was held up until the kernel in SP3
Updates was at a higher level than the current SP2
On 7/8/2013 10:25 AM, Leland Lucius wrote:
One thing I do recall having difficulty with though is that zypper
doesn't like the checksums in the mirrored repodata files. They contain
a sha256 checksum, but zypper seems to truncate it to 40 bytes and it
complains that it doesn't match the type.
I have many Linux guests running on z/VM. We are in the process of
migrating ECKD DASD from old switches to new switches. I am trying to find
out how Linux stores the paths information, how to display what Linux
thinks and whether there is a way to tell Linux to re-validate its path
information.
I would think this would be transparent to a guest it's path will be
the minidisk .. which won't change - unless I misunderstand what you mean
by switches. Are you presenting the DASD as minidisks, or attaching them?
Either way I don't see the pathing changing at the Linux level.
Scott
That is what I thought too. However, some guests are having issues. Some
parts of lvm groups switched to r/o. Some page errors. It is not
consistent. I'm confused!
Rick Barlow
Nationwide
On Mon, Jul 8, 2013 at 11:34 PM, Scott Rohling scott.rohl...@gmail.comwrote:
I would think this would
Perhaps the UUID' s of the DASD got changed or mangled at the CP level?
David Kreuter
Original message
From: Rick Barlow rrhbar...@gmail.com
Date:
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Where does Linux store path information for dasd devices?
That is what I thought
inline: velologo.gifinline: Facebook.jpginline: LinkedIn.jpginline: TwitterL.jpginline: XingButt.jpg
Do you have any errors on any of these new paths? I recently learned linux
will switch to read only after 256 failed i/o. Any erep records generated?
Marcy. Sent from my BlackBerry.
- Original Message -
From: Rick Barlow [mailto:rrhbar...@gmail.com]
Sent: Monday, July 08, 2013
Thanks Marcy. That is a good thought. Unfortunately, EREP doesn't even
log errors unless there are 10 consecutive failures. So intermittent
errors can go unrecorded. Depending on how Linux counts, that could be
possible.
We had issues on about a dozen Linux guests spread across 4 z/VM LPARs
12 matches
Mail list logo
