On Wed, 28 Apr 1999, Jean-Michel Lacroix wrote:
> Try without the "v" on your tar command (tar df /dev/nqft0): I found on a
> previous system (486-66 with an old hercules TTL card) that "v" on the tar
> command what slowing down the system too much since it was writting one
> line per file on the screen: then the tape had to stop (I guess the system
> was not able to feed the tape fast enough), rewind a little bit and start
> again, make an entry in /var/adm/messages, this was slowing the system even
> more, creating an other error that was written again to the
> /var/adm/messages, slowing down the system again..... You get the picture!
Thanks for the tip. Someone else suggested ftformat in
ftape-tool, so I ran that on the tape. The command that it gave was
ftformat -f /dev/nrawft0 --mode=auto --verify-only . I ran this
overnight, and found errors in the morning. In the message window in
ftape-tool was:
Verifying track 18
Verifying track 19
Ioctl error sending enter primary mode command: Device or resource busy
and "Unable to close ftformat pipe" was in my root console window. I just
checked /var/log/messages for the time the backup was running, and there
were alot of write errors listed. Here's a small example:
Apr 27 02:42:27 sunlink kernel: [052] 0 ftape-write.c (write_segment)
- hard
error in segment 3249.
Apr 27 02:42:28 sunlink kernel: [053] 0 ftape-write.c
(ftape_write_segment) -
write_segment failed, error: -5.
Apr 27 02:42:28 sunlink kernel: [054] 0 zftape-write.c
(zftape_write_segment)
- Hard error writing segment, trying to recover.
Given all this, I think it's a bad tape. Will reformating help,
or is it completely toasted?
Hrmm, I think verify is what I was looking for as a tar option,
not compare. How would I run this on a previously-recorded archive
without listing every single file in the archive? tar tWf is spammy.
Suggestions? Thanks.
Jamie
Egg, [EMAIL PROTECTED]
FMS3amr A- C- H+ M+ P+++ R+ T Z+ Sp#
RL->CT a cu++ e++ f h+ iw+ j p- sm#
