Re: Restoring file from MKSYSB (summary)

From: Bill Verzal (BVerzal@KOMATSUNA.COM)
Date: Thu Apr 29 2004 - 14:39:22 EDT


I have a mksysb.sh script I run that changes the block size to 0 during the
mksysb, then returns it to its previous value after it is done. It is
specifically to eliminate this type of problem. Actually, all of by backup
jobs set the block_size to 0 before they do anything.

BV
--------------------------------------------------------

"If everything is coming your way, then you are in the wrong lane"

Bill Verzal
AIX Administrator, Komatsu America
(847) 970-3726 - direct
(847) 970-4184 - fax

             Holger.VanKoll@SW
             ISSCOM.COM
             Sent by: IBM AIX To
             Discussion List aix-l@Princeton.EDU
             <aix-l@Princeton. cc
             EDU>
                                                                   Subject
                                       Re: Restoring file from MKSYSB
             04/29/2004 01:09 (summary)
             PM

             Please respond to
                  IBM AIX
              Discussion List
             <aix-l@Princeton.
                   EDU>

I never changed block_size , never had problems.
But doing mksysb is not very fast.

Where can I read about pros/cons of changing the block_size?

-----Original Message-----
From: IBM AIX Discussion List [mailto:aix-l@Princeton.EDU] On Behalf Of
John Jolet
Sent: Thursday, April 29, 2004 7:52 PM
To: aix-l@Princeton.EDU
Subject: Re: Restoring file from MKSYSB (summary)

hmm, really? I've always specified block size of zero for my
makesysbs. Otherwise it's too slow.

Stamper, Steve wrote:

> Thanks for everyone's feedback. I tried everyone's suggestion (see
> snip below) and still ended up with the same results. I then started
> wondering if I had a bad tape so I did another MKSYSB; same results.
> I changed the block_size between 1024 and 512; same results. I then
> set the block_size to 0 (variable) and TADA!!! This goes against what
> I have learned about MKSYSB tapes so I guess I need to do some
research.
>
> Thanks everyone for your help - Steve
>
> <snip_o_failures>
> # tctl -f /dev/rmt0 rewind
> # tctl -f /dev/rmt0.1 fsf 2
> # restore -Tvf /dev/rmt0.1
> Please mount volume 1 on /dev/rmt0.1.
> Press the Enter key to continue.
>
> restore: 0511-160 Cannot read the backup media
> /dev/rmt0.1: There is an input or output error.
>
> # tctl -f /dev/rmt0 rewind
> # restore -s4 -xvf /dev/rmt0.1 ./etc/motd
> Please mount volume 1 on /dev/rmt0.1.
> Press the Enter key to continue.
>
> restore: 0511-157 Cannot skip tape records.
> #
>
> # tctl -f /dev/rmt0 rewind
> # restore -s3 -xvf /dev/rmt0.1 ./etc/motd
> Please mount volume 1 on /dev/rmt0.1.
> Press the Enter key to continue.
>
> restore: 0511-160 Cannot read the backup media
> /dev/rmt0.1: There is an input or output error.
> #
>
> # tctl -f /dev/rmt0 rewind
> # restore -s2 -xvf /dev/rmt0.1 ./etc/motd
> Please mount volume 1 on /dev/rmt0.1.
> Press the Enter key to continue.
>
> restore: 0511-262 Read an unexpected end of file.
> #
>
> </snip_o_failures>
>



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:52 EDT