I wanted to update everyone on our issue. Here is the comment from my team
member who is working the issue.
I've isolated the problem to the disk copy using the dd utility rather than the
mount and update of the cloned root file system as I first thought. I've found
that if I use the 'oflag=
Sent: Thursday, July 26, 2018 10:52 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issue cloning RHEL server
On Thursday, 07/26/2018 at 01:45 GMT, "Feller, Paul"
wrote:
>
I'm thinking along the same lines as Mike.
If this is a synchronous mirror, something seems wrong. Is it reall
, 2018 9:45 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issue cloning RHEL server
Mike, here are the answers to your questions.
Can you post the contents of the clone script? Is it based on the code
starting on p. 528?
>>>> Yes, we're using that one with no modificati
On Thursday, 07/26/2018 at 01:45 GMT, "Feller, Paul"
wrote:
>
I'm thinking along the same lines as Mike.
If this is a synchronous mirror, something seems wrong. Is it really a
synchronous mirror primary? It's sort of acting like an as-yet-unpopulated
flashcopy target, which is inappropria
r
AGT Mainframe Technical Support
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael
MacIsaac
Sent: Thursday, July 26, 2018 9:12 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issue cloning RHEL server
Paul,
I don't want to point fingers,
header/extent in
> inode #5136: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
> EXT4-fs error (device dm-0): __ext4_ext_check_block: bad header/extent in
> inode #5136: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
> /etc/rc.d/rc.sysinit: line 667: 1151 Bus error
>/dev/null
DCVML99 :
EXT4-fs error (device dm-0): __ext4_ext_check_block: bad header/extent in inode
#5136: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
init: rc main process (1158) killed by BUS signal
Thanks..
Paul Feller
AGT Mainframe Technical Support
-Original Message
ey }
# main()
# global variables
sourceID="S11RWMNT" # VM user ID where first Linux was installed
parmType="PARM-S11" # File type of parameter file on 191 disk
# function calls
findID
enableAdisk
findSourceIP
findTargetIP
modifyIP
genSSHkeys
chkconfig boot.findself o
Sent: Wednesday, July 25, 2018 1:19 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Issue cloning RHEL server
Paul,
Can you post the contents of the clone script? Is it based on the code
starting on p. 528?
When you say " corrupts one or more of the copy's file systems", can you be
mo
al variables
sourceID="S11RWMNT" # VM user ID where first Linux was installed
parmType="PARM-S11" # File type of parameter file on 191 disk
# function calls
findID
enableAdisk
findSourceIP
findTargetIP
modifyIP
genSSHkeys
chkconfig boot.findself off # run only once =
Paul,
Can you post the contents of the clone script? Is it based on the code
starting on p. 528?
When you say " corrupts one or more of the copy's file systems", can you
be more specific?
Thanks.
-Mike
On Wed, Jul 25, 2018 at 1:08 PM Feller, Paul
wrote:
> One of my team members is tryi
One of my team members is trying to run the cloning process described in "The
Virtualization Cookbook for z/VM 6.3, RHEL 6.4 and SLES 11 SP3 October 2013,
January 2014 (SG-248147-00)". I believe the process has worked in the past.
But as things go the environment has changed over time.
Here
12 matches
Mail list logo
