|
List Info
Thread: Digest Number 1254
|
|
| Digest Number 1254 |
  United States |
2007-08-28 08:43:53 |
|
Messages In This Digest (1
Message)
Message
- 1.
-
Posted by: "Christopher McCrory" chrismcc pricegrabber.com?Subject= Re%3Awith-maxtapeblocksize%20vs%2E%20%20amfetchdump%7Camrestore">
chrismcc pricegrabber.com
Mon Aug 27, 2007 6:36 pm (PST)
Hello...
I compiled amanda with --with-maxtapeblocksize=512 to speed up my LTO-4
tape drives. amfetchdump breaks with "Cannot allocate memory":
shell> amfetchdump -a ...
The following tapes are needed: 000031L4
amfetchdump: error reading file header: Cannot allocate memory
Not an amanda tape
Looking for tape 000031L4...
amfetchdump: slot 31: date 20070821082505 label 000031L4 (exact label
match)
amfetchdump: error reading file header: Cannot allocate memory
Not an amanda tape
Insert tape labeled 000031L4 in device /dev/nst0
and press enter, ^D to finish reading tapes
in amanda.conf: tapetype I have:
blocksize 256
from "man amfetchdump"
-b blocksize
Force a particular block size when reading from tapes. This value
will usually be autodetected, and should not normally need to be
set.
The autodetect part does not seem to work ( at least for me). To get it
to work, I had to do:
amfetchdump -b 256k -a ...
bug? or by design?
--
Christopher McCrory
"The guy that keeps the servers running"
To the optimist, the glass is half full.
To the pessimist, the glass is half empty.
To the engineer, the glass is twice as big as it needs to be.
chrismcc  pricegrabb er.com?Subject=Re%3Awith-maxtapeblocksize%20vs%2E%20%20amfetchdump%7Camrestore">
Reply to sender
|
amanda-hackers@yahoogroups.com?Subject= Re%3Awith-maxtapeblocksize%20vs%2E%20%20amfetchdump%7Camrestore">
Reply to group
|
Reply via web post
Messages in this topic
(1)
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|