On Friday 21 July 2006 17:55, Jon LaBadie wrote:
>
> I suspect it considers it "invalid" as it is not the start of
> the DLE's souce directory.  Have you gone further and tried
> to do recoveries after this type of message?
>
> I don't see that message, or react to it the same way, because
> I generally am recovering to somewhere totally different than
> the thing which was dumped, like /tmp/recover.  Then is complains
> that no DLE corresponds to /tmp/recover and I have to set all
> those "set{disk|date|tape|...} things manually (including the
> recovery destination by doing an "lcd" if I forgot to cd to the
> correct place before running amrecover.

Actually, I much prefer to restore to /Backup/recover - well out of the way of 
original files.  In fact, after reading your message I have managed to do 
exactly that.  It's this 'relative addressing', I suppose, that I hadn't 
quite understood.

This time I changed directory to /Backup/recover and launched amrecover from 
there.  I then had to setdisk, but then everything was absolutely 
straightforward.

Thanks to all for the patience.

Anne

pgpXPKJFckQJM.pgp
Description: PGP signature