It was two vgs during install. mkinitrd and zipl fixed the problem.
Thanks all.
>>> [EMAIL PROTECTED] 9/2/2005 2:50:33 PM >>>
Did you create two Volume Groups, or just two Logical Volumes from one
Volume Group?Robert Nix had a problem where he created two VGs
during the install of a SLES9 S
Did you create two Volume Groups, or just two Logical Volumes from one
Volume Group?Robert Nix had a problem where he created two VGs
during the install of a SLES9 SP2 system, and when the system tried to
boot, the LVs weren't available. Removing one of the two VGs "fixed"
the problem.
Mark
David wrote:
>I think also that VM TCPIP is smart enough to look at the system ID and
execute a
>specific profile based on the system id.
It is and that works well (that's how we do it). But MPROUTE is not so
clever in the current release. So you still need to work that one out
with either an ex
> This is a SLES9 sp2 on z/vm. We have created two lvm groups
> and then our required mount points. We then successfully
> mount the new slices.
> When we reboot the second LVM is not seen nor mounted. This
> is all done through yast.
You forgot to mkinitrd and zipl following the new volume def
> So how
> do you tell:
> (1) z/VM - bring up TCPIP with this alternate networking
> information, and
I think also that VM TCPIP is smart enough to look at the system ID and
execute a specific profile based on the system id. So, if your normal
systemID is FOO1, if you have entries in SYSTEM NETID
Did you run mkinitrd and zipl afterwards?
Mark Wiggins
University of Connecticut
Operating Systems Programmer
860-486-2792
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Kenneth Libutti
Sent: Friday, September 02, 2005 1:11 PM
To: LINUX-390@VM.MARIST.E
Did you run mkinitrd? If not, you may want to manually scan and mount
your new stuff and then run mkinitrd when everything looks good. You
really should report this to SuSE as yast should at least give you a
warning or an opportunity to run mkinitrd following a change/addition to
LVM. This is perha
This is a SLES9 sp2 on z/vm. We have created two lvm groups and then
our required mount points. We then successfully mount the new slices.
When we reboot the second LVM is not seen nor mounted. This is all done
through yast.
--
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On
> Behalf Of Michael MacIsaac
> Sent: Friday, September 02, 2005 11:05 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: How to do a planned DR test?
>
>
> Hello list,
>
> Has anyone addressed the issue of how to do a
> I can see how you can address (1) - maintain a second TCPIP
> service machine - say TCPIP2. Bring up z/VM without AUTOLOG
> and manually bring up TCPIP2. But how to address (2)? Is
> anyone doing this?
1) Ensure the VM install has a unique MACPREFIX in SYSTEM CONFIG.
2) Ensure that each NICDEF
We do not have the luxury of using the production IP addresses in the event of
a disaster. We will have to use whatever addresses our DR vendor provides just
like during a test. The DNS entries will have to be changed for a real
disaster, but for testing, we have the testers use the test IP address
On 9/2/05, Carsten Otte <[EMAIL PROTECTED]> wrote:
> This is the right soloution. Also, to make this change
> permanent, modify your parmfile to mark the disk read-
> only like this:
> ... dasd=1234,5678(ro),...
> You need to re-run zipl and reboot to make the change
> effective. Afterwards, the c
Hello list,
Has anyone addressed the issue of how to do a planned DR test? Here are
the assumptions:
-) There is a production z/VM+Linux LPAR at the primary data center.
-) There is a DR site where the production LPAR volumes, etc. are
replicated.
-) A planned DR test is necessary.
In a real dis
Rob van der Heij wrote:
> But with Linux on z/VM we could in theory provide the same amount of
> CPU cycles in any number of logical CPU's. I could imagine CP to put
> the machine in reduced service and dispatch only the virtual CPU that
> has a new PSW that identifies kernel mode work. But to keep
Ifurung, [EMAIL PROTECTED] wrote:
> Try this, before you do your mount:
>
> echo 1 > /sys/bus/ccw/devices/0.0.1200/readonly
>
> (example where 1200 is your mdisk addr)
This is the right soloution. Also, to make this change
permanent, modify your parmfile to mark the disk read-
only like this:
... d
15 matches
Mail list logo
