On Thu, Jul 30, 2009 at 1:33 AM, Marcy
Cortesmarcy.d.cor...@wellsfargo.com wrote:
Question, what is the value of using diag for swapping to vdisk?
Even if it is a more efficient driver, you're swapping to memory. How much
does it save?
Hey, what's happening. Wasn't I supposed to ask those
Dear all,
In this matter I reinstalled now a SLES 10 as Installation server and there
is NO problem in handling the LV. Because of this I conclude:
This is a problem in SUSE11 and not in z/VM or with the hardware. I checked
with a vanilla SLES 11 GA installation and this issue is also happening
In SLES 11, can you still code dasd= in the kernel parameter line of zipl.conf?
The SLES 11 Device Drivers manual no longer mentions dasd= is supported in the
kernel parameter line;
unlike earlier editions that did cover that method of configuring the dasd
driver.
-Original Message-
On 7/30/2009 at 12:18 PM, Romanowski, John (OFT)
john.romanow...@cio.ny.gov
wrote:
In SLES 11, can you still code dasd= in the kernel parameter line of
zipl.conf?
The SLES 11 Device Drivers manual no longer mentions dasd= is supported in
the kernel parameter line;
unlike earlier
That explains that?
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Mark Post
Sent: Thursday, July 30, 2009 12:23 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problems with SLES 11 and LVM
On 7/30/2009 at 12:18 PM, Romanowski, John (OFT)
On 7/30/2009 at 11:25 AM, Florian Bilek florian.bi...@gmail.com wrote:
-snip-
Maybe somebody from Novell could help me in this matter because I think this
is an essential problem of SLES11 and other implementations could easily
face the same problem.
Florian, as you were told, a bug report
On 7/30/2009 at 12:27 PM, Romanowski, John (OFT)
john.romanow...@cio.ny.gov
wrote:
That explains that?
Yes. The modinfo command is showing that the dasd_mod kernel module accepts a
parameter of dasd with multiple values.
Mark Post
John,
In SLES 11, can you still code dasd= in the kernel parameter line of
zipl.conf?
I have used it in SLES 11 and it appears to work.
Mike MacIsaac mike...@us.ibm.com (845) 433-7061
--
For LINUX-390 subscribe / signoff /
Mark,
I understood from the support people that there was no real hope to have a
fix for that soon because of no L3 support. I had the impression that those
things won't get any priority.
Since I don't know the reason of the problem regarding the dm driver, it is
qute difficult for me to plan
So can anyone help me on this? I am still stuck. When I copy the volumes and
then IPL from the new UCB It will only recognize the old volumes but I have
changed everything in zipl.conf and fstab.
One of my thoughts is that I need to change dasd_mod. During boot I get
these messages:
Starting
Paul,
If you have access to a installation Linux, try this:
1 - start the installation as if you would reinstall from scratch
2 - somewhere in the installation, the installer will activate the dasds for
you. as soon as it happens, drop to a shell (connect another session, and
under sles or rhel
Did you run zipl and mk_initrd?
-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Paul Meier
Sent: Thursday, July 30, 2009 10:26 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Moving native linux
So can anyone help me on this? I am still stuck. When I
On 7/30/2009 at 10:25 AM, Paul Meier pm.mli...@gmail.com wrote:
So can anyone help me on this? I am still stuck. When I copy the volumes and
then IPL from the new UCB It will only recognize the old volumes but I have
changed everything in zipl.conf and fstab.
One of my thoughts is that I
Thanks,
I did not run mkinitrd. I did everything else but that. It works now!
Thanks!
On Thu, Jul 30, 2009 at 1:53 PM, Mark Post mp...@novell.com wrote:
On 7/30/2009 at 10:25 AM, Paul Meier pm.mli...@gmail.com wrote:
So can anyone help me on this? I am still stuck. When I copy the volumes
14 matches
Mail list logo
