Re: amlabel: not an amanda tape ???

2007-08-01 Thread Stefan G. Weichinger 
Michael D Schleif schrieb:
 Please, ANY ideas ???
 
 
 amanda is version 2.5.1p1-2.1 , running on debian:
 
 # uname -a
 Linux erda 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 
 GNU/Linux
 
 Trying to setup a VXA-2 manual load tape drive with amanda.
 
 Same tape that I used earlier today with amtapetype, and successfully
 got a tapetype definition.
 
 Now, I want to label this same tape, and perform the first backup.
 
 # sudo -u backup amlabel -f DailySet1 backup.001
 rewinding, reading label, not an amanda tape (Invalid argument)
 rewinding, writing label backup.001, checking label
 amlabel: not an amanda tape (Invalid argument)
 
 
 What do you think?

(I thought: Should I reply or not? ;-) )

What's the definition of labelstr in your amanda.conf?
Your label does not fit that definition.

Stefan

Re: amlabel: not an amanda tape ???

2007-08-01 Thread Paul Bijnens 

On 2007-08-01 14:08, Michael D Schleif wrote:

Please, ANY ideas ???


amanda is version 2.5.1p1-2.1 , running on debian:

# uname -a
Linux erda 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 GNU/Linux

Trying to setup a VXA-2 manual load tape drive with amanda.

Same tape that I used earlier today with amtapetype, and successfully
got a tapetype definition.

Now, I want to label this same tape, and perform the first backup.

# sudo -u backup amlabel -f DailySet1 backup.001
rewinding, reading label, not an amanda tape (Invalid argument)
rewinding, writing label backup.001, checking label
amlabel: not an amanda tape (Invalid argument)


What do you think?



Seems that, when reading something from the tape
some syscall used returns Invalid argument.

Pure guesses:

- Is your tapedevice in the amanda.conf set to a real device?

- Did you modify the config paramater --with-maxtapeblocksize=... from
something other than the default value 32, which results in some
weird or invalid bufferlength for such a device?  (Also when using
fixed blocks in the tapedevice, Amanda's buffer should be at least as
large as those fixed blocks; I prefer variable blocks for tapes.)


--
Paul Bijnens, xplanation Technology ServicesTel  +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, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  Are you sure?  ...   YES   ...   Phew ...   I'm out  *
***

Re: amlabel: not an amanda tape ??? [ SOLVED ]

2007-08-01 Thread Michael D Schleif 

[ [ [ Anybody else seeing this?
  amanda-users@amanda.org:
  204.127.192.17 does not like recipient.
  Remote host said: 550 [PERMFAIL] destination not valid within DNS
  Giving up on 204.127.192.17.  ] ] ]


Eureka!

# sudo mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
  Tape block size 0 bytes. Density code 0x81 (DLT 15GB compressed).
Soft error count since last status=0
General status bits on (4101):
 BOT ONLINE IM_REP_EN

Changed /etc/stinit.def:

manufacturer=EXABYTE model = VXA-2 {
auto-lock
can-bsr
can-partitions
mode1 blocksize=32768 compression=0
}

Now:

# sudo mt -f /dev/nst0 status
SCSI 2 tape drive:
File number=0, block number=1, partition=0.
Tape block size 32768 bytes. Density code 0x81 (DLT 15GB compressed).
Soft error count since last status=0
General status bits on (101):
 ONLINE IM_REP_EN

And:

# sudo -u backup amlabel -f DailySet1 backup.001
rewinding, reading label backup.001, tape is active
rewinding, writing label backup.001, checking label, done.


* Stefan G. Weichinger [EMAIL PROTECTED] [2007:08:01:14:32:04+0200] scribed:
 Michael D Schleif schrieb:
  Please, ANY ideas ???
  
  
  amanda is version 2.5.1p1-2.1 , running on debian:
  
  # uname -a
  Linux erda 2.6.18-4-amd64 #1 SMP Mon Mar 26 11:36:53 CEST 2007 x86_64 
  GNU/Linux
  
  Trying to setup a VXA-2 manual load tape drive with amanda.
  
  Same tape that I used earlier today with amtapetype, and successfully
  got a tapetype definition.
  
  Now, I want to label this same tape, and perform the first backup.
  
  # sudo -u backup amlabel -f DailySet1 backup.001
  rewinding, reading label, not an amanda tape (Invalid argument)
  rewinding, writing label backup.001, checking label
  amlabel: not an amanda tape (Invalid argument)
  
  
  What do you think?
 
 (I thought: Should I reply or not? ;-) )
 
 What's the definition of labelstr in your amanda.conf?
 Your label does not fit that definition.
 
 Stefan
 

-- 
Best Regards,

mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know.  The more I know, the more I know I don't know . . .
--


signature.asc
Description: Digital signature