All systems are clones of an original, so all device assignments in
Linux are the same across systems. Here is my ZIPL and FSTAB. I cannot
generate the error messages as I had to re-clone the system and get it
back online.
I was receiving errors on different filesystems and I ran FSCK's on
them, then received this abend in the kernel:
I restored the Linux volumes from the backup tapes and it will not come
up all the way. I switched tape sets with the same result. The kernel is
abending.
************************************************************************
****

Unable to handle kernel pointer dereference at virtual kernel address
0c800000

Oops: 0010

CPU:    0    Not tainted

Process find (pid: 497, task: 09804000, ksp: 09805940)

Krnl PSW : 07081000 8d020b96

Krnl GPRS: 09709a80 fffd2348 0c7fff79 ffff6003

           0c5c7570 0000d140 09a3e779 09a34300

           b814a409 00643c03 00000d14 ffff6004

           09a414b0 8d020864 8d020a54 09805c98

Krnl ACRS: 00000000 00000000 00000000 00000000

           00000001 00000000 00000000 00000000

           00000000 00000000 00000000 00000000

           00000000 00000000 00000000 00000000

Krnl Code: d2 ff 40 00 20 00 41 40 41 00 41 20 21 00 a7 16 ff f9 a7 15

Call Trace:

 <1>Unable to handle kernel pointer dereference at virtual kernel
address 180000

00

Oops: 0010

CPU:    0    Not tainted

Process find (pid: 497, task: 09804000, ksp: 09805940)

Krnl PSW : 07082000 800765aa

Krnl GPRS: 00a83f80 00000002 18000000 000000c0
**************************************************************

[EMAIL PROTECTED]:~> cd /etc
[EMAIL PROTECTED]:/etc> cat zipl.conf
# Generated by YaST2
[defaultboot]
default=ipl

[ipl]
target=/boot/zipl
image=/boot/kernel/image
ramdisk=/boot/initrd
parameters="dasd=0201-020f,0300-030f root=/dev/dasda1"

[dumpdasd]
target=/boot/zipl
dumpto=/dev/dasd??

[dumptape]
target=/boot/zipl
dumpto=/dev/rtibm0
[EMAIL PROTECTED]:/etc> cat fstab
/dev/dasda1          /                    reiserfs   defaults
1 1
/dev/dasda2          /tmp                 ext2       defaults
1 2
/dev/dasdb1          /usr                 reiserfs   defaults
1 2
/dev/dasdd1          /var                 reiserfs   defaults
1 2
/dev/dasde1          /home                reiserfs   defaults
1 2
/dev/dasdf1          /user2               reiserfs   defaults
1 2
/dev/dasdc1          swap                 swap       pri=42
0 0
/dev/dasdd2          /opt/IBM             reiserfs   defaults
0 2 
devpts               /dev/pts             devpts     mode=0620,gid=5
0 0
proc                 /proc                proc       defaults
0 0
[EMAIL PROTECTED]:/etc>

Lea Stahr
Sr. System Administrator
Linux/Unix Team
630-753-5445
[EMAIL PROTECTED]
 

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
James Melin
Sent: Tuesday, July 25, 2006 8:43 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Bad Linux backups

I think I might have an idea as to where your problem MAY be - I'm
guessing at this point so I'd like you to fill in some blanks....

Are your Linux guests device number consistent across Linuxen? As in,
/dev/dasdb1 is always device 601 and /{root file system} is 600, etc? Or
is it
on Linux A it's 600,601,602 etc and Linux B it's 400,401,402 etc?  What
does your zipl.conf look like?

Also can you post any messages you get when you try to boot them?





             "Stahr, Lea" <[EMAIL PROTECTED]>
             Sent by: Linux on 390 Port
             <LINUX-390@VM.MARIST.EDU>
To
 
LINUX-390@VM.MARIST.EDU
 
cc
             07/25/2006 07:17 AM
 
Subject
                                                                     Re:
Bad Linux backups
                            Please respond to
               Linux on 390 Port <LINUX-390@VM.MARIST.EDU>








FDR says working as designed. They back up the entire volume and restore
the entire volume. I have restored 3 systems and they DO NOT BOOT.

Lea Stahr
Sr. System Administrator
Linux/Unix Team
630-753-5445
[EMAIL PROTECTED]


-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
John Summerfied
Sent: Monday, July 24, 2006 6:03 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Bad Linux backups

Stahr, Lea wrote:
> I run SuSE SLES 8 under ZVM 5.1 in an IFL. The DASD are in a SAN that
is
> also accessed by ZOS. Backups are taken by ZOS using FDR full volume
> copies on Saturday morning (low usage). When I restore a backup, it
will
> not boot. The backup and the restore have the same byte counts. Linux
> support at MainLine Systems tells me that he has seen this before at
> other customers. What is everyone using for Linux under ZVM backups?
> HELP! My backups are no good!

What do the FDR suppliers say?


--

Cheers
John

-- spambait
[EMAIL PROTECTED]  [EMAIL PROTECTED]
Tourist pics
http://portgeographe.environmentaldisasters.cds.merseine.nu/

do not reply off-list

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to