On Jun 19 Joshua Baker-LePain wrote:
On Mon, 19 Jun 2006 at 3:28pm, Matt Bernstein wrote
Please can the default maxima be increased for the tape, to whatever this
list thinks is wise?
Patches welcome. In the meantime, re-compiling is dead easy. ISTR that there
*is* an effort (or at least a desire) to move away from configure-time
configuration, but there's also a lot of intertia. :)
Is it this trivial?
diff -ur amanda-2.5.1b1-20060619/configure amanda-patched/configure
--- amanda-2.5.1b1-20060619/configure 2006-06-19 19:36:58.000000000 +0100
+++ amanda-patched/configure 2006-06-20 12:36:40.000000000 +0100
@@ -5543,7 +5543,7 @@
MAXTAPEBLOCKSIZE="$withval"
else
- : ${MAXTAPEBLOCKSIZE=32}
+ : ${MAXTAPEBLOCKSIZE=2048}
fi;
diff -ur amanda-2.5.1b1-20060619/configure.in amanda-patched/configure.in
--- amanda-2.5.1b1-20060619/configure.in 2006-06-19 19:36:37.000000000
+0100
+++ amanda-patched/configure.in 2006-06-20 12:35:23.000000000 +0100
@@ -1256,7 +1256,7 @@
[
MAXTAPEBLOCKSIZE="$withval"
],
- : ${MAXTAPEBLOCKSIZE=32}
+ : ${MAXTAPEBLOCKSIZE=2048}
)
AC_DEFINE_UNQUOTED(MAX_TAPE_BLOCK_KB,($MAXTAPEBLOCKSIZE),[Maximum size of a
tape block in KBytes.])
Please can it be possible to specify custom arguments to dump and its
friends?
Currently possible with some clever scripting, and on the TODO list for the
dumper API (or whatever it's called these days).
So if I nobble the dump packages on the amanda clients to default to 64k
(or more) block size, apply the above patch to the amanda SRPM and
configure a 2048k tape block size for my nice LTO3, will all my bits still
be backed up?
If I accidentally add a new client with a 10k block size, would it still
be true?
Sorry if I'm being dense
Matt
|