|
amrecover won't set correct disk based on CWD
2003-04-08 09:41:36
I've mentioned this on the list before, but as no conclusion came out of
the discussion I've tried again:
amrecover (Amanda 2.4.3) will in my setup often make a wrong guess about
the disk/DLE for the current directory. The following output illustrates
the problem quite well:
# cd /usr/local
# amrecover ks
AMRECOVER Version 2.4.3. Contacting server on localhost ...
220 praha AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-04-08)
200 Working date set to 2003-04-08.
200 Config set to ks.
[ ... ]
Trying host fileserv ...
200 Dump host set to fileserv.
Trying disk /u ...
$CWD '/usr/local' is on disk '/u' mounted at '/u'.
200 Disk set to /u.
Invalid directory - /usr/local
The problem is that the current directory (/usr/local) isn't really on
disk /u; in fact there is a separate (GNUTAR based) DLE for it. The
disklist has:
fileserv /u full-tar
[ ... ]
fileserv /usr/local full-tar
What is going on here? Is this possibly caused by a bug? It may seem like
amindexd will return the shortest or first DLE match when it should in
fact look for the longest one. Or maybe amrecover will only look for
directories that are mount points? The amrecover log may actually suggest
this. Note that /u is a separate partition, while /usr/local is part of /.
amrecover log has been attached. The amindexd one merely contains the
messages indicated above.
--
- Toralf
amrecover.20030408140121.debug
Description: Text document
|
| <Prev in Thread] |
Current Thread |
[Next in Thread>
|
- amrecover won't set correct disk based on CWD,
Toralf Lund <=
|
|
|
