On Thu, Sep 09, 2004 at 03:29:42 +1000, Peter Miller wrote:
> On Thu, 2004-09-09 at 13:15, John Clarke wrote:
> > tar: /dev/st0: Cannot read: Input/output error
>
> This means that there is no Tape Mark on the tape, meaning that the tape
> was probably written using a no-rewind device, and you failed to
Not true, /dev/st0 *is* the rewind device.
> The "fix" is to write the tape properly in the first place. The
> auto-rewind device usually writes two tape marks when you call close().
That's what I thought. Your suggestion has made me have a closer look
at st(4) though, and the two filemark option is disabled by default:
MT_ST_TWO_FM (Default: false)
This option modifies the driver behavior when a file is closed.
The normal action is to write a single filemark. If the option
is true the driver will write two filemarks and backspace over
the second one.
I've just run a quick test with a small amount of data after turning
this option on (mt -f /dev/st0 stoptions two-fms) and it appears to
have fixed the problem -- it failed before I turned on two-fms and
worked after turning it on.
I'll run it again with the same data I was trying earlier, but I expect
it'll work now. Thanks.
And I think my sigmonster's become sentient :-)
Cheers,
John
--
DDS-3 is of course modelled on core memory. The process of reading it to
verify the backup will have wiped it from the tape.
-- Peter Corlett
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
