runtapes set to 7 INITIAL SCHEDULE (size 94289500): lx /mnt/hde4 pri 1 lev 0 size 69069340 lx /mnt/hdg3 pri 1 lev 0 size 6060890 lx /mnt/hdg2 pri 1 lev 0 size 5286010 lx /mnt/hdg4 pri 1 lev 0 size 5186500 lx /mnt/sdb2 pri 1 lev 0 size 4156550 lx / pri 1 lev 0 size 1962280 lx /mnt/sdb4 pri 1 lev 0 size 1810290 lx /mnt/sda2 pri 1 lev 0 size 737320
DELAYING DUMPS IF NEEDED, total_size 94289500, tape length 215040000 mark 2000 delay: Total size now 94289500. "John R. Jackson" wrote: > > >Hummm, DLT tape set to 30000mb ( 20000 + .5 compression ) > >partition on /mnt/hde4 is 69578056k ( via df ) /mnt/hde4 'sendsizes' to > >70727004160 ( 66GB, 4.6MB/s ) > >... > >i guess i should ask why I didnt get any of these errors? > > Don't know without more information. > > Take a look at the amdump.<NN> file for the "got result for host" lines > to make sure what planner was working with. > > Then look for the "DELAYING DUMPS IF NEEDED" line, e.g.: > > DELAYING DUMPS IF NEEDED, total_size 33616007, tape length 55296000 mark 2000 > > This says the total estimated size was 33616007 KBytes, the tape length > (including the runtapes multiplier) is 55296000 KBytes and a tape mark > (space between each image) is 2000 KBytes. > > What is your runtapes set to? > > >If it hits EOT, then didnt sendsize & friends miscalculat? > > Not necessarily. If someone touch's a 30 GByte file that the estimate > skipped over because it looked idle at that time, the dump will have to > do it and that would throw everything out of whack. > > >And is there any consideration on fitting a large partition onto one or > >more tapes? > > Definitely. All it takes is a few weeks of dedicated programming time > by someone and a whole lot of testing. > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
