>I tried what you suggested and this is what I got:
>bash-2.02$ mt -f /dev/rst0 rewind
>bash-2.02$ dd if=/dev/rst0 bs=32k
>0+0 records in
>0+0 records out
OK, that says the tape is empty. It's as though someone did:
mt -f /dev/nrst0 rewind
mt -f /dev/nrst0 eof
BTW, you should use /dev/nrst
John,
I tried what you suggested and this is what I got:
bash-2.02$ mt -f /dev/rst0 rewind
bash-2.02$ dd if=/dev/rst0 bs=32k
0+0 records in
0+0 records out
0 bytes transferred in 14.688649 secs (0 bytes/sec)
My OS is FreeBSD and I am using DAT DSS2 4Gbytes...
I will be on vacation for two weeks b
>Apparently I confused every one with my explanations.
OK, I get it now.
>The problem occurs when I do put the valid tape in for the next run and
>amcheck is run, it then compains that the inserted tape isn't an amanda tape
>and if I check the first block using dd it does seem like if the tape w
John,
Apparently I confused every one with my explanations.
Of course I run amcheck BEFORE amdump, but that also means that amcheck is
run after the "previous" amdump
And the output of the amcheck on tape DailySet109 was just to prove that the
tape does have a valid label!
The problem occu
>I have this constant recurrant error, that every day the amcheck is
>failing just after a succesfull amdump.
I don't understand. Do you really mean you're running amcheck **after**
you run amdump? Why? Usually it's run **before** amdump so any problems
it finds can be fixed before the run.
>
Hi,
I have this constant recurrant error, that every day the amcheck is
failing just after a succesfull amdump.
I get the following result:
Amanda Tape Server Host Check
-
Holding disk /amanda2/amanda/work: 985384 KB disk space available,
that's plenty
ERROR: /dev/nrs
