How about another spin to this question: Assuming that one has created
an LVM2 environment on their zFCP disks, can one then multipath those
disks? If so, should one be using the multipath-tools utilities rather than
EVMS? Opinions?
Robert J Brenneman wrote:
Never tried that, but I have a
Tony Kubinski wrote:
How about another spin to this question: Assuming that one has created
an LVM2 environment on their zFCP disks, can one then multipath those
disks? If so, should one be using the multipath-tools utilities rather than
EVMS? Opinions?
Uhh, I would'nt try such thing. What's
It came to my attention that multipathing via EVMS was probably not the
correct method, rather using the multipath-tools set was.
If you are suggesting that it's acceptable to multipath zFCP disks thru the
EVMS plugin, can you elaborate with a simple example?
Carsten Otte wrote:
Tony
Tony Kubinski wrote:
It came to my attention that multipathing via EVMS was probably not the
correct method, rather using the multipath-tools set was.
If you are suggesting that it's acceptable to multipath zFCP disks thru the
EVMS plugin, can you elaborate with a simple example?
The evms
Hello list,
Has anyone successfully installed SLES-9 on a FLEX-ES system? We have
seen at least two instances where the second half of the install process
(after IPLing from disk) fails. It seems to be a network issue for which I
don't have a lot of details at this point. But I was just
I have SLES9 running under Flex and do not recall having any install
problems.
Michael MacIsaac wrote:
Hello list,
Has anyone successfully installed SLES-9 on a FLEX-ES system? We have
seen at least two instances where the second half of the install process
(after IPLing from disk) fails. It
Mark,
that was helpful, the make -C /lib/modules/`uname -r`/build
M=3D`pwd` SUBDIRS=3D`pwd`
module ran ok with a link from
/usr/src/kernel-source-2.6.8 to /lib/modules/2.6.8-2-s390/build, that
allows me to get a module that will force load. The next stumbling block
is the dynamic creation of
Mike,
We are having the same problem. SuSE support has been unable to figure
it out and we have a ticket open with IBM. They didn't have a Flex
system so they are setting one up now though it may be a couple of weeks
before they get back to us. The problem we experienced was that after
the IPL
On Thu, 29 Sep 2005 08:14:20 -0700, Paul Ohmart wrote:
Mike,
We are having the same problem. SuSE support has been unable to figure
it out and we have a ticket open with IBM. They didn't have a Flex
system so they are setting one up now though it may be a couple of weeks
before they get back to
I have the Redbook on the subject and am trying this.
We are at level SP2 on the SLES9 system and the directory layout and files
that actually exits on the master system do not match what's mentioned in
the Redbook.
I tried to 'feel my way around' but the IPL of the clone fails. I suspect
my
Trying to setup a test zFCP multipathed environment on a SLES9
z/VM instance and want to use the EVMS (2.3.3) that comes with
the distro. The supplied docs point to
http://evms.sourceforge.net/user_guide
for the user guide but that points to the current release's (2.5.3)
guide.
It appears
I have an existing SLES9 SP1 and trying to install the SP2 update.
I down loaded the three ISO files from the SuSE Portal. All checked out ok
with MD5SUM.
I then uploaded them to a SLES8 system that we use as a software
repository.
Umounted that filesystem and mounted to the SLES9 that we want to
You need to copy the first two CDs into a common directory and use that as
your installation source. The third CD is only source files and is not
needed to apply the service pack.
I have an existing SLES9 SP1 and trying to install the SP2 update.
I down loaded the three ISO files from the SuSE
Do you mean to mount loop back and then copy the contents of CD1 and CD2
into a new subdirectory 'xxx'
and use 'xxx' as the new source location ?
TIA ..
---
Bill replied:
You need to copy the first two CDs into a common
Read the README on the SP2 cd. You need to register the SP as an
installation source before running the upgrade.
I do not recall having these types of problems with service
packs on SLES8.
--
For LINUX-390 subscribe / signoff
I assume you mean change the source location or is there an actual
registration ?
I did change the source location.
thanks ...
-
David Replied:
Read the README on the SP2 cd. You need to register the SP as an
installation source before
Exactly. Loop mount the first ISO files and CD to the mount point then do:
cp -av * ../xxx. Repeat for the
second ISO file. xxx then becomes your installation source. You should
update yast2-online-update, yast2-ncurses, and yest2-packagemanager before
doing the system update or patch CD update,
17 matches
Mail list logo
