Hi,
Just providing my 2 cents, take it for what it's worth...
For the 7+ years I have been supporting Linux on System z we have a typical set
up of one 3390-9 to contain the SLES installation, one 3390-3 as swap space,
and one virtual disk for swap (the size depends on the nature of the
sles003:~ df -Ht
df: option requires an argument -- 't'
Try 'df --help' for more information.
sles003:~ df -H
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/system-root 5.7G 2.5G 3.0G 46% /
devtmpfs 460M 8.2k 460M 1% /dev
tmpfs467M
On 18 December 2014 at 20:26, Mark Post mp...@suse.com wrote:
On 12/18/2014 at 09:32 AM, Levy, Alan al...@doitt.nyc.gov wrote:
Does it make sense in just setting up one mod 29 (32000+ cylinders, app
21G)
and let the btrfs use the whole thing instead of breaking it up into
smaller
pieces
Hi,
I am having trouble configuring SLES 12 to logoff the z/VM guest when it shuts
down (in some situations). In SLES 11 I updated the parameters in
/etc/zipl.conf and specified 'vmpoff=LOGOFF' and also modified the ctrl-alt-del
line in /etc/inittab from
ca::ctrlaltdel:/sbin/shutdown -r -t 4
On 12/19/2014 at 09:46 AM, Mark Pace pacemainl...@gmail.com wrote:
sles003:~ df -Ht
df: option requires an argument -- 't'
Try 'df --help' for more information.
sles003:~ df -H
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/system-root 5.7G 2.5G 3.0G 46% /
Hi Alan and all,
The EQID on VSWITCH was fixed. When I ran the following:
vmreloc test Lnx004 zvm2
HCPRLH1940E LNX004 is not relocatable for the following reason (s):
Ray,
You should detach the CMS-oriented disks from your Linux guest before booting
the Linux kernel. Your kernel should only have disks attached that Linux will
actually use. Having disks attached/linked that are dedicated to one
particular z/VM image will prevent relocation.
Thanks,
Sam
I'm going back and putting / in a partition of it's own.
And will then try to add the other 3 disks to a btrfs.
So during install I don't see a way to add 3 disks to btrfs without first
creating an LVM volume group. I see no way to run this command, btrfs
device add dev1 dev2 /path/to/filesystem
As part of my linux PROFILE EXEC - if it is going to IPL linux it runs an
exec that detaches all disks that do not belong to that linux guest, in my
case, all R/O disks.
On Fri, Dec 19, 2014 at 1:55 PM, Cohen, Sam sam.co...@lrs.com wrote:
Ray,
You should detach the CMS-oriented disks from
Mark,
I am still a z/VM learner. Based on your comments, my PROFILE LNXDFLT for
TCPMAINT should be changed from
LINK MAINT 0190 0190 RR
LINK MAINT 019D 019D RR
LINK MAINT 019E 019E RR
LINK LNXMAINT 0192 0191 RR
LINK TCPMAINT 0592 0592 RR
To
LINK MAINT 0190 0190 R
LINK MAINT 019D 019D R
LINK
On Friday, 12/19/2014 at 03:35 EST, Chu, Raymond raymond@pseg.com
wrote:
Mark,
I am still a z/VM learner. Based on your comments, my PROFILE LNXDFLT
for
TCPMAINT should be changed from
LINK MAINT 0190 0190 RR
LINK MAINT 019D 019D RR
LINK MAINT 019E 019E RR
LINK LNXMAINT 0192 0191 RR
Here is the exec/pipe that I run to detach all disks link R/O.
/* *
*\
Name:
DETDISK
Version:
1.0
Author: M.
Pace
Function: Detach all disk linked
R/O
Comments: Give Linux fewer disks to look
at.
History:
\*
On 12/17/2014 at 06:07 PM, Mark Post wrote:
On 12/17/2014 at 12:25 PM, Linker Harley - hlinke
harley.lin...@acxiom.com
wrote:
-snip-
This is very frustrating.
Please run the supportconfig utility and send the resulting tarball (in
/var/log/) to me off-list.
The problem turns out
Interestingly, when I brought up the first zLinux image, I needed to add the
LINK TCPMAINT 0592 0592 RR statement to the PROFILE LNXDFLT and all zLinux
images came up. However it caused the issue of LGR. Now I have the statement
removed from the PROFILE, run directxa user command and reIPL all
That's good - you shouldn't need this link anyway unless something in your
PROFILE EXEC is actually using TCPIP commands..but even so - detaching
it before IPLing Linux (along with anything else non-Linux you have linked)
would work as well..
Scott Rohling
On Fri, Dec 19, 2014 at 2:23 PM,
15 matches
Mail list logo
