>Amanda started returning these results a couple of days ago...
Ummmm, let's be clear here. Amanda is not saying this. Your dump
program is. Amanda is just passing along the good news :-).
>? DUMP: bread: lseek fails
This might be nothing more than an active file system. What happens
is dump reads what it thinks are going to be disk block addresses (e.g.
from an indirect block) and by the time it gets there, that disk block
has been re-assigned to some file for data, so when it tries to seek based
on what it thinks is a disk block, it jumps off into never never land.
As long as the dump goes ahead and completes, I wouldn't worry about it.
Or you could switch to GNU tar (but check the mailing list for the issues
that brings up).
You might also make sure you're up to date on dump version. A lot of good
things have happened to it in the last several months (so I've heard).
>Anything I can check for? Is there anyway I can identify where on the disk
>it's failing, and try removing that file?
You could get the source code for dump and add some better diagnostics
(what you're getting is, shall we say, marginal). That's probably not
too hard -- just some extra print statements.
>Chris Herrmann
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
