Re: Can't determine disk and mount point from $CWD...
On Thu, 30 Nov 2006 at 6:23am, Gene Heskett wrote I tried with the FQDN and it works now I have another message like the one below. Since I am trying to to use a FILE-DRIVER to simulate tape behaviour I have 15 pseudo-tapes. However,I didn't define any disk type in amanda.conf; do you think that might be a problem? If it is, what should I define as a tape "type" for these pseudo-tapes? amrecover test AMRECOVER Version 2.4.4p1. Contacting server on localhost ... 220 amandatux AMANDA index server (2.4.4p1) ready. 200 Access OK Setting restore date to today (2004-04-21) 200 Working date set to 2004-04-21. 200 Config set to test. 200 Dump host set to amandatux.int-evry.fr. Trying disk / ... Trying disk rootfs ... Can't determine disk and mount point from $CWD '/etc/amanda/test' This is a standard amrecover FAQ. 'man amrecover' and look at the sethost and setdisk commands. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Can't determine disk and mount point from $CWD...
On Wednesday 21 April 2004 09:09, nejat onay erkose wrote: To me privately, but I do not know the exact answer so I'm posting it back to the list. Please keep it on the list so that the list archive might contain the answer for the next person searching for a solution to the same problem. >Hello Gene, > >I tried with the FQDN and it works now I have another message like the >one below. Since I am trying to to use a FILE-DRIVER to simulate tape >behaviour I have 15 pseudo-tapes. However,I didn't define any disk type >in amanda.conf; do you think that might be a problem? If it is, what >should I define as a tape "type" for these pseudo-tapes? > >amrecover test >AMRECOVER Version 2.4.4p1. Contacting server on localhost ... >220 amandatux AMANDA index server (2.4.4p1) ready. >200 Access OK >Setting restore date to today (2004-04-21) >200 Working date set to 2004-04-21. >200 Config set to test. >200 Dump host set to amandatux.int-evry.fr. >Trying disk / ... >Trying disk rootfs ... >Can't determine disk and mount point from $CWD '/etc/amanda/test' > >Regards, >Thank you! -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: "Can't determine disk and mount point from $CWD..."
On Wednesday 21 April 2004 09:35, nejat onay erkose wrote: >Hello Gene, > Gaack! See my private post, and ignore the diatribe about the list. >I tried with the FQDN and it works now I have another message like > the one below. Since I am trying to to use a FILE-DRIVER to > simulate tape behaviour I have 15 pseudo-tapes. However,I didn't > define any disk type in amanda.conf; do you think that might be a > problem? If it is, what should I define as a tape "type" for these > pseudo-tapes? > >amrecover test >AMRECOVER Version 2.4.4p1. Contacting server on localhost ... >220 amandatux AMANDA index server (2.4.4p1) ready. >200 Access OK >Setting restore date to today (2004-04-21) >200 Working date set to 2004-04-21. >200 Config set to test. >200 Dump host set to amandatux.int-evry.fr. >Trying disk / ... >Trying disk rootfs ... >Can't determine disk and mount point from $CWD '/etc/amanda/test' > >Regards, >Thank you! -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.22% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
"Can't determine disk and mount point from $CWD..."
Hello Gene, I tried with the FQDN and it works now I have another message like the one below. Since I am trying to to use a FILE-DRIVER to simulate tape behaviour I have 15 pseudo-tapes. However,I didn't define any disk type in amanda.conf; do you think that might be a problem? If it is, what should I define as a tape "type" for these pseudo-tapes? amrecover test AMRECOVER Version 2.4.4p1. Contacting server on localhost ... 220 amandatux AMANDA index server (2.4.4p1) ready. 200 Access OK Setting restore date to today (2004-04-21) 200 Working date set to 2004-04-21. 200 Config set to test. 200 Dump host set to amandatux.int-evry.fr. Trying disk / ... Trying disk rootfs ... Can't determine disk and mount point from $CWD '/etc/amanda/test' Regards, Thank you!
Re: Can't determine disk and mount point from $CWD
HI... I feel that me a little fool... sorry, for time that I have made them lose... I exec : #amdump DailySet1 -- and work fine : -- [EMAIL PROTECTED] root]# amrecover DailySet1 AMRECOVER Version 2.4.2p2-tapeio. Contacting server on servidor-backup .. 220 servidor-backup AMANDA index server (2.4.2p2-tapeio) ready. 200 Access OK Setting restore date to today (2004-03-23) 200 Working date set to 2004-03-23. 200 Config set to DailySet1. 200 Dump host set to servidor-backup. Trying disk / ... Trying disk rootfs ... Can't determine disk and mount point from $CWD '/root' amrecover> setdate 2004-03-23 200 Working date set to 2004-03-23. amrecover> sethost nucleo0 200 Dump host set to nucleo0. amrecover> setdisk /home Warning: no log files found for tape DailySet114 written0-00-00 Warning: no log files found for tape DailySet113 written0-00-00 Warning: no log files found for tape DailySet112 written0-00-00 Warning: no log files found for tape DailySet111 written0-00-00 Warning: no log files found for tape DailySet110 written0-00-00 Warning: no log files found for tape DailySet109 written0-00-00 Warning: no log files found for tape DailySet108 written0-00-00 Warning: no log files found for tape DailySet107 written0-00-00 Warning: no log files found for tape DailySet106 written0-00-00 Warning: no log files found for tape DailySet105 written0-00-00 Warning: no log files found for tape DailySet104 written0-00-00 Warning: no log files found for tape DailySet103 written0-00-00 Warning: no log files found for tape DailySet102 written0-00-00 Scanning /var/tmp... 200 Disk set to /home. amrecover> ls< -- 2004-03-23 . 2004-03-23 .amandahosts < -- 2004-03-23 edwin/< -- 2004-03-23 lost found/ < -- amrecover> -- Now, add the cront one line (user = amanda) -- 00 02 * * * /usr/local/sbin/amdump DailySet1 and with this already having to work... you believe? thank's for the attentiont lent... http://www.latinmail.com - La forma más cómoda de enviar y recibir tus e-mails
Re: Can't determine disk and mount point from $CWD
edwin valencia wrote:
ev> No index records for disk for specified date
ev> If date correct, notify system administrator
ev> any idea,suggestion?
[EMAIL PROTECTED] restore]# amadmin DailySet1 disklist
...
disk /home:
...
index YES
...
define dumptype hard-disk-tar {
hard-disk-dump
comment "Back up to hard disk instead of tape - using tar"
program "GNUTAR"
}
Are there any index files? Look in ~amanda/DailySet1/index .
There should be files like "hostname._home.20040322.0.gz".
What is in the files? 'gzip < zome_file.gz | head'.
If the lines start with a large number, then that is a symptom
of a bad version of gtar, probaboy 1.13.
Then you'll have a look that the version of gnutar on that client.
gtar --version
If it is version 1.13 it is not good.
You need 1.13.19 or better yet 1.13.25 (and nothing else currently).
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... "Are you sure?" ... YES ... Phew ... I'm out *
***
Re: Can't determine disk and mount point from $CWD
Hi, edwin valencia, on Dienstag, 23. März 2004 at 17:54 you wrote to amanda-users: ev> HI.. >>> Hi, edwin ev>> No index records for disk for specified date ev>> If date correct, notify system administrator ev>> any idea,suggestion? >>> To use the indexes with amrecover, they have to be there. >>> Check that your dumptypes use the option "index yes". >>> Verify this by: >>> amadmin disklist ev> [EMAIL PROTECTED] restore]# amadmin DailySet1 disklist ev> line 71: ev> host servidor-backup: ev> interface default ev> disk /boot: ev> program "GNUTAR" ev> priority 2 ev> dumpcycle 14 ev> maxdumps 1 ev> strategy STANDARD ev> compress CLIENT FAST ev> comprate 0.50 0.50 ev> auth BSD ev> kencrypt NO ev> holdingdisk NO ev> record YES ev> index YES ev> skip-incr NO ev> skip-full NO Was this BEFORE or AFTER editing? If BEFORE: There is a index-dir where the index-files should go to. Check your amanda.conf for something like indexdir "/usr/adm/amanda/daily/index" See if there are files generated. Check permissions of dir. Check sendbackup.*.debug in your amanda-log-dir (usually something like /tmp/amanda). The generation of the indizes gets logged there. Like in: > sendbackup: time 0.197: started index creator: "/bin/tar -tf - 2>/dev/null | sed -e > 's/^\.//'" > sendbackup: time 75.849: index created successfully > sendbackup: time 75.973: 46:size(|): Total bytes written: 66344960 (63MB, > 855kB/s) -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: Can't determine disk and mount point from $CWD
HI..
>> Hi, edwin
ev> No index records for disk for specified date
ev> If date correct, notify system administrator
ev> any idea,suggestion?
>> To use the indexes with amrecover, they have to be there.
>> Check that your dumptypes use the option "index yes".
>> Verify this by:
>> amadmin disklist
[EMAIL PROTECTED] restore]# amadmin DailySet1 disklist
line 71:
host servidor-backup:
interface default
disk /boot:
program "GNUTAR"
priority 2
dumpcycle 14
maxdumps 1
strategy STANDARD
compress CLIENT FAST
comprate 0.50 0.50
auth BSD
kencrypt NO
holdingdisk NO
record YES
index YES
skip-incr NO
skip-full NO
line 72:
host nucleo0:
interface default
disk /home:
program "DUMP"
priority 2
dumpcycle 14
maxdumps 1
strategy STANDARD
compress CLIENT FAST
comprate 0.50 0.50
auth BSD
kencrypt NO
holdingdisk NO
record YES
index YES
skip-incr NO
skip-full NO
>> and look for the lines containing index.
>> If no, edit dumptypes in amanda.conf to contain "index yes".
--
My amanda.conf in the section globas have :
--
define dumptype global {
comment "Global definitions"
index yes
record yes
}
--
and amanda.conf section tar and dump
--
define dumptype hard-disk-dump {
global
comment "Back up to hard disk instead of tape - using dump"
holdingdisk no
index yes
priority high
}
define dumptype hard-disk-tar {
hard-disk-dump
comment "Back up to hard disk instead of tape - using tar"
program "GNUTAR"
}
thanks for the attention lent...
http://www.latinmail.com - La forma más cómoda de enviar y recibir tus e-mails
Re: Can't determine disk and mount point from $CWD
Hi, edwin, on Dienstag, 23. März 2004 at 16:49 you wrote to amanda-users: ev> No index records for disk for specified date ev> If date correct, notify system administrator ev> any idea,suggestion? To use the indexes with amrecover, they have to be there. Check that your dumptypes use the option "index yes". Verify this by: amadmin disklist and look for the lines containing index. If no, edit dumptypes in amanda.conf to contain "index yes". -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: Can't determine disk and mount point from $CWD
HI... ev> -- ev> That is the message. How can I solve this problem? ev> -- >> It is no problem: >> Just say "disklist" on the amrecover-prompt, and after choosing the >> disk you would like to recover, do a "setdisk". Ok... thanks for the explanation. I saw this in one of the web pages that find... I can't exec the "disklist" amrecover> disklist Invalid command - syntax error I can't see my copies (the amanda don't work fine and I know why?) when run : amrecover> sethost nucleo0 200 Dump host set to nucleo0. amrecover> setdisk /home Warning: no log files found for tape DailySet114 written0-00-00 ... Warning: no log files found for tape DailySet101 written0-00-00 Scanning /var/tmp... 200 Disk set to /home. No index records for disk for specified date If date correct, notify system administrator any idea,suggestion? PD : sorry, for my english is very basic and poor PD2 : sorry, for send reply a your email persona,l I am wrong :'( http://www.latinmail.com - La forma más cómoda de enviar y recibir tus e-mails
Re: Can't determine disk and mount point from $CWD
On Tue, Mar 23, 2004 at 08:48:48AM -0500, edwin valencia wrote: > HI... > > I want to know how to fix this error message. > > > [EMAIL PROTECTED] restore]# amrecover DailySet1 > AMRECOVER Version 2.4.2p2-tapeio. Contacting server on servidor-backup .. > 220 servidor-backup AMANDA index server (2.4.2p2-tapeio) ready. > 200 Access OK > Setting restore date to today (2004-03-23) > 200 Working date set to 2004-03-23. > 200 Config set to DailySet1. > 200 Dump host set to servidor-backup. > Trying disk / ... > Trying disk rootfs ... > Can't determine disk and mount point from $CWD '/tmp/restore' > amrecover> It is not an error, it is informational only. amrecover needs to know which disklist entry you want to recover. You can tell it after amrecover starts with various set... commands. You can tell it before amrecover starts with command line options. And amrecover tries to "guess" based on what directory is current whey you enter amrecover. If it matches one of the disklist entries then it sets the host and directory to those values. If the current directory ($CWD) does not match any disklist entry, amrecover tells you that (can't determine ...). -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Can't determine disk and mount point from $CWD
Hi, edwin, on Dienstag, 23. März 2004 at 14:48 you wrote to amanda-users: ev> I also believe that my amanda has something missing because ev> when I exec the following comand : ev> [EMAIL PROTECTED] restore]# amrecover DailySet1 ev> AMRECOVER Version 2.4.2p2-tapeio. Contacting server on servidor-backup .. ev> 220 servidor-backup AMANDA index server (2.4.2p2-tapeio) ready. ev> 200 Access OK ev> Setting restore date to today (2004-03-23) ev> 200 Working date set to 2004-03-23. ev> 200 Config set to DailySet1. ev> 200 Dump host set to servidor-backup. ev> Trying disk / ... ev> Trying disk rootfs ... ev> Can't determine disk and mount point from $CWD '/tmp/restore' amrecover>> ev> -- ev> That is the message. How can I solve this problem? ev> -- It is no problem: Just say "disklist" on the amrecover-prompt, and after choosing the disk you would like to recover, do a "setdisk". Saying "help" there helps, too ;) The message you get just indicates that amrecover could not find your $CWD on your backups, to say it simplified. Recovering stuff into tmp-dirs is a GOOD thing, stay with it. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Can't determine disk and mount point from $CWD
HI... I want to know how to fix this error message. I ran the amrecovet as root; like FAQ page says-- > http://amanda.sourceforge.net/fom-serve/cache/191.html I also believe that my amanda has something missing because when I exec the following comand : [EMAIL PROTECTED] restore]# su amanda bash-2.05a$ amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /var/tmp: 10939228 KB disk space available, that's plenty amcheck-server: slot 1: date Xlabel DailySet101 (exact label match) NOTE: skipping tape-writable test Tape DailySet101 label ok Server check took 0.960 seconds Amanda Backup Client Hosts Check Client check: 2 hosts checked in 0.269 seconds, 0 problems found (brought to you by Amanda 2.4.2p2-tapeio) -- until here works fine! or it seems to be -- [EMAIL PROTECTED] restore]# amrecover DailySet1 AMRECOVER Version 2.4.2p2-tapeio. Contacting server on servidor-backup .. 220 servidor-backup AMANDA index server (2.4.2p2-tapeio) ready. 200 Access OK Setting restore date to today (2004-03-23) 200 Working date set to 2004-03-23. 200 Config set to DailySet1. 200 Dump host set to servidor-backup. Trying disk / ... Trying disk rootfs ... Can't determine disk and mount point from $CWD '/tmp/restore' amrecover> -- That is the message. How can I solve this problem? -- -- just in case bash-2.05a$ df -h FilesystemSize Used Avail Use% Mounted on /dev/sda3 12G 1.1G 10G 9% / /dev/sda1 98M 14M 79M 15% /boot none 62M 0 61M 0% /dev/shm bash-2.05a$ -- thank's for the attentiont lent http://www.latinmail.com - La forma más cómoda de enviar y recibir tus e-mails
Re: "Can't determine disk and mount point from $CWD"
On Thu, 31 Oct 2002 at 2:27pm, [EMAIL PROTECTED] wrote > Hi. I'm trying to run amrecover but I get this message up above the > amrecover prompt:- > "Can't determine disk and mount point from $CWD" [jlb@chaos jlb]$ man amrecover . . . setdisk diskname [ mountpoint ] Specifies which disk to consider (default: the disk holding the working directory where amrecover is started). It can only be set after the host is set with sethost. Diskname is the device name speci fied in the amanda.conf or disklist configuration file. The disk must be local to the host. If mountpoint is not specified, all pathnames will be relative to the (unknown) mount point instead of full pathnames. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
"Can't determine disk and mount point from $CWD"
Hi. I'm trying to run amrecover but I get this message up above the amrecover prompt:- "Can't determine disk and mount point from $CWD" everything else up to this point looks ok:- #amrecover Bacup AMRECOVER Version 2.4.2p2. Contacting server on Neli ... 220 Neli AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-10-31) 200 Working date set to 2002-10-31. 200 Config set to Bacup. 200 Dump host set to Neli. Can't determine disk and mount point from $CWD amrecover> I have no idea how to solve this! Any help or advice would be greatly appreciated. Thank you
