amadmin force matches too many disks
I just noticed the following: $ amadmin ks/incr force fileserv /scanner amadmin: fileserv:/scanner/plankart is set to a forced level 0 at next run. amadmin: fileserv:/scanner/golg is set to a forced level 0 at next run. amadmin: fileserv:/scanner is set to a forced level 0 at next run. Why did this happen? Shouldn't only /scanner be forced? (I have separate DLEs for two subdirectories indicated above; these are excluded in the main DLE config.) Amanda version 2.4.4p3. - Toralf
Re: how to automate tape changing
Jukka Salmi [EMAIL PROTECTED] writes: Is it possible to automate the process of loading the needed tapes? (tape changing with amrecover) Yes. I'm using the following tape device setup to do this: amrecover_changer /dev/nrtape amrecover_do_fsf yes amrecover_check_label yes It's amrecover_changer that does the trick; essentially it tells amrecover to use the tape changer or the tape device is set to /dev/nrtape. I'm using this now too; works fine. After each automatically loaded tape amrecover still prompts to continue. Is this expected behaviour? Sven
Re: amadmin force matches too many disks
Toralf Lund wrote: I just noticed the following: $ amadmin ks/incr force fileserv /scanner amadmin: fileserv:/scanner/plankart is set to a forced level 0 at next run. amadmin: fileserv:/scanner/golg is set to a forced level 0 at next run. amadmin: fileserv:/scanner is set to a forced level 0 at next run. Why did this happen? Shouldn't only /scanner be forced? (I have separate DLEs for two subdirectories indicated above; these are excluded in the main DLE config.) That's because the arguments are interpreted as globs: From man amanda (unfortunatly not a word about this in man amadmin) HOST DISK EXPRESSION All host and disk arguments to programs are special expression. The command apply to all disk that match your arguments. This section describe the matcher. The matcher match by word, each word is a glob expression, word are separated by the separator '.' for host and '/' for disk. You can anchor the expression at left with a '^'. You can anchor the expression at right with a '$'. The matcher is case insensitive for host but is case sen- sitive for disk. A match succeed if all word in your expression match contiguous word in the host or disk. [...snip...] Some examples: EXPRESSION WILL MATCH WILL NOT MATCH hosta hosta hostb hoSTA.dOMAIna.ORG foo.hosta.org [...snip...] /usr/usr /usr/opt /usr$ /usr/usr/opt Suprising he... -- 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: how to automate tape changing
Sven Rudolph wrote: Jukka Salmi [EMAIL PROTECTED] writes: Is it possible to automate the process of loading the needed tapes? Yes. I'm using the following tape device setup to do this: amrecover_changer /dev/nrtape amrecover_do_fsf yes amrecover_check_label yes It's amrecover_changer that does the trick; essentially it tells amrecover to use the tape changer or the tape device is set to /dev/nrtape. I'm using this now too; works fine. After each automatically loaded tape amrecover still prompts to continue. Is this expected behaviour? Unfortunately yes. I had a look in the sources, and currently there is not (yet?) a way for the server to indicate that the tape is found already, and that the client question to proceed? [Y/n] can be skipped. And it's not added with a few lines of code either. -- 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: amadmin force matches too many disks
Paul Bijnens wrote: Toralf Lund wrote: I just noticed the following: $ amadmin ks/incr force fileserv /scanner amadmin: fileserv:/scanner/plankart is set to a forced level 0 at next run. amadmin: fileserv:/scanner/golg is set to a forced level 0 at next run. amadmin: fileserv:/scanner is set to a forced level 0 at next run. Why did this happen? Shouldn't only /scanner be forced? (I have separate DLEs for two subdirectories indicated above; these are excluded in the main DLE config.) That's because the arguments are interpreted as globs: From man amanda (unfortunatly not a word about this in man amadmin) HOST DISK EXPRESSION All host and disk arguments to programs are special expression. The command apply to all disk that match your arguments. This section describe the matcher. The matcher match by word, each word is a glob expression, word are separated by the separator '.' for host and '/' for disk. You can anchor the expression at left with a '^'. You can anchor the expression at right with a '$'. The matcher is case insensitive for host but is case sen- sitive for disk. A match succeed if all word in your expression match contiguous word in the host or disk. Ah. Right. That's of course the way I thought it looked like it worked, more or less, but since the amdump manual page mentioned nothing about it... In I didn't think to try '$' right away... Has it always been that way? I never really noticed it earlier, but I don't use the force that often... - Toralf
smbclient and amandapass problem
Hi! I'm new in the list! I'm experiencing some dificulties with amanda and smb shares: in the file /etc/amanda/DailySet1/disklist, I have: backup//apolo/ARGOS nocomp-user-gnutar backup //homero/D$/Netscape nocomp-user-gnutar and in the file /etc/amandapass I have: //apolo/ARGOS [EMAIL PROTECTED] MYWORKGROUP //homero/D$/Netscape [EMAIL PROTECTED] MYWORKGROUP but when I run /usr/sbin/amcheck DailySet1, I got the follow error: [EMAIL PROTECTED]:~$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - Holding disk /usr/local/amanda/dumps: 11480512 KB disk space available, that's plenty Holding disk /var/backups/amanda/dumps: 9209888 KB disk space available, that's plenty amcheck-server: slot 4: date 20041019 label DailySet104 (exact label match) NOTE: skipping tape-writable test Tape DailySet104 label ok NOTE: info dir /var/lib/amanda/DailySet1/curinfo/backup/__homero_D$_Netscape: does not exist Server check took 0.313 seconds Amanda Backup Client Hosts Check ERROR: backup: [cannot find password for //homero/D$/Netscape] Client check: 1 host checked in 26.793 seconds, 1 problem found (brought to you by Amanda 2.4.4p3) amanda can find the password for //apolo/ARGOS but not for //homero/D$/Netscape. I tried with //homero/D$ and then amanda can find the password :-( I can't find what's wrong with this :-(. I hope someone can help me here :-) PS: I'm using amanda on a Debian GNU/Linux (testing / sarge) Thanks in advance. -- Julián
Re: Unexpected 'gzip --best' processes
On Thu, 21 Oct 2004 at 6:19pm, Toralf Lund wrote This may be related to our backup problems described earlier: I just noticed that during a dump running just now, I have # ps -f -C gzip UIDPID PPID C STIME TTY TIME CMD amanda3064 769 0 17:18 pts/500:00:00 /bin/gzip --best amanda3129 773 0 17:44 pts/500:00:00 /bin/gzip --best *snip* Any ideas why I get these processes? That's the indexes (indices?) getting compressed. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Error with sense data: Info fld=0x40, Current st0: sense key Medium Error
--- Paul Bijnens [EMAIL PROTECTED] wrote: Ping Wing wrote: lcpci says: :00:0a.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U now I cannot find any driver for linux from adaptec site. Under http://www.adaptec.com/worldwide/support/suppbyproduct.jsp?sess=nolanguage=English+UScat=%2FTechnology%2FSCSI+Host+AdaptersfromPage=driverindex I looked for AHA-2940 , AHA-2940UW , AHA-2940UW PRO , AHA-2940W but theres nothing for linux.. For linux this is a standard kernel module. Try as root: modprobe aic7xxx (Of course, you need the complete scsi support too.) yes, I have tried with both 2.6.7 and 2.4.27 kernels, and yes theres is aic7xxx module. Its just that someone told that this is problem with module and that I should get new one from adaptec site... __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
