On Wed, 29 Aug 2001 at 1:57pm, Lorrie Wood wrote
> no problem there. I tried to run amflush, though, and it failed on
> several filesystems. I am guessing it's a failure of the files on the
> holding disk instead of the tape (as the tape does have good data!).
Don't be so sure...
> FAILURE AND STRANGE DUMP SUMMARY:
> bertha /usr2 lev 1 FAILED [input: Can't read data: : Input/output error]
> us /export/home/us0 lev 3 FAILED [input: Can't read data: :
> +Input/output error]
> us /export/home/us1 lev 4 FAILED [input: Can't read data: :
> +Input/output error]
*snip*
> NOTES:
> amflush: /home/amanda/20010829/bertha._usr2.1: taper error, leaving file on disk
> amflush: /home/amanda/20010829/us._export_home_us0.3: taper error, leaving file on
>disk
> amflush: /home/amanda/20010829/us._export_home_us1.4: taper error, leaving file on
>disk
> amflush: Could not rmdir /home/amanda/20010829. Check for cruft.
> taper: tape DailySet159 kb 2292256 fm 5 [OK]
>
taper ran into an "Input/output error" trying to put those disk images
onto tape. In reality, taper is just telling you what the OS told it.
Check your system logs for related messages -- they should tell you what
type of Input/output error occurred.
I've seen old tape drives/tapes/combos thereof which will write random
amounts of data (sometimes a whole night's worth, sometimes not) before
giving such errors.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University