RE: [flexbackup-help] TOC missing

[Luis C. <in...@co...>]

Results:


flexbackup version 1.0.2 (http://flexbackup.sourceforge.net)
/etc/flexbackup.conf syntax OK

|------------------------------------------------------------
| Checking 'buffer' on this machine... Ok
| Checking /bin/sh on this machine... bash2
|------------------------------------------------------------
| Trying "mt defblksize" instead of "mt setblk"
| Testing will *erase* the tape currently in the drive!
| Hit CTRL-C to abort within 10 seconds...
|------------------------------------------------------------
| If for some reason this program does not exit within a few minutes,  
|Hit CTRL-C, and try adjusting $blksize, $pad_blocks, or 
|$mt_var_blksize.
|------------------------------------------------------------
| Rewinding & erasing tape...
| Creating index key 200302202305
|------------------------------------------------------------
At block 771771535.

Writing test file #1
At block 771771535.

Writing test file #2
At block 771771535.

Rewinding...
Skipping index label...
At block 771771535.

Reading test file #1
At block 771771535.

Reading test file #2
At block 771771535.

Comparing...
SUCCESS! Tape drive parameters seem to work just fine

NOTE: The only strange thing is not all output of the tests go to
standard out.  

Thanks for any help ahead of time,
Luis.



-----Original Message-----
From: John Reynolds [mailto:jo...@re...] 
Sent: Thursday, February 20, 2003 10:37 PM
To: Luis Cortes
Subject: Re: [flexbackup-help] TOC missing



[ On Thursday, February 20, Luis Cortes wrote: ]
> Hello,
> 
> I am having trouble with my TOC. Every time I create a new tape, it 
> has the toc, then I do a backup and it gets erased.  is this normal?  
> Is there a right way to do this?
> 
> I have included my flexbackup config, maybe someone out might have a 
> clue (or give me one ;-) )?

well, it looks like you're using version 1.0.2. With that comes a new
test procedure. run flexbackup with the flag -test-tape-drive and see
what that tells you.

What you describe is not normal. Maybe your driver isn't setup to deal
with filemarks properly or something. Using -test-tape-drive will
hopefully ferrit out the problem. IFF -test-tape-drive comes back and
says things are working, then post that information too.

Other debugging: turn indexes off temporarily in your config. Then do
some backups to tape so that there is at least 2 files on the tape. Then
see if you can manually seek to the last file and "extract" it. That
might also detect a filemark problem with your tapedrive/driver.

-Jr

-- 
John & Jennifer Reynolds  jo...@re...
http://www.reynoldsnet.org/
Sr. Component Design Engineer, ICG, Intel Corp.
jre...@se...
Running FreeBSD since 2.1.5-RELEASE.               FreeBSD: The Power to
Serve!
"Unix is user friendly, it's just particular about the friends it
chooses."