S.Krumme AT stadt-duisburg DOT de wrote:

after moving my backup hard- and software to another machine, I encountered several problems. One was due to faulty tapes, the other due to the fact that I didn´t knew the blocksize I set the tape device on the old machine. These problems I had resolved by using fresh tapes and by setting the default block size of the tape device to 32, which was the original setting.

blocksize of 32 bytes?  Or do you mean 32 Kbytes?

Now my backup is up an running again. But when I start amdump, the filesystems are dumped quickly as usual, but when the taper starts writing it takes extremly long.

Here is an example:

10.0.1.5:/                    1    55424k writing to tape (12:20:40)

Now its 13:42 and it is still writing.

Any idea whats wrong now ?

If the blocksize if 32 bytes, then, yes, that is incredebly slow.

Personally, I prefer the variable block tape device (by setting default
blocksize to zero), and specify the blocksize I need using the programs
(32Kbyte by default for amanda, or "dd bs=..." etc.)



--
Paul Bijnens, Xplanation                            Tel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  +32 16 397.512
http://www.xplanation.com/          email:  Paul.Bijnens AT xplanation DOT com
***********************************************************************
* 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          *
***********************************************************************