Re: amlabel (v3.4.3) doesn't write tape line when first creating tapelist file
On Thu, Mar 16, 2017 at 11:46:50 -0400, Jean-Louis Martineau wrote:
> Thanks for reporting the issue.
> I committed the attached patch.
[...]
> diff --git a/perl/Amanda/Tapelist.swg b/perl/Amanda/Tapelist.swg
> index 99f1164..e846eb0 100644
> --- a/perl/Amanda/Tapelist.swg
> +++ b/perl/Amanda/Tapelist.swg
> @@ -309,7 +309,12 @@ sub _read_tapelist {
> $self->{'tle_hash_label'} = undef;
> $self->{'tle_hash_barcode'} = undef;
> my $linenum = 0;
> -open(my $fh, "<", $self->{'filename'}) or return undef;
> +my $fh;
> +if (!open($fh, "<", $self->{'filename'})) {
> + $self->{'tles'} = [];
> + return undef;
> +}
> +
> while (my $line = <$fh>) {
> $linenum++;
> my ($datestamp, $label, $reuse, $barcode, $meta, $blocksize, $pool,
> $storage, $config, $comment)
I manually applied this patch to the system Tapelist.pm file, and can
confirm a newly-created tapelist file is populated correctly:
# rm tapelist
# su backup -c "amlabel TestBackup TESTBACKUP-01 slot 1"
Reading label...
Found an empty tape.
Writing label 'TESTBACKUP-01'...
Checking label...
Success!
# cat tapelist
0 TESTBACKUP-01 reuse BLOCKSIZE:32 POOL:TestBackup STORAGE:TestBackup
CONFIG:TestBackup
Thanks!
Nathan
Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
Re: amlabel (v3.4.3) doesn't write tape line when first creating tapelist file
Nathan,
Thanks for reporting the issue.
I committed the attached patch.
Jean-LouisOn 15/03/17 06:27 PM, Nathan Stratton Treadway wrote:
> Summary: if the "tapelist" file doesn't exist, amlabel creates the file
> but doesn't populate it. (Again, this is using Amanda 3.4.3.)
>
> (In the following examples, I delete the 0.TESTBACKUP-01 file out of
> the vtape slot1 directory before each test run, so the only difference
> is the existence of the "tapelist" file.)
>
> First test: if tapelist doesn't exist beforehand, amlabel creates it,
> but the line for the newly-labled tape isn't written to it:
> =
> # rm tapelist
> # cat tapelist
> cat: tapelist: No such file or directory
>
> # su backup -c "amlabel TestBackup TESTBACKUP-01 slot 1"
> Reading label...
> Found an empty tape.
> Writing label 'TESTBACKUP-01'...
> Checking label...
> Success!
> # cat tapelist
> # ls -l tapelist
> -rw--- 1 backup backup 0 Mar 15 17:58 tapelist
> =
>
> (The label is in fact written to the vtape, so the end result a labeled
> vtape that isn't listed in the tapelist file, as shown if I repeat the
> label command again immediately after the previous run:
> =
> # su backup -c "amlabel TestBackup TESTBACKUP-01 slot 1"
> Reading label...
> Found label 'TESTBACKUP-01' but it is not in the tapelist file.
> Not writing label.
> Not writing label.
> =
> )
>
>
> However, if I create an empty tapelist file first, the tape-line is
> written to the file as expected:
> =
> # rm tapelist
> # cat tapelist
> cat: tapelist: No such file or directory
> # touch tapelist
>
> # su backup -c "amlabel TestBackup TESTBACKUP-01 slot 1"
> Reading label...
> Found an empty tape.
> Writing label 'TESTBACKUP-01'...
> Checking label...
> Success!
> # cat tapelist
> 0 TESTBACKUP-01 reuse BLOCKSIZE:32 POOL:TestBackup STORAGE:TestBackup
> CONFIG:TestBackup
> =
>
> At first glance, the amlabel.20170315*.debug files for the two runs
> appear identical (e.g. both are 33 lines and 449 words long, according
> to "wc"), so I don't believe the log gives any indication that something
> went wrong.
>
> (Jean-Louis,) let me know if the cause of this problem is immediately
> obvious to you or if it would help for me to do some debugging the
> Tapelist.pm code.
>
> Thanks.
>
>
> Nathan
>
>
> Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region
> Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
> GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
> Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
>
This message is the property of CARBONITE, INC. and may contain confidential or
privileged information.
If this message has been delivered to you by mistake, then do not copy or
deliver this message to anyone. Instead, destroy it and notify me by reply
e-mail
diff --git a/perl/Amanda/Tapelist.swg b/perl/Amanda/Tapelist.swg
index 99f1164..e846eb0 100644
--- a/perl/Amanda/Tapelist.swg
+++ b/perl/Amanda/Tapelist.swg
@@ -309,7 +309,12 @@ sub _read_tapelist {
$self->{'tle_hash_label'} = undef;
$self->{'tle_hash_barcode'} = undef;
my $linenum = 0;
-open(my $fh, "<", $self->{'filename'}) or return undef;
+my $fh;
+if (!open($fh, "<", $self->{'filename'})) {
+ $self->{'tles'} = [];
+ return undef;
+}
+
while (my $line = <$fh>) {
$linenum++;
my ($datestamp, $label, $reuse, $barcode, $meta, $blocksize, $pool, $storage, $config, $comment)
Re: amlabel problem
When reporting a problem, can you at least report which version you are
using.
We also need a way to reproduce the issue, the minum it hat case is the
amlabel command line argument and all setting related to the changer.
Bug get fixed a lot faster when enough information to reproduce the
issue is provided.
I committed the attached patch to fix the issue.
Jean-Louis
On 17/10/15 08:39 AM, Kamil Jońca wrote:
I want to add some new virtual tapes, but I got:
--8<---cut here---start->8---
Reading label...
Found an empty tape.
amlabel: Can't use an undefined value as a subroutine reference at
/usr/sbin/amlabel line 120.
--8<---cut here---end--->8---
lines from sbin/amlabel:
--8<---cut here---start->8---
117 if ($res) {
118 $res->release(finished_cb => sub {
119 # ignore error
120 $finished_cb->()
121 });
--8<---cut here---end--->8---
KJ
diff --git a/config/compile b/config/compile
old mode 100644
new mode 100755
diff --git a/config/config.guess b/config/config.guess
old mode 100644
new mode 100755
diff --git a/server-src/amlabel.pl b/server-src/amlabel.pl
index 307af07..b3c8aa4 100644
--- a/server-src/amlabel.pl
+++ b/server-src/amlabel.pl
@@ -255,7 +255,7 @@ sub main {
my ($err, $meta) = @_;
if (defined $meta && defined $opt_meta && $meta ne $opt_meta) {
- return failure();
+ return failure("Device meta '$meta' is not the same as the --meta argument '$opt_meta'", $finished_cb);
}
$meta = $opt_meta if !defined $meta;
($meta, my $merr) = $res->make_new_meta_label() if !defined $meta;
@@ -347,7 +347,7 @@ sub main {
if (defined $meta) {
if (defined($tle->{'meta'}) && $meta ne $tle->{'meta'} &&
!$opt_force) {
- return failure("Can't change meta-label with --force, old meta-label is '$tle->{'meta'}'");
+ return failure("Can't change meta-label with --force, old meta-label is '$tle->{'meta'}'", $finished_cb);
}
} else {
$meta = $tle->{'meta'};
@@ -357,7 +357,7 @@ sub main {
if (defined($tle->{'barcode'}) &&
$barcode ne $tle->{'barcode'} &&
!$opt_force) {
- return failure("Can't change barcode with --force, old barcode is '$tle->{'barcode'}'");
+ return failure("Can't change barcode with --force, old barcode is '$tle->{'barcode'}'", $finished_cb);
}
} else {
$barcode = $tle->{'barcode'};
RE: amlabel segmentation fault
Hi Jean-Louis, Sorry for the delay. I had to remove a binary install and get the source build back up again. But it all works now with your patch. Thanks! Best regards, Kervin Web Services Design, Development and Maintenance http://adevsoft.com/ -Original Message- From: Jean-Louis Martineau [mailto:martin...@zmanda.com] Sent: Friday, January 10, 2014 8:35 AM To: Kervin L. Pierre Cc: amanda-users@amanda.org Subject: Re: amlabel segmentation fault Kervin, Did you try the patch? Jean-Louis On 01/06/2014 09:13 AM, Jean-Louis Martineau wrote: > Kervin, > > Looks like there is a bug if libcurl use GNUTLS. > > Can you try the attached patch? > > Jean-Louis > > On 01/05/2014 12:10 PM, Kervin L. Pierre wrote: >> Hi Jean-Louis, >> >> Thanks for the response. Is there a way to rebuild with '-g' for >> debugging support and to avoid stripping symbols? Would that help? >> >> Here is the gdb output... >> >> $ gdb --args perl /usr/local/sbin/amlabel --version GNU gdb (GDB) >> 7.6.1-ubuntu Copyright (C) 2013 Free Software Foundation, Inc. >> License GPLv3+: GNU GPL version 3 or later >> <http://gnu.org/licenses/gpl.html> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. Type "show >> copying" >> and "show warranty" for details. >> This GDB was configured as "x86_64-linux-gnu". >> For bug reporting instructions, please see: >> <http://www.gnu.org/software/gdb/bugs/>... >> Reading symbols from /usr/bin/perl...(no debugging symbols >> found)...done. >> (gdb) run >> Starting program: /usr/bin/perl /usr/local/sbin/amlabel --version >> [Thread debugging using libthread_db enabled] Using host libthread_db >> library "/lib/x86_64-linux-gnu/libthread_db.so.1". >> >> Program received signal SIGSEGV, Segmentation fault. >> 0x7489876d in ?? () from >> /lib/x86_64-linux-gnu/libgcrypt.so.11 >> (gdb) backtrace >> #0 0x7489876d in ?? () from >> /lib/x86_64-linux-gnu/libgcrypt.so.11 >> #1 0x748925ae in ?? () from >> /lib/x86_64-linux-gnu/libgcrypt.so.11 >> #2 0x7489004c in gcry_control () from >> /lib/x86_64-linux-gnu/libgcrypt.so.11 >> #3 0x70c75259 in device_api_init () at device.c:64 >> #4 0x70ebc1f2 in boot_Amanda__Device (my_perl=> out>, cv=) at Amanda/Device.c:4676 >> #5 0x77b10591 in Perl_pp_entersub () from >> /usr/lib/libperl.so.5.14 >> #6 0x77b07d36 in Perl_runops_standard () from >> /usr/lib/libperl.so.5.14 >> #7 0x77aa43c0 in Perl_call_sv () from >> /usr/lib/libperl.so.5.14 >> #8 0x77aa51cc in Perl_call_list () from >> /usr/lib/libperl.so.5.14 >> #9 0x77a8faf1 in ?? () from /usr/lib/libperl.so.5.14 >> #10 0x77a9b7b3 in Perl_newATTRSUB () from >> /usr/lib/libperl.so.5.14 >> #11 0x77a9bfa2 in Perl_utilize () from >> /usr/lib/libperl.so.5.14 >> #12 0x77ac989e in Perl_yyparse () from >> /usr/lib/libperl.so.5.14 >> #13 0x77aa9b76 in perl_parse () from /usr/lib/libperl.so.5.14 >> #14 0x00400dae in main () >> (gdb) list >> 1: No such file or directory. >> >> Best regards, >> Kervin >> >> >> Web Services Design, Development and Maintenance http://adevsoft.com/ >> >> >> -Original Message- >> From: Jean-Louis Martineau [mailto:martin...@zmanda.com] >> Sent: Sunday, January 5, 2014 9:19 AM >> To: Kervin L. Pierre >> Cc: amanda-users@amanda.org >> Subject: Re: amlabel segmentation fault >> >> Kevin, >> >> run amlabel under gdb: >> >> $ gdb perl >> (gdb) run /usr/local/sbin/amlabel --version >> (gdb) bt >> (gdb) list >> >> Jean-Louis >> >> On 01/04/2014 11:01 PM, Kervin L. Pierre wrote: >>> Hi, >>> >>> This Segfault seems to occur occasionally and for different >>> reasons. It's possible that amlabel do not handle unknown devices >>> gracefully. But I'm still looking. My tapedevice is "S3". >>> >>> But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault >>> whenever I run amlabel... >>> >>> $ perl -d /usr/local/sbin/amlabel --version >>> >>> Loading DB routines from perl5db.pl version 1.33 Editor support >>> available. >>> >>> Enter h or `h h' for help, or `man perldebug' for more help. >>> >>>
Re: amlabel segmentation fault
Kervin,
Did you try the patch?
Jean-Louis
On 01/06/2014 09:13 AM, Jean-Louis Martineau wrote:
Kervin,
Looks like there is a bug if libcurl use GNUTLS.
Can you try the attached patch?
Jean-Louis
On 01/05/2014 12:10 PM, Kervin L. Pierre wrote:
Hi Jean-Louis,
Thanks for the response. Is there a way to rebuild with '-g' for
debugging support and to avoid stripping symbols? Would that help?
Here is the gdb output...
$ gdb --args perl /usr/local/sbin/amlabel --version
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show
copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/perl...(no debugging symbols
found)...done.
(gdb) run
Starting program: /usr/bin/perl /usr/local/sbin/amlabel --version
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
(gdb) backtrace
#0 0x7489876d in ?? () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#1 0x748925ae in ?? () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#2 0x7489004c in gcry_control () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#3 0x70c75259 in device_api_init () at device.c:64
#4 0x70ebc1f2 in boot_Amanda__Device (my_perl=out>, cv=) at Amanda/Device.c:4676
#5 0x77b10591 in Perl_pp_entersub () from
/usr/lib/libperl.so.5.14
#6 0x77b07d36 in Perl_runops_standard () from
/usr/lib/libperl.so.5.14
#7 0x77aa43c0 in Perl_call_sv () from /usr/lib/libperl.so.5.14
#8 0x77aa51cc in Perl_call_list () from
/usr/lib/libperl.so.5.14
#9 0x77a8faf1 in ?? () from /usr/lib/libperl.so.5.14
#10 0x77a9b7b3 in Perl_newATTRSUB () from
/usr/lib/libperl.so.5.14
#11 0x77a9bfa2 in Perl_utilize () from /usr/lib/libperl.so.5.14
#12 0x77ac989e in Perl_yyparse () from /usr/lib/libperl.so.5.14
#13 0x77aa9b76 in perl_parse () from /usr/lib/libperl.so.5.14
#14 0x00400dae in main ()
(gdb) list
1: No such file or directory.
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Sunday, January 5, 2014 9:19 AM
To: Kervin L. Pierre
Cc: amanda-users@amanda.org
Subject: Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
Hi,
This Segfault seems to occur occasionally and for different
reasons. It's possible that amlabel do not handle unknown devices
gracefully. But I'm still looking. My tapedevice is "S3".
But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault
whenever I run amlabel...
$ perl -d /usr/local/sbin/amlabel --version
Loading DB routines from perl5db.pl version 1.33 Editor support
available.
Enter h or `h h' for help, or `man perldebug' for more help.
Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
main::BEGIN() called at
/usr/local/share/perl/5.14.2/Amanda/Device.pm line 0
eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
Device.pm looks like
# This file was automatically generated by SWIG (http://www.swig.org).
# Version 2.0.4
#
# Do not make changes to this file unless you know what you are
doing--modify # the SWIG interface file instead.
package Amanda::Device;
use base qw(Exporter);
use base qw(DynaLoader);
require Amanda::Header;
package Amanda::Devicec;
bootstrap Amanda::Device;
package Amanda::Device;
@EXPORT = qw();
With the "bootstrap Amanda" line being line 12.
Should that line read "package Amanda::Devicec;"?
Any idea what the issue could be?
Best regards,
Kervin
Web Services Design, Development and Maintenance http://adevsoft.com/
Re: amlabel segmentation fault
Kervin,
Looks like there is a bug if libcurl use GNUTLS.
Can you try the attached patch?
Jean-Louis
On 01/05/2014 12:10 PM, Kervin L. Pierre wrote:
Hi Jean-Louis,
Thanks for the response. Is there a way to rebuild with '-g' for debugging
support and to avoid stripping symbols? Would that help?
Here is the gdb output...
$ gdb --args perl /usr/local/sbin/amlabel --version
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/perl...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/perl /usr/local/sbin/amlabel --version
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
(gdb) backtrace
#0 0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
#1 0x748925ae in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
#2 0x7489004c in gcry_control () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#3 0x70c75259 in device_api_init () at device.c:64
#4 0x70ebc1f2 in boot_Amanda__Device (my_perl=,
cv=) at Amanda/Device.c:4676
#5 0x77b10591 in Perl_pp_entersub () from /usr/lib/libperl.so.5.14
#6 0x77b07d36 in Perl_runops_standard () from /usr/lib/libperl.so.5.14
#7 0x77aa43c0 in Perl_call_sv () from /usr/lib/libperl.so.5.14
#8 0x77aa51cc in Perl_call_list () from /usr/lib/libperl.so.5.14
#9 0x77a8faf1 in ?? () from /usr/lib/libperl.so.5.14
#10 0x77a9b7b3 in Perl_newATTRSUB () from /usr/lib/libperl.so.5.14
#11 0x77a9bfa2 in Perl_utilize () from /usr/lib/libperl.so.5.14
#12 0x77ac989e in Perl_yyparse () from /usr/lib/libperl.so.5.14
#13 0x77aa9b76 in perl_parse () from /usr/lib/libperl.so.5.14
#14 0x00400dae in main ()
(gdb) list
1 : No such file or directory.
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Sunday, January 5, 2014 9:19 AM
To: Kervin L. Pierre
Cc: amanda-users@amanda.org
Subject: Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
Hi,
This Segfault seems to occur occasionally and for different reasons. It's possible that
amlabel do not handle unknown devices gracefully. But I'm still looking. My tapedevice
is "S3".
But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault whenever I
run amlabel...
$ perl -d /usr/local/sbin/amlabel --version
Loading DB routines from perl5db.pl version 1.33 Editor support
available.
Enter h or `h h' for help, or `man perldebug' for more help.
Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
main::BEGIN() called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
Device.pm looks like
# This file was automatically generated by SWIG (http://www.swig.org).
# Version 2.0.4
#
# Do not make changes to this file unless you know what you are
doing--modify # the SWIG interface file instead.
package Amanda::Device;
use base qw(Exporter);
use base qw(DynaLoader);
require Amanda::Header;
package Amanda::Devicec;
bootstrap Amanda::Device;
package Amanda::Device;
@EXPORT = qw();
With the "bootstrap Amanda" line being line 12.
Should that line read "package Amanda::Devicec;"?
Any idea what the issue could be?
Best regards,
Kervin
Web Services Design, Development and Maintenance http://adevsoft.com/
diff --git a/common-src/glib-util.c b/common-src/glib-util.c
index 713f0fc..905d518 100644
--- a/common-src/glib-util.c
+++ b/common-src/glib-util.c
@@ -27,6 +27,7 @@
#include "amanda.h"
#include "glib-util.h"
+#include "pthread.h"
#include "conffile.h" /* For find_multiplier. */
#ifdef HAVE_LIBCURL
@@ -71,7 +72,13 @@ GCRY_THREAD_OPTION_PTHREAD_IMPL;
static void
init_ssl(void)
{
-gcry_control(GCRYCTL_SET_THREAD_CBS);
+gcry_control(GCRYCTL_SET_THREAD_CBS, &gcry_threads_pthread);
+
+if (!gcry_check_version (GCRYPT_VERSION)) {
+ g_critical("libgcrypt version mismatch");
+}
+
+gcry_control (GCRYCTL_INITIALIZATION_FINISHED, 0);
}
#else /* LIBCURL_USE_GNUTLS */
RE: amlabel segmentation fault
Hi Jean-Louis,
Thanks for the response. Is there a way to rebuild with '-g' for debugging
support and to avoid stripping symbols? Would that help?
Here is the gdb output...
$ gdb --args perl /usr/local/sbin/amlabel --version
GNU gdb (GDB) 7.6.1-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/perl...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/perl /usr/local/sbin/amlabel --version
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
(gdb) backtrace
#0 0x7489876d in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
#1 0x748925ae in ?? () from /lib/x86_64-linux-gnu/libgcrypt.so.11
#2 0x7489004c in gcry_control () from
/lib/x86_64-linux-gnu/libgcrypt.so.11
#3 0x70c75259 in device_api_init () at device.c:64
#4 0x70ebc1f2 in boot_Amanda__Device (my_perl=,
cv=) at Amanda/Device.c:4676
#5 0x77b10591 in Perl_pp_entersub () from /usr/lib/libperl.so.5.14
#6 0x77b07d36 in Perl_runops_standard () from /usr/lib/libperl.so.5.14
#7 0x77aa43c0 in Perl_call_sv () from /usr/lib/libperl.so.5.14
#8 0x77aa51cc in Perl_call_list () from /usr/lib/libperl.so.5.14
#9 0x77a8faf1 in ?? () from /usr/lib/libperl.so.5.14
#10 0x77a9b7b3 in Perl_newATTRSUB () from /usr/lib/libperl.so.5.14
#11 0x77a9bfa2 in Perl_utilize () from /usr/lib/libperl.so.5.14
#12 0x77ac989e in Perl_yyparse () from /usr/lib/libperl.so.5.14
#13 0x77aa9b76 in perl_parse () from /usr/lib/libperl.so.5.14
#14 0x00400dae in main ()
(gdb) list
1 : No such file or directory.
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
-Original Message-
From: Jean-Louis Martineau [mailto:martin...@zmanda.com]
Sent: Sunday, January 5, 2014 9:19 AM
To: Kervin L. Pierre
Cc: amanda-users@amanda.org
Subject: Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
> Hi,
>
> This Segfault seems to occur occasionally and for different reasons. It's
> possible that amlabel do not handle unknown devices gracefully. But I'm
> still looking. My tapedevice is "S3".
>
> But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault whenever
> I run amlabel...
>
> $ perl -d /usr/local/sbin/amlabel --version
>
> Loading DB routines from perl5db.pl version 1.33 Editor support
> available.
>
> Enter h or `h h' for help, or `man perldebug' for more help.
>
> Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
> require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
> main::BEGIN() called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
> line 0
> eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
> line 0
>
> Device.pm looks like
> # This file was automatically generated by SWIG (http://www.swig.org).
> # Version 2.0.4
> #
> # Do not make changes to this file unless you know what you are
> doing--modify # the SWIG interface file instead.
>
> package Amanda::Device;
> use base qw(Exporter);
> use base qw(DynaLoader);
> require Amanda::Header;
> package Amanda::Devicec;
> bootstrap Amanda::Device;
> package Amanda::Device;
> @EXPORT = qw();
>
> With the "bootstrap Amanda" line being line 12.
>
> Should that line read "package Amanda::Devicec;"?
>
> Any idea what the issue could be?
>
> Best regards,
> Kervin
>
> Web Services Design, Development and Maintenance http://adevsoft.com/
>
>
Re: amlabel segmentation fault
Kevin,
run amlabel under gdb:
$ gdb perl
(gdb) run /usr/local/sbin/amlabel --version
(gdb) bt
(gdb) list
Jean-Louis
On 01/04/2014 11:01 PM, Kervin L. Pierre wrote:
Hi,
This Segfault seems to occur occasionally and for different reasons. It's possible that
amlabel do not handle unknown devices gracefully. But I'm still looking. My tapedevice
is "S3".
But I just built 3.3.5 on a Ubuntu desktop and now I get a segfault whenever I
run amlabel...
$ perl -d /usr/local/sbin/amlabel --version
Loading DB routines from perl5db.pl version 1.33
Editor support available.
Enter h or `h h' for help, or `man perldebug' for more help.
Signal SEGV at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 12
require Amanda/Device.pm called at /usr/local/sbin/amlabel line 29
main::BEGIN() called at /usr/local/share/perl/5.14.2/Amanda/Device.pm
line 0
eval {...} called at /usr/local/share/perl/5.14.2/Amanda/Device.pm line 0
Device.pm looks like
# This file was automatically generated by SWIG (http://www.swig.org).
# Version 2.0.4
#
# Do not make changes to this file unless you know what you are doing--modify
# the SWIG interface file instead.
package Amanda::Device;
use base qw(Exporter);
use base qw(DynaLoader);
require Amanda::Header;
package Amanda::Devicec;
bootstrap Amanda::Device;
package Amanda::Device;
@EXPORT = qw();
With the "bootstrap Amanda" line being line 12.
Should that line read "package Amanda::Devicec;"?
Any idea what the issue could be?
Best regards,
Kervin
Web Services Design, Development and Maintenance
http://adevsoft.com/
Re: amlabel --barcode fails
Dennis Benndorf wrote: Hi Jean-Louis, amanda@dl380-54:~$ amgetconf daily autolabel "" Ok, but I thought it would automaticly label the string on the barcode to tape, doesnt it? no, generated label always use the autolabel template. you want: autolabel "$b" Jean-Louis Regards, Dennis Original-Nachricht Datum: Mon, 18 Apr 2011 10:10:24 -0400 Von: Jean-Louis Martineau An: Dennis Benndorf CC: amanda-users@amanda.org Betreff: Re: amlabel --barcode fails Dennis Benndorf wrote: Hello, testing 3.3beta1, fails for me when using the new feature "amlabel --barcode": amlabel -f --barcode D10080 -olabelstr='^D1[0-9]*$' -otpchanger=l700-robot-MRO daily Reading label... barcode: D10080 sl_barcode: D10080 slot: 269 Found an empty tape. Writing label ''... The generated label is a empty. what's the output of: amgetconf daily autolabel Jean-Louis
Re: amlabel --barcode fails
Oh yes, thank you! Nice feature.. Original-Nachricht > Datum: Mon, 18 Apr 2011 10:21:25 -0400 > Von: Jean-Louis Martineau > An: Dennis Benndorf > CC: amanda-users@amanda.org > Betreff: Re: amlabel --barcode fails > Dennis Benndorf wrote: > > Hi Jean-Louis, > > > > amanda@dl380-54:~$ amgetconf daily autolabel > > "" > > > > > > Ok, but I thought it would automaticly label the string on the barcode > to tape, doesnt it? > > > no, generated label always use the autolabel template. > you want: autolabel "$b" > > Jean-Louis > > Regards, > > Dennis > > > > Original-Nachricht > > > >> Datum: Mon, 18 Apr 2011 10:10:24 -0400 > >> Von: Jean-Louis Martineau > >> An: Dennis Benndorf > >> CC: amanda-users@amanda.org > >> Betreff: Re: amlabel --barcode fails > >> > > > > > >> Dennis Benndorf wrote: > >> > >>> Hello, > >>> > >>> testing 3.3beta1, fails for me when using the new feature "amlabel > >>> > >> --barcode": > >> > >>> amlabel -f --barcode D10080 -olabelstr='^D1[0-9]*$' > >>> > >> -otpchanger=l700-robot-MRO daily > >> > >>> Reading label... > >>> barcode: D10080 > >>> sl_barcode: D10080 > >>> slot: 269 > >>> Found an empty tape. > >>> Writing label ''... > >>> > >>> > >> The generated label is a empty. > >> what's the output of: amgetconf daily autolabel > >> > >> Jean-Louis > >> > > > > > -- GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit gratis Handy-Flat! http://portal.gmx.net/de/go/dsl
Re: amlabel --barcode fails
Hi Jean-Louis, amanda@dl380-54:~$ amgetconf daily autolabel "" Ok, but I thought it would automaticly label the string on the barcode to tape, doesnt it? Regards, Dennis Original-Nachricht > Datum: Mon, 18 Apr 2011 10:10:24 -0400 > Von: Jean-Louis Martineau > An: Dennis Benndorf > CC: amanda-users@amanda.org > Betreff: Re: amlabel --barcode fails > Dennis Benndorf wrote: > > Hello, > > > > testing 3.3beta1, fails for me when using the new feature "amlabel > --barcode": > > > > amlabel -f --barcode D10080 -olabelstr='^D1[0-9]*$' > -otpchanger=l700-robot-MRO daily > > > > Reading label... > > barcode: D10080 > > sl_barcode: D10080 > > slot: 269 > > Found an empty tape. > > Writing label ''... > > > The generated label is a empty. > what's the output of: amgetconf daily autolabel > > Jean-Louis -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de
Re: amlabel --barcode fails
Dennis Benndorf wrote: Hello, testing 3.3beta1, fails for me when using the new feature "amlabel --barcode": amlabel -f --barcode D10080 -olabelstr='^D1[0-9]*$' -otpchanger=l700-robot-MRO daily Reading label... barcode: D10080 sl_barcode: D10080 slot: 269 Found an empty tape. Writing label ''... The generated label is a empty. what's the output of: amgetconf daily autolabel Jean-Louis
Re: amlabel problem - reading chunks from holding area
Brian Cuttler schrieb: > Chris, > > I _so_ love amanda! Nice to hear that ;) Stefan
Re: amlabel problem - reading chunks from holding area
Chris, I _so_ love amanda! thank you! On Fri, Feb 29, 2008 at 02:43:50PM -0500, Chris Hoogendyk wrote: > > > Brian Cuttler wrote: > >Stefan, et al, > > > >We have decided that the standalone tape drive has failed, it > >will not read nor write known good tapes. > > > >We are thinking of allocating a large NFS partition (I know, bad > >mojo and performace but apparently/supposedly its going to be temporary) > >and just letting the files live in the "amanda work area". > > > >The question then becomes one of file restores. > > > >How do you restore data from holding area chunks ? > >Do I just cat them together (is there an easy way to get > >them in order ?), if there a good method of reading them ? > >Or can I create readable files that aren't chunked ? > > Amanda will restore files from dle's that are still on the holding disk > just as easily as from tapes, only faster. Same procedure. Amanda knows > where they are and that they haven't been flushed to tape yet. I've done > it before just to see. > > > --- > > Chris Hoogendyk > > - > O__ Systems Administrator > c/ /'_ --- Biology & Geology Departments > (*) \(*) -- 140 Morrill Science Center > ~~ - University of Massachusetts, Amherst > > <[EMAIL PROTECTED]> > > --- > > Erd?s 4 > > --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: amlabel problem - reading chunks from holding area
Brian Cuttler wrote: Stefan, et al, We have decided that the standalone tape drive has failed, it will not read nor write known good tapes. We are thinking of allocating a large NFS partition (I know, bad mojo and performace but apparently/supposedly its going to be temporary) and just letting the files live in the "amanda work area". The question then becomes one of file restores. How do you restore data from holding area chunks ? Do I just cat them together (is there an easy way to get them in order ?), if there a good method of reading them ? Or can I create readable files that aren't chunked ? Amanda will restore files from dle's that are still on the holding disk just as easily as from tapes, only faster. Same procedure. Amanda knows where they are and that they haven't been flushed to tape yet. I've done it before just to see. --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst <[EMAIL PROTECTED]> --- Erdös 4
Re: amlabel problem - reading chunks from holding area
Stefan, et al,
We have decided that the standalone tape drive has failed, it
will not read nor write known good tapes.
We are thinking of allocating a large NFS partition (I know, bad
mojo and performace but apparently/supposedly its going to be temporary)
and just letting the files live in the "amanda work area".
The question then becomes one of file restores.
How do you restore data from holding area chunks ?
Do I just cat them together (is there an easy way to get
them in order ?), if there a good method of reading them ?
Or can I create readable files that aren't chunked ?
I know that the right way is to build a new version of amanda,
using vtapes, and install it on the server that has the large
partition - but that machine too is scheduled to move offsite.
Big investment in time for a solution that is about to walk out
of the door, but I have to at least try and get backups done for
the machines our site will retain.
thanks,
Brian
On Fri, Feb 29, 2008 at 11:13:06AM -0500, Brian Cuttler wrote:
>
> Stefan,
>
> I didn't realize the amlabel command wrote a log, I have it,
> unfortunately not as informative as one might like in these
> circumstances.
>
> samar 5# more amlabel.20080229105753.debug
> amlabel: debug 1 pid 873486 ruid 0 euid 0: start at Fri Feb 29 10:57:53 2008
> amlabel: writing label: Invalid argument
> amlabel: pid 873486 finish time Fri Feb 29 10:57:53 2008
>
> The change from the jukebox to the standalone drive involved
> these changes to amanda.conf.
>
> samar 11# diff amanda.conf amanda.conf-20080221-jukebox
> 93,95c93,94
> < #runtapes 2 # number of tapes to be used in a single run of amdump
> < runtapes 1# number of tapes to be used in a single run of amdump
> < #tpchanger "chg-zd-mtx" # the tape-changer glue script
> ---
> > runtapes 2# number of tapes to be used in a single run of amdump
> > tpchanger "chg-zd-mtx"# the tape-changer glue script
> 97,98c96
> < #tapedev "/dev/sdlt2" # the no-rewind tape device to be used
> < tapedev "/dev/sdlt" # the no-rewind tape device to be used
> ---
> > tapedev "/dev/sdlt2" # the no-rewind tape device to be used
> 101,102c99,100
> < #changerfile "/usr5/amanda/chg-zd-mtx"
> < #changerdev "/dev/scsi/sc7d1l0"
> ---
> > changerfile "/usr5/amanda/chg-zd-mtx"
> > changerdev "/dev/scsi/sc7d1l0"
>
> Apparently I didn't change the tape type, I probably should have
> but I don't know that the tapes differ except for capacity as the
> current drive is an SDLT 220.
>
> samar 13# mt -f /dev/sdlt status
> Controller: SCSI
> Device: QUANTUM: SuperDLT1 3737?7
> Status: 0x20262
> Drive type: unknown
> Media : READY, writable, at BOT
>
> samar 14# mt -f /dev/sdlt2 status
> Controller: SCSI
> Device: QUANTUM: SDLT320 3838?8
> Status: 0xa00
> Drive type: unknown
> Media : Not READY
>
> From amanda.conf, the tapetype definition. Nothing terribly odd
> here I don't think.
>
> define tapetype SDLT {
> comment "QUAMTUM SDLT320"
> length 16 mbytes
> filemark 100 kbytes # don't know a better value
> speed 100 kbytes# dito
> }
>
>
> And again, I was able to label and write the first several tapes
> without addititional changes to the config.
>
> I was also unable to dump or tar to the drive, I wonder if we
> don't have a general failure.
>
> I will ask a user to see if they can access the drive properly
> with whatever tapes they normally use in this drive (it was used
> for user data archiving before I commendeered it.
>
> thanks,
>
> Brian
>
>
>
> On Fri, Feb 29, 2008 at 09:57:07AM +0100, Stefan G. Weichinger wrote:
> > Brian Cuttler schrieb:
> > > Hello Amanda users,
> > >
> > > I had the jukebox I use on one of my SGI/IRIX Amanda servers fail
> > > and we reverted to the attached standalone SDLT 220.
> > >
> > > I modified amanda.conf to use the different tape drive and to
> > > not use any changer config.
> > >
> > > I was able to label (one/day) a few tapes (and write them that evening),
> > > but I'm having difficulty with subsequent tapes.
> > >
> > > samar 8# /usr/local/sbin/amlabel -f samar SAMAR30
> > > rewinding, reading label, reading label: Invalid argument
> > > rewinding, writing label SAMAR30
> > > amlabel: writing label: Invalid argument
> >
> > So you use another tapetype.
> > What does it look like? Any specific settings in there?
> > Using some unusual blocksize or something?
> >
> > Also browse the log- and debugfiles for anything related.
> >
> > Stefan
> ---
>Brian R Cuttler [EMAIL PROTECTED]
>Computer Systems Support(v) 518 486-1697
>Wadsworth Center(f) 518 473-6384
>NYS Department of HealthHelp Desk 518 47
Re: amlabel problem
Stefan,
I didn't realize the amlabel command wrote a log, I have it,
unfortunately not as informative as one might like in these
circumstances.
samar 5# more amlabel.20080229105753.debug
amlabel: debug 1 pid 873486 ruid 0 euid 0: start at Fri Feb 29 10:57:53 2008
amlabel: writing label: Invalid argument
amlabel: pid 873486 finish time Fri Feb 29 10:57:53 2008
The change from the jukebox to the standalone drive involved
these changes to amanda.conf.
samar 11# diff amanda.conf amanda.conf-20080221-jukebox
93,95c93,94
< #runtapes 2 # number of tapes to be used in a single run of amdump
< runtapes 1# number of tapes to be used in a single run of amdump
< #tpchanger "chg-zd-mtx" # the tape-changer glue script
---
> runtapes 2# number of tapes to be used in a single run of amdump
> tpchanger "chg-zd-mtx"# the tape-changer glue script
97,98c96
< #tapedev "/dev/sdlt2" # the no-rewind tape device to be used
< tapedev "/dev/sdlt" # the no-rewind tape device to be used
---
> tapedev "/dev/sdlt2" # the no-rewind tape device to be used
101,102c99,100
< #changerfile "/usr5/amanda/chg-zd-mtx"
< #changerdev "/dev/scsi/sc7d1l0"
---
> changerfile "/usr5/amanda/chg-zd-mtx"
> changerdev "/dev/scsi/sc7d1l0"
Apparently I didn't change the tape type, I probably should have
but I don't know that the tapes differ except for capacity as the
current drive is an SDLT 220.
samar 13# mt -f /dev/sdlt status
Controller: SCSI
Device: QUANTUM: SuperDLT1 3737?7
Status: 0x20262
Drive type: unknown
Media : READY, writable, at BOT
samar 14# mt -f /dev/sdlt2 status
Controller: SCSI
Device: QUANTUM: SDLT320 3838?8
Status: 0xa00
Drive type: unknown
Media : Not READY
>From amanda.conf, the tapetype definition. Nothing terribly odd
here I don't think.
define tapetype SDLT {
comment "QUAMTUM SDLT320"
length 16 mbytes
filemark 100 kbytes # don't know a better value
speed 100 kbytes# dito
}
And again, I was able to label and write the first several tapes
without addititional changes to the config.
I was also unable to dump or tar to the drive, I wonder if we
don't have a general failure.
I will ask a user to see if they can access the drive properly
with whatever tapes they normally use in this drive (it was used
for user data archiving before I commendeered it.
thanks,
Brian
On Fri, Feb 29, 2008 at 09:57:07AM +0100, Stefan G. Weichinger wrote:
> Brian Cuttler schrieb:
> > Hello Amanda users,
> >
> > I had the jukebox I use on one of my SGI/IRIX Amanda servers fail
> > and we reverted to the attached standalone SDLT 220.
> >
> > I modified amanda.conf to use the different tape drive and to
> > not use any changer config.
> >
> > I was able to label (one/day) a few tapes (and write them that evening),
> > but I'm having difficulty with subsequent tapes.
> >
> > samar 8# /usr/local/sbin/amlabel -f samar SAMAR30
> > rewinding, reading label, reading label: Invalid argument
> > rewinding, writing label SAMAR30
> > amlabel: writing label: Invalid argument
>
> So you use another tapetype.
> What does it look like? Any specific settings in there?
> Using some unusual blocksize or something?
>
> Also browse the log- and debugfiles for anything related.
>
> Stefan
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Re: amlabel problem
Brian Cuttler schrieb: > Hello Amanda users, > > I had the jukebox I use on one of my SGI/IRIX Amanda servers fail > and we reverted to the attached standalone SDLT 220. > > I modified amanda.conf to use the different tape drive and to > not use any changer config. > > I was able to label (one/day) a few tapes (and write them that evening), > but I'm having difficulty with subsequent tapes. > > samar 8# /usr/local/sbin/amlabel -f samar SAMAR30 > rewinding, reading label, reading label: Invalid argument > rewinding, writing label SAMAR30 > amlabel: writing label: Invalid argument So you use another tapetype. What does it look like? Any specific settings in there? Using some unusual blocksize or something? Also browse the log- and debugfiles for anything related. Stefan
Re: amlabel: not an amanda tape ??? [ SOLVED ]
[ [ [ Anybody else seeing this?
:
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
Re: amlabel: not an amanda tape ???
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 ???
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 problem
On Thursday 17 August 2006 03:15, Natalia García Nebot <[EMAIL PROTECTED]> wrote: > Hi! I have installed amanda on my server host. The server is conected to > a tape device. I have created a configuration named DiariaPrueba. I have > configured all parameters in amanda.conf and I want to label only one > tape to make tests before. In my amanda.conf I have configures de > parameter labelstr to > labelstr "^DiariaPruebaTape[0-9][0-9]*$" > > When I try to label my first tape amlabe says me: > amlabel: could not load tapelist "/etc/amanda/DiariaPrueba/tapelist" You may need to create tapelist by hand the first time. 'touch /etc/amanda/DiariaPrueba/tapelist' > > So i tried this command: > su amanda -c "amlabel -f DiariaPrueba DiariaPrueba01" > > And amlabel says me: > amlabel: label DiariaPrueba01 doesn't match labelstr > "^DiariaPruebaTape[0-9][0-9]*$" > > What's wrong? Why can't I label a tape? amlabel has told you. Tape labels must match the pattern ^DiariaPruebaTape[0-9][0-9]*$ But your label does not have the "Tape" part in it. Try su amanda -c "amlabel -f DiariaPrueba DiariaPruebaTape01" -- -- jeffrey anderson| [EMAIL PROTECTED] Lawrence Berkeley National Laboratory | Mailstop 50a-5101 Phone: 510 486-4208 | Fax: 510 486-6808
Re: amlabel problem
On Thu, 17 Aug 2006 at 12:15pm, Natalia García Nebot wrote Hi! I have installed amanda on my server host. The server is conected to a tape device. I have created a configuration named DiariaPrueba. I have configured all parameters in amanda.conf and I want to label only one tape to make tests before. In my amanda.conf I have configures de parameter labelstr to labelstr "^DiariaPruebaTape[0-9][0-9]*$" When I try to label my first tape amlabe says me: amlabel: could not load tapelist "/etc/amanda/DiariaPrueba/tapelist" su amanda -c "touch /etc/amanda/DiariaPrueba/tapelist" -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amlabel problem
Natalia García Nebot wrote: > Hi! I have installed amanda on my server host. The server is conected to > a tape device. I have created a configuration named DiariaPrueba. I have > configured all parameters in amanda.conf and I want to label only one > tape to make tests before. In my amanda.conf I have configures de > parameter labelstr to >labelstr "^DiariaPruebaTape[0-9][0-9]*$" > > When I try to label my first tape amlabe says me: >amlabel: could not load tapelist "/etc/amanda/DiariaPrueba/tapelist" > > So i tried this command: > su amanda -c "amlabel -f DiariaPrueba DiariaPrueba01" > > And amlabel says me: >amlabel: label DiariaPrueba01 doesn't match labelstr > "^DiariaPruebaTape[0-9][0-9]*$" > > What's wrong? Why can't I label a tape? > Natalia, Your labelstr contains ..Tape.. while the amlabel command does not. You should make it matching. Franz - Franz-Heinrich Massmann GeoForschungsZentrum Potsdam (GFZ) Department 1: Geodesy and Remote Sensing, Section 1.2 c/o DLR Oberpfaffenhofen 82230 Wessling, Germany Tel./Fax: (+49) 8153-28-1206/1735 email: [EMAIL PROTECTED] -
Re: amlabel: writing label: Device or resource busy
On Wed, Aug 09, 2006 at 05:22:37PM +0200, Franz-Heinrich Massmann wrote: > Hi, > > The same problem as Sven reported on 02-Aug has been seen > with Novell Suse 10.1/Qualstar TLS46120/Amanda 2.5.0. > > Six out of 20 tapes have been labelled some time ago, > but no way to label another one. > > Does somebody know any workaround? > > Do I have to delete all tapelist files and label everything > from the beginning? Could you, and/or Sven, file a bug report on sourceforge? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel: writing label: Device or resource busy
Hi, The same problem as Sven reported on 02-Aug has been seen with Novell Suse 10.1/Qualstar TLS46120/Amanda 2.5.0. Six out of 20 tapes have been labelled some time ago, but no way to label another one. Does somebody know any workaround? Do I have to delete all tapelist files and label everything from the beginning? Thanks. Franz - Franz-Heinrich Massmann GeoForschungsZentrum Potsdam (GFZ) Department 1: Geodesy and Remote Sensing, Section 1.2 c/o DLR Oberpfaffenhofen 82230 Wessling, Germany Tel./Fax: (+49) 8153-28-1206/1735 email: [EMAIL PROTECTED] -
Re: amlabel: command not found (was Re: port 35280 not secure)
On Wednesday 05 April 2006 10:52, Anne Wilson wrote: >On Wednesday 05 April 2006 15:27, Gene Heskett wrote: >> I found it, at least I did here Anne. It seems that if you are >> logged in from a password login as the user amanda, then >> /usr/local/sbin IS NOT in the $PATH, see my other private message. >> >> I also posted both here and on the fedora list as to why >> /usr/local/bin is not in a normal users $PATH. In any event, I >> added it to the ~/.bash_profile and it survives doing an 'su - >> amanda' now. >> >> But my real question is: whyinhell ain't it in a normal users $PATH >> in the first place? Boggles this mind, thats for sure... > >Well, that has certainly moved us along. Amdump appears to have > initialised all the slots, but then > >These dumps were to tape Dailys-1. >The next tape Amanda expects to use is: a new tape. >The next new tape already labelled is: Dailys-2. > >FAILURE AND STRANGE DUMP SUMMARY: > borg /homelev 0 FAILED [dump larger than available tape space, >24082716 KB, but cannot incremental dump new disk] > borg /Public lev 0 FAILED [dumper returned FAILED] > borg /Public lev 0 FAILED [/sbin/dump returned 1] > borg /Public lev 0 FAILED [dumper returned FAILED] > borg /Public lev 0 FAILED [/sbin/dump returned 1] > >so now I just have to work out why a 24GB backup won't fit into 97GB > disk space. I don't think you have sufficient holding disk as its all collected in the holding disk before its flushed to the media & I recall from a previous message its only about 11GB? It might do to set the phrase 'holding disk no' in that dumptype. Also, what size did you set in the HARD-DISK tapetype? To do a level 0 might need that set bigger by a couple of gigs more than the above, or take advantage of the new tape spanning abilities of 2.5.0. I have to run for about 4 hours, the missus is bowling. >Anne -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: amlabel: command not found (was Re: port 35280 not secure)
On Wednesday 05 April 2006 15:27, Gene Heskett wrote: > > I found it, at least I did here Anne. It seems that if you are logged > in from a password login as the user amanda, then /usr/local/sbin IS > NOT in the $PATH, see my other private message. > > I also posted both here and on the fedora list as to why /usr/local/bin > is not in a normal users $PATH. In any event, I added it to the > ~/.bash_profile and it survives doing an 'su - amanda' now. > > But my real question is: whyinhell ain't it in a normal users $PATH in > the first place? Boggles this mind, thats for sure... Well, that has certainly moved us along. Amdump appears to have initialised all the slots, but then These dumps were to tape Dailys-1. The next tape Amanda expects to use is: a new tape. The next new tape already labelled is: Dailys-2. FAILURE AND STRANGE DUMP SUMMARY: borg /homelev 0 FAILED [dump larger than available tape space, 24082716 KB, but cannot incremental dump new disk] borg /Public lev 0 FAILED [dumper returned FAILED] borg /Public lev 0 FAILED [/sbin/dump returned 1] borg /Public lev 0 FAILED [dumper returned FAILED] borg /Public lev 0 FAILED [/sbin/dump returned 1] so now I just have to work out why a 24GB backup won't fit into 97GB disk space. Anne pgpwGPGe3lhfk.pgp Description: PGP signature
Re: amlabel: command not found (was Re: port 35280 not secure)
On Wednesday 05 April 2006 09:49, Anne Wilson wrote:
>On Monday 03 April 2006 22:20, Kevin Till wrote:
>> Anne Wilson wrote:
>> > On Monday 03 April 2006 22:03, you wrote:
>> >>what is the latest output of:
>> >>
>> >>ls -la /usr/local/sbin/amcheck
>> >
>> > -rwsr-x--- 1 amanda disk 82445 Mar 26 20:31
>> > /usr/local/sbin/amcheck
>> >
>> > I've talked it over with Gene. Early on in the installation I
>> > made a mistake, which I thought I had corrected, but which may be
>> > responsible for the whole mess. I'm going to start all over
>> > again. Thanks for trying to help, Kevin. I'll let you know how it
>> > goes.
>>
>> Ok, just do "make install" again, it will install
>>
>> -rwsr-x--- 1 root disk 63345 Apr 3 10:45 /usr/local/sbin/amcheck
>>
>> and let us know how it goes.
>
>I've completely rebuilt and reinstalled. Because we also had trouble
> with that data link, I nuked the slots and link as well, and re-ran
> mkvtapes as amanda, only to see
>
>mode of `/Backup/amandatapes/Dailys/slot1' changed to 0750 (rwxr-x---)
>./mkvtapes: line 24: amlabel: command not found
>etc.
>
>So, two possibilities. Am I running this from the wrong directory? -
> it is in server-src. I've tried running mkvtapes both by referencing
> the directory above, where I originally had it, and by putting a copy
> in server-src, both times getting the same result.
>
>Or is there something actually wrong with my amendments of the script:
>
>for n in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
>do
>mkdir -p /Backup/amandatapes/Dailys/slot${n}
>chmod -v 750 /Backup/amandatapes/Dailys/slot${n}
>rm -f /Backup/amandatapes/Dailys/data
>ln
>-s /Backup/amandatapes/Dailys/slot${n} /Backup/amandatapes/Dailys/data
>amlabel -f Daily Dailys-${n} slot ${n}
>done
>
>Anne
I found it, at least I did here Anne. It seems that if you are logged
in from a password login as the user amanda, then /usr/local/sbin IS
NOT in the $PATH, see my other private message.
I also posted both here and on the fedora list as to why /usr/local/bin
is not in a normal users $PATH. In any event, I added it to the
~/.bash_profile and it survives doing an 'su - amanda' now.
But my real question is: whyinhell ain't it in a normal users $PATH in
the first place? Boggles this mind, thats for sure...
--
Cheers, Gene
People having trouble with vz bouncing email to me should add the word
'online' between the 'verizon', and the dot which bypasses vz's
stupid bounce rules. I do use spamassassin too. :-)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: amlabel Issue
Thanks for the help, everyone. This was a permissions issue. Thanks! On Aug 24, 2005, at 5:02 PM, James Jacocks wrote: Indeed, amtape produces the same response. Does this help us to determine the cause? Thanks! On Aug 23, 2005, at 6:49 PM, Jon LaBadie wrote: On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote: We are currently experiencing the below issue using amlabel. I have tried with and without a tape loaded, with and without a slot specified etc.. All chg-zd-mtx "tests" described in the script notes have been confirmed to work.. As an intermediate test (between chg-zd-mtx direct and am- applications), did you try amtape to manipulate your drive and changer? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel Issue
Indeed, amtape produces the same response. Does this help us to determine the cause? Thanks! On Aug 23, 2005, at 6:49 PM, Jon LaBadie wrote: On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote: We are currently experiencing the below issue using amlabel. I have tried with and without a tape loaded, with and without a slot specified etc.. All chg-zd-mtx "tests" described in the script notes have been confirmed to work.. As an intermediate test (between chg-zd-mtx direct and am- applications), did you try amtape to manipulate your drive and changer? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel Issue
On Tue, Aug 23, 2005 at 02:04:13PM -0400, James Jacocks wrote: > We are currently experiencing the below issue using > amlabel. I have tried with and without a tape loaded, with and > without a slot specified etc.. All chg-zd-mtx "tests" described in > the script notes have been confirmed to work.. As an intermediate test (between chg-zd-mtx direct and am-applications), did you try amtape to manipulate your drive and changer? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: amlabel: tape is write protected
Thanks Jon. It was device permission. /dev/nst0 was set read only for group disk. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jon LaBadie Sent: Tuesday, July 26, 2005 11:32 AM To: amanda-users@amanda.org Subject: Re: amlabel: tape is write protected On Tue, Jul 26, 2005 at 11:00:48AM -0400, Lei Zhong wrote: > Hi all, > > > > When I tried to label a tape using amlabel, I got an error "amlabel: > tape is write protected". Does anybody know how to fix it? Right now, > I am running mt -f /dev/nst0 erase. It's taking forever. Is there any > fast way to commission a tape? Thank you, Lei > I ususally think of "write protected" as the physical tab on the tape itself. I suppose it could also come from device permissions, but that would not be my first guess. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel: tape is write protected
On Tue, Jul 26, 2005 at 11:00:48AM -0400, Lei Zhong wrote: > Hi all, > > > > When I tried to label a tape using amlabel, I got an error "amlabel: > tape is write protected". Does anybody know how to fix it? Right now, > I am running mt -f /dev/nst0 erase. It's taking forever. Is there any > fast way to commission a tape? Thank you, Lei > I ususally think of "write protected" as the physical tab on the tape itself. I suppose it could also come from device permissions, but that would not be my first guess. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel question
ÐÐÑÐÑÐ ÐÐÑ wrote: amlabel: label svn16 doesn't match labelstr "^svn[1-25][1-25]*$" in amanda.conf labelstr has a following appearance: labelstr "^svn[1-25][1-25]*$" Learn something more about regular expressions again. Between square brackets is a set of characters, and a range indicate just a character range: "[1-39]" means 1, or 2, or 3 or 9. The above "[1-25]" means: "1" or "2" or "5". Which fails because it encounters a "6". A better label is: "^svn[0-9][0-9]$". The label is just to protect you from accidently overwriting a tape having nothing to do with amanda, and to avoid mixing different configurations of tapes (when you multiple configs, e.g. one for archiving one for daily, or one for that department and another config for a different department). There is no need to limit the possible range of numbers to 25 in the labelstring -- too strict. -- 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: AMLABEL
On Monday 21 February 2005 10:01, Paul Bijnens wrote: >Gene Heskett wrote: >> Silly Q? Could this be the reason I've blamed amanda for not >> being able to rewind the tape in a Seagate 4586N changer? And >> while amanda couldn't rewind it, mt could? > >I don't think so. The file contains parameters to set blocksize >and hw-compression if different modes. But rewind is (AFAIK) a > generic scsi-tape command. Anyway, amanda does not read that file; > adding it would not a difference for amanda. No, amanda does, but presumably stinit does. OTOH, I don't believe I've ever run stinit either, although I have looked at the manpage for it, without finding the answer to any of my 'itches' :) >"man stinit" gives some idea what can be configured in the file. > >> Humm, on inspecting that file, I find its quite jurassic, offering >> no clues for anything newer than whats obviously decade+ old DDS1 >> drives. And no mention of rewind capabilities for any drive IIRC. >> So I doubt its connected with my non-rewinding chg-scsi script >> useage. I should correct that, it treats DDS1's with data compression, and DDS2-3-4's the same, or does in my version of the file. In any event, it wasn't any help to me at the time. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.34% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL
Gene Heskett wrote: Silly Q? Could this be the reason I've blamed amanda for not being able to rewind the tape in a Seagate 4586N changer? And while amanda couldn't rewind it, mt could? I don't think so. The file contains parameters to set blocksize and hw-compression if different modes. But rewind is (AFAIK) a generic scsi-tape command. Anyway, amanda does not read that file; adding it would not a difference for amanda. "man stinit" gives some idea what can be configured in the file. Humm, on inspecting that file, I find its quite jurassic, offering no clues for anything newer than whats obviously decade+ old DDS1 drives. And no mention of rewind capabilities for any drive IIRC. So I doubt its connected with my non-rewinding chg-scsi script useage. -- 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: AMLABEL
Jon LaBadie wrote: On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote: Late reply, as this mail (and some other apparently) got stuck in the mailserver... And check the file st.init, where the letters get their meaning. Paul, I'm unfamiliar with the file st.init. Nor do I find one on my system. Did you mean the st.conf file in /kernel/drv? Yes, that's what I mean. (I mixed up Linux /etc/stinit.def and Solaris /kernel/drv/st.conf apparently.) If the st.conf file, I don't find an entries for any lto's I recognize. One poster said it was "builtin" to the driver, another said they had to edit the file and add an entry. Yes, some are built-in into the driver. Non-builtin can be defined in this file. At least, that's what I did to get my Sony AIT-1 tape drive working on Solaris without compresssion. The drive docs would probably still be needed to interpret the entry. You need some numbers to fill in, and I got those from a webpage by the manufacturer of my drive (Sony). Without the numbers, the drive did work, but it would always have hardware compression on (or always off, if I switched the dip-switch in the drive). With the correct numbers, I can control the hw-compression by using the appropriate letter /dev/rmt/0c. -- 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: AMLABEL
On Sunday 20 February 2005 19:07, Spicer, Kevin (MBLEA it) wrote: >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett > >>Paul: That file (st.init/st.conf) doesn't exist on a redhat >> flavored linux install. Nor on a debian sarge based install of >> BDI-4.08, I just checked that one too > >If my Tao box is anything to go by [it should be, Tao is a rebuild > of RHEL] then you need the mt-st package installed which contains > the program stinit and an example config file > /usr/share/doc/mt-st-0.7/stinit.def.examples which you need to copy > to /etc/stinit.def and edit to meet your requirements. You'll > probably also want to put something in your boot time scripts to > run stinit (just call /sbin/stinit without any arguments). Humm, I apparently never did that, Kevin. All I have is the .examples file. Silly Q? Could this be the reason I've blamed amanda for not being able to rewind the tape in a Seagate 4586N changer? And while amanda couldn't rewind it, mt could? Humm, on inspecting that file, I find its quite jurassic, offering no clues for anything newer than whats obviously decade+ old DDS1 drives. And no mention of rewind capabilities for any drive IIRC. So I doubt its connected with my non-rewinding chg-scsi script useage. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
RE: AMLABEL
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett >Paul: That file (st.init/st.conf) doesn't exist on a redhat flavored >linux install. Nor on a debian sarge based install of BDI-4.08, I >just checked that one too If my Tao box is anything to go by [it should be, Tao is a rebuild of RHEL] then you need the mt-st package installed which contains the program stinit and an example config file /usr/share/doc/mt-st-0.7/stinit.def.examples which you need to copy to /etc/stinit.def and edit to meet your requirements. You'll probably also want to put something in your boot time scripts to run stinit (just call /sbin/stinit without any arguments). BMRB International http://www.bmrb.co.uk +44 (0)20 8566 5000 _ This message (and any attachment) is intended only for the recipient and may contain confidential and/or privileged material. If you have received this in error, please contact the sender and delete this message immediately. Disclosure, copying or other action taken in respect of this email or in reliance on it is prohibited. BMRB International Limited accepts no liability in relation to any personal emails, or content of any email which does not directly relate to our business.
Re: AMLABEL
On Tuesday 08 February 2005 11:24, Jon LaBadie wrote: >On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote: >> Jon LaBadie wrote: >> >With the ultrium it is less important about considering HW or SW >> >compression. But be aware that on Solaris whether HW compression >> >is turned on or not is determined by the device you choose. You >> >will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines >> >the properties of the device the driver will set upon opening it. >> > >> >Don't be fooled into assumptions about the various devices. The >> >"c" device is listed as "compressed". But that is the >> > conventional use. There is no certainty that it turns >> > compression on for every device, or that devices without the "c" >> > are no compression. You will even have a "c" device for drives >> > that are not capable of HW compression ;-) Only way to tell is >> > check the docs for the drive and settings for the driver. And >> > then I'd check it if I could. >> >> Indeed. >> >> And check the file st.init, where the letters get their meaning. > >Paul, I'm unfamiliar with the file st.init. >Nor do I find one on my system. >Did you mean the st.conf file in /kernel/drv? > >If the st.conf file, I don't find an entries for any lto's I >recognize. One poster said it was "builtin" to the driver, >another said they had to edit the file and add an entry. > >The drive docs would probably still be needed to interpret >the entry. Paul: That file (st.init/st.conf) doesn't exist on a redhat flavored linux install. Nor on a debian sarge based install of BDI-4.08, I just checked that one too. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.33% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL - might be a bug in amtapetype
On Tue, Feb 08, 2005 at 05:53:43PM +0100, Paul Bijnens wrote: > Jon LaBadie wrote: > > >On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote: > > > >>All that said, when using an LTO drive, you may have hardware > >>compression enabled anyway, because the hw compr algorithm in those > >>drives does not expand uncompressable data. > > > > > >Maybe the amtapetype message should be revised to something like: > > > > hardware compression off (or drive uses a dynamic compression algorithm) > > > > Actually the message is still correct. > amtapetype does detect if hw compr is enabled. > And you would notice the effect if you wrote without software compression. > The fact that the algorithm does not expand data is something else. My misreading of your statement. I missed the "when using an LTO drive" and thought you meant hardware compression might have been on when amtapetype was run but could have been fooled. Sorry bout dat. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL - might be a bug in amtapetype
Jon LaBadie wrote: On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote: All that said, when using an LTO drive, you may have hardware compression enabled anyway, because the hw compr algorithm in those drives does not expand uncompressable data. Maybe the amtapetype message should be revised to something like: hardware compression off (or drive uses a dynamic compression algorithm) Actually the message is still correct. amtapetype does detect if hw compr is enabled. And you would notice the effect if you wrote without software compression. The fact that the algorithm does not expand data is something else. -- 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: AMLABEL - might be a bug in amtapetype
On Tue, Feb 08, 2005 at 04:02:29PM +0100, Paul Bijnens wrote: > > All that said, when using an LTO drive, you may have hardware > compression enabled anyway, because the hw compr algorithm in those > drives does not expand uncompressable data. Maybe the amtapetype message should be revised to something like: hardware compression off (or drive uses a dynamic compression algorithm) -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL
On Tue, Feb 08, 2005 at 10:04:40AM +0100, Paul Bijnens wrote: > Jon LaBadie wrote: > > > >With the ultrium it is less important about considering HW or SW > >compression. But be aware that on Solaris whether HW compression > >is turned on or not is determined by the device you choose. You > >will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines > >the properties of the device the driver will set upon opening it. > > > >Don't be fooled into assumptions about the various devices. The > >"c" device is listed as "compressed". But that is the conventional > >use. There is no certainty that it turns compression on for every > >device, or that devices without the "c" are no compression. You > >will even have a "c" device for drives that are not capable of > >HW compression ;-) Only way to tell is check the docs for the > >drive and settings for the driver. And then I'd check it if I > >could. > > > > Indeed. > > And check the file st.init, where the letters get their meaning. > Paul, I'm unfamiliar with the file st.init. Nor do I find one on my system. Did you mean the st.conf file in /kernel/drv? If the st.conf file, I don't find an entries for any lto's I recognize. One poster said it was "builtin" to the driver, another said they had to edit the file and add an entry. The drive docs would probably still be needed to interpret the entry. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL - might be a bug in amtapetype
On Tue, Feb 08, 2005 at 09:47:17AM -0500, Gil Naveh wrote: > The issue I had was that the first time I run amtapetype the result was a > little off. I would not consider them different at all. capacity, differed by 0.31 percent filemark, differed by 3.41 percent (and only 0.00045% of capacity) speed,differed by 0.06 percent -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL - might be a bug in amtapetype
Gil Naveh wrote: The issue I had was that the first time I run amtapetype the result was a little off. Which was painful because it takes a few hours to run it. yet, it might not be a bug - the reason I put it in the subject was that people would notice it. No, it's not a bug. That's real life with tapes. Not all tapes have exactly the same length. Even the temperature has a measurable influence on tapecapacity. Also when writing to tape, the drive verifies the data, and rewrites any block that contains an uncorrectable error, up to a certain time (15 sometimes). These "soft" errors also take up tape capacity. Furthermore, if the drive has to pause, because the data is not delivered fast enough to the drive, it takes a few inches to stop the tape, rewind and restart again, leaving a little gap between the blocks again. That's why you should specify a little lower value than the one that amtapetype measured. All that said, when using an LTO drive, you may have hardware compression enabled anyway, because the hw compr algorithm in those drives does not expand uncompressable data. Which gives you the opportunity to mix hardware and software compression, using whatever method for each host/disk that fits best (slow host= only hardware compression, slow network = software compression on client etc.) -- 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: AMLABEL - might be a bug in amtapetype
The issue I had was that the first time I run amtapetype the result was a
little off.
Which was painful because it takes a few hours to run it.
yet, it might not be a bug - the reason I put it in the subject was that
people would notice it.
Thx,
gil
-Original Message-
From: Paul Bijnens [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 08, 2005 9:27 AM
To: Gil Naveh
Cc: amanda-users@amanda.org
Subject: Re: AMLABEL - might be a bug in amtapetype
Gil Naveh wrote:
> Hello and thanks,
>
> So it turn out that my suspicious were correct.
Which suspicions?
> After rerunning amtapetype twice on our Solaris 9 server I got the
> configuration for Ultrium2-LTO slightly different and with the new results
> amlabel worked fine :)
> In the first run I got the following result:
> define tapetype unknown-tapetype {
> comment "just produced by tapetype prog (hardware compression off)"
> length 207465 mbytes
> filemark 939 kbytes
> speed 17489 kps
> }
> But Amanda could not identify my tape drive.
>
> In the second run I got the following results:
> define tapetype unknown-tapetype {
> comment "just produced by tapetype prog (hardware compression off)"
> length 206819 mbytes
> filemark 918 kbytes
> speed 17477 kps
> }
> which worked fine.
>
>
> Anyway, I'll publish the results for the Ultrium-LTO2 tape drive on
Amanda's
> website.
And what kind of bug have you found, as the subject seems to imply?
--
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: AMLABEL - might be a bug in amtapetype
Hello and thanks,
So it turn out that my suspicious were correct.
After rerunning amtapetype twice on our Solaris 9 server I got the
configuration for Ultrium2-LTO slightly different and with the new results
amlabel worked fine :)
In the first run I got the following result:
define tapetype unknown-tapetype {
comment "just produced by tapetype prog (hardware compression off)"
length 207465 mbytes
filemark 939 kbytes
speed 17489 kps
}
But Amanda could not identify my tape drive.
In the second run I got the following results:
define tapetype unknown-tapetype {
comment "just produced by tapetype prog (hardware compression off)"
length 206819 mbytes
filemark 918 kbytes
speed 17477 kps
}
which worked fine.
Anyway, I'll publish the results for the Ultrium-LTO2 tape drive on Amanda's
website.
Thx,
gil
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon LaBadie
Sent: Monday, February 07, 2005 10:48 PM
To: amanda-users@amanda.org
Subject: Re: AMLABEL
On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote:
> On Monday 07 February 2005 18:31, Paul Bijnens wrote:
> >Gil Naveh wrote:
> >> Gene - thanks for trying to help,
> >>
> >> Currently the only reason that I can think of is that Amanda has
> >> not read correctly our tape drive so I am re-running
> >> #amtapetype -f /dev/rmt/0n
> >
> >Add an estimate value! And it takes about 5 hours only. Without
> >an estimate it takes a week or so. Like this:
> >
> > amtapetype -f /dev/rmt/0n -e 200g
> >
> >On the other hand, writing a few bytes is enough to see it the drive
> >works.
> >
> >About the problem: you did specify that device in your amanda.conf ?
> >(I believe that was what Gene was hinting about.)
>
> Chuckle, yup. Sometimes I get my tongue tangled up with my eyeteeth,
> and can't see what I'm writing... Corrections in that case are
> always welcome. :-)
With the ultrium it is less important about considering HW or SW
compression. But be aware that on Solaris whether HW compression
is turned on or not is determined by the device you choose. You
will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines
the properties of the device the driver will set upon opening it.
Don't be fooled into assumptions about the various devices. The
"c" device is listed as "compressed". But that is the conventional
use. There is no certainty that it turns compression on for every
device, or that devices without the "c" are no compression. You
will even have a "c" device for drives that are not capable of
HW compression ;-) Only way to tell is check the docs for the
drive and settings for the driver. And then I'd check it if I
could.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL
And assuming that "c" does enable compression on your solaris system the difference (at least on my drives) between "h" and "u" is also the HW compression, though both are highest density (on devices where its offered). On Mon, Feb 07, 2005 at 10:48:27PM -0500, Jon LaBadie wrote: > On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote: > > On Monday 07 February 2005 18:31, Paul Bijnens wrote: > > >Gil Naveh wrote: > > >> Gene - thanks for trying to help, > > >> > > >> Currently the only reason that I can think of is that Amanda has > > >> not read correctly our tape drive so I am re-running > > >> #amtapetype -f /dev/rmt/0n > > > > > >Add an estimate value! And it takes about 5 hours only. Without > > >an estimate it takes a week or so. Like this: > > > > > > amtapetype -f /dev/rmt/0n -e 200g > > > > > >On the other hand, writing a few bytes is enough to see it the drive > > >works. > > > > > >About the problem: you did specify that device in your amanda.conf ? > > >(I believe that was what Gene was hinting about.) > > > > Chuckle, yup. Sometimes I get my tongue tangled up with my eyeteeth, > > and can't see what I'm writing... Corrections in that case are > > always welcome. :-) > > With the ultrium it is less important about considering HW or SW > compression. But be aware that on Solaris whether HW compression > is turned on or not is determined by the device you choose. You > will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines > the properties of the device the driver will set upon opening it. > > Don't be fooled into assumptions about the various devices. The > "c" device is listed as "compressed". But that is the conventional > use. There is no certainty that it turns compression on for every > device, or that devices without the "c" are no compression. You > will even have a "c" device for drives that are not capable of > HW compression ;-) Only way to tell is check the docs for the > drive and settings for the driver. And then I'd check it if I > could. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: AMLABEL
Jon LaBadie wrote: With the ultrium it is less important about considering HW or SW compression. But be aware that on Solaris whether HW compression is turned on or not is determined by the device you choose. You will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines the properties of the device the driver will set upon opening it. Don't be fooled into assumptions about the various devices. The "c" device is listed as "compressed". But that is the conventional use. There is no certainty that it turns compression on for every device, or that devices without the "c" are no compression. You will even have a "c" device for drives that are not capable of HW compression ;-) Only way to tell is check the docs for the drive and settings for the driver. And then I'd check it if I could. Indeed. And check the file st.init, where the letters get their meaning. -- 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: AMLABEL
On Mon, Feb 07, 2005 at 10:06:09PM -0500, Gene Heskett wrote: > On Monday 07 February 2005 18:31, Paul Bijnens wrote: > >Gil Naveh wrote: > >> Gene - thanks for trying to help, > >> > >> Currently the only reason that I can think of is that Amanda has > >> not read correctly our tape drive so I am re-running > >> #amtapetype -f /dev/rmt/0n > > > >Add an estimate value! And it takes about 5 hours only. Without > >an estimate it takes a week or so. Like this: > > > > amtapetype -f /dev/rmt/0n -e 200g > > > >On the other hand, writing a few bytes is enough to see it the drive > >works. > > > >About the problem: you did specify that device in your amanda.conf ? > >(I believe that was what Gene was hinting about.) > > Chuckle, yup. Sometimes I get my tongue tangled up with my eyeteeth, > and can't see what I'm writing... Corrections in that case are > always welcome. :-) With the ultrium it is less important about considering HW or SW compression. But be aware that on Solaris whether HW compression is turned on or not is determined by the device you choose. You will find lots of /dev/rmt/0"xyz" devices. The "xyz" determines the properties of the device the driver will set upon opening it. Don't be fooled into assumptions about the various devices. The "c" device is listed as "compressed". But that is the conventional use. There is no certainty that it turns compression on for every device, or that devices without the "c" are no compression. You will even have a "c" device for drives that are not capable of HW compression ;-) Only way to tell is check the docs for the drive and settings for the driver. And then I'd check it if I could. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: AMLABEL
On Monday 07 February 2005 18:31, Paul Bijnens wrote: >Gil Naveh wrote: >> Gene - thanks for trying to help, >> >> Currently the only reason that I can think of is that Amanda has >> not read correctly our tape drive so I am re-running >> #amtapetype -f /dev/rmt/0n > >Add an estimate value! And it takes about 5 hours only. Without >an estimate it takes a week or so. Like this: > > amtapetype -f /dev/rmt/0n -e 200g > >On the other hand, writing a few bytes is enough to see it the drive >works. > >About the problem: you did specify that device in your amanda.conf ? >(I believe that was what Gene was hinting about.) Chuckle, yup. Sometimes I get my tongue tangled up with my eyeteeth, and can't see what I'm writing... Corrections in that case are always welcome. :-) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.32% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL
Gil Naveh wrote: Gene - thanks for trying to help, Currently the only reason that I can think of is that Amanda has not read correctly our tape drive so I am re-running #amtapetype -f /dev/rmt/0n Add an estimate value! And it takes about 5 hours only. Without an estimate it takes a week or so. Like this: amtapetype -f /dev/rmt/0n -e 200g On the other hand, writing a few bytes is enough to see it the drive works. About the problem: you did specify that device in your amanda.conf ? (I believe that was what Gene was hinting about.) -- 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: AMLABEL
Gene - thanks for trying to help,
Currently the only reason that I can think of is that Amanda has not read
correctly our tape drive so I am re-running
#amtapetype -f /dev/rmt/0n
By tomorrow I'll see what the results are and hopefully it should work...
Any thoughts why amlabel is not working are mostly welcome.
gil
-Original Message-
From: Gene Heskett [mailto:[EMAIL PROTECTED]
Sent: Monday, February 07, 2005 5:52 PM
To: Gil Naveh
Subject: Re: AMLABEL
On Monday 07 February 2005 13:57, Gil Naveh wrote:
>The Operating system is Solaris 9
>and tape drive is under /dev/rmt/0n which is the defualt for
> Solaris.
>
>Thx,
>gil
>
Ok, then thats out of my field of expertise (such as it is), so take
this back to the mailing list where Jon LaBadie seems to be our
resident solaris expert, he can probably help you where I would be
making only SWAG's.
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] Behalf Of Gene Heskett
>Sent: Monday, February 07, 2005 12:43 PM
>To: amanda-users@amanda.org
>Cc: Gil Naveh
>Subject: Re: AMLABEL
>
>On Monday 07 February 2005 10:56, Gil Naveh wrote:
>>Hello,
>>
>>We have a new tape drive but I am unsuccessfully running amlabel.
>>Some background:
>>I was successfully running amlabel on HARD-DISK.
>>I modified amanda.conf file to accommodate the new tape drive
>>specifications:
>> I added the new tape drive spec - which I got through running
>> amtapetype. with the following :
>>
>> define tape type ULTRIUM2-LTO{
>>comment "just produced by tape type prog (hardware compression
>> off)" length 207465 mbytes
>>filemark 939 kbytes
>>speed 17489 kps
>>}
>>
>>and added the following line in the 'main' section in amanda.conf
>> tape type ULTRIUM2-LTO
>>
>>But when I run the command:
>># amlabel DailySet1 DailySet1001
>>The system ask me:
>>#insert tape into slot 1 and press return
>>Even though the tape is already in! - I tried to eject and insert
>> the tape but it again requested me to insert a tape!
>>Is it because Amanda could not identify my tape drive?
>>Or maybe it is related to my previous testing of Amanda with our
>> hard-drive. I successfully labeled our hard-drive and recently I
>> comment it out and labeled the new tape drive?
>
>This would suggest that the tape device really isn't the right tape
>device. Which /dev/??? do you have it set to, and what OS?
>
>>Thanks much,
>>gil
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.32% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: AMLABEL
On Monday 07 February 2005 10:56, Gil Naveh wrote:
>Hello,
>
>We have a new tape drive but I am unsuccessfully running amlabel.
>Some background:
>I was successfully running amlabel on HARD-DISK.
>I modified amanda.conf file to accommodate the new tape drive
>specifications:
> I added the new tape drive spec - which I got through running
> amtapetype. with the following :
>
> define tape type ULTRIUM2-LTO{
>comment "just produced by tape type prog (hardware compression
> off)" length 207465 mbytes
>filemark 939 kbytes
>speed 17489 kps
>}
>
>and added the following line in the 'main' section in amanda.conf
> tape type ULTRIUM2-LTO
>
>But when I run the command:
># amlabel DailySet1 DailySet1001
>The system ask me:
>#insert tape into slot 1 and press return
>Even though the tape is already in! - I tried to eject and insert
> the tape but it again requested me to insert a tape!
>Is it because Amanda could not identify my tape drive?
>Or maybe it is related to my previous testing of Amanda with our
> hard-drive. I successfully labeled our hard-drive and recently I
> comment it out and labeled the new tape drive?
This would suggest that the tape device really isn't the right tape
device. Which /dev/??? do you have it set to, and what OS?
>
>Thanks much,
>gil
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.32% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2005 by Maurice Eugene Heskett, all rights reserved.
Re: amlabel problem.
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17 Feb 2004 14:29:51 +0100 > Don't fear the steps you have to take. > I assume you try to install and setup the most recent AMANDA-release > 2.4.4p2. This should take most of the standard-issues off your > shoulders. > > Here parts of my config-string, maybe it helps you: > > > ./configure --with-user=amanda --with-group=disk --with-owner=amanda > > --with-tape-device=/dev/nst0 --prefix=/usr/local --with-debugging=/tmp/amanda/ > > --with-tape-server= --with-amandahosts > > --with-config=daily --with-configdir=/usr/local/etc/amanda/ > > With this you get a pretty standard-directories-Linux-setup. > Create directories if you need to. > Edit parameters like --with-user to meet your needs ... Thanks, you have been most helpful. Regards, Erik P. Olsen
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 14:19 you wrote to amanda-users: EPO> I realize I have a lot to learn. I am new to Linux and before I can move my EPO> production to Linux I need a reliable backup system. Very reasonable ;) EPO> I am all for standards, so I'll see to that my system complies to EPO> it - as long as I know about it :) Don't fear the steps you have to take. I assume you try to install and setup the most recent AMANDA-release 2.4.4p2. This should take most of the standard-issues off your shoulders. Here parts of my config-string, maybe it helps you: > ./configure --with-user=amanda --with-group=disk --with-owner=amanda > --with-tape-device=/dev/nst0 --prefix=/usr/local --with-debugging=/tmp/amanda/ > --with-tape-server= --with-amandahosts > --with-config=daily --with-configdir=/usr/local/etc/amanda/ With this you get a pretty standard-directories-Linux-setup. Create directories if you need to. Edit parameters like --with-user to meet your needs ... -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17 Feb 2004 14:05:11 +0100 > Hi, Erik, > > on Dienstag, 17. Februar 2004 at 12:06 you wrote to amanda-users: > > >> Do you really want to keep your config-files in /etc/amanda? > >> The default points to /usr/local/etc/amanda, for example. > >> > EPO> Anything wrong in that? That's where the sample config is located. Of course I > EPO> can easily change it if it makes any difference. [snip] > From FHS: > > The /etc directory contains configuration unique to the system and is > required for boot time. > > You see? > > Just configure your AMANDA-sources with > > --with-configdir=/usr/local/etc/amanda/ > > put your configs in there and feel the satisfaction of meeting the > standard ;) I realize I have a lot to learn. I am new to Linux and before I can move my production to Linux I need a reliable backup system. I am all for standards, so I'll see to that my system complies to it - as long as I know about it :) Regards, Erik P. Olsen
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 12:06 you wrote to amanda-users: >> Do you really want to keep your config-files in /etc/amanda? >> The default points to /usr/local/etc/amanda, for example. >> EPO> Anything wrong in that? That's where the sample config is located. Of course I EPO> can easily change it if it makes any difference. I don't know from which sources you compiled on what OS, but for me the default setting for AMANDA-2.4.4p2 (and earlier versions, too) is /usr/local/etc/amanda (it's Linux here). It's not WRONG to put configs in /etc, but it ain't the place they should go when you read the FHS (Filesystem Hierarchy Standard). >From FHS: The /etc directory contains configuration unique to the system and is required for boot time. You see? Just configure your AMANDA-sources with --with-configdir=/usr/local/etc/amanda/ put your configs in there and feel the satisfaction of meeting the standard ;) -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17 Feb 2004 11:54:09 +0100 > Hi, Erik, > > on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: > > EPO> I am installing amanda for the first time and have problems labeling tapes for > EPO> it. I get the error message: > > EPO> amlabel: could not load tapelist "/etc/amanda/normal/tapelist" > [snip] > EPO> modified by the user/administrator. The command I issue from the amanda user is: > > EPO> amlabel /usr/sbin/amlabel normal normal00 > > EPO> and it doesn't help to use the force flag. What am I doing wrong? > > Nothing. Just try a > > touch /etc/amanda/normal/tapelist > > and amlabel again. Thanks, that did it. I now have labels on my tapes and may move on to the next problem. Regards, Erik P. Olsen
Re: amlabel problem.
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17 Feb 2004 11:54:09 +0100 > Hi, Erik, > > on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: > > EPO> I am installing amanda for the first time and have problems labeling tapes for > EPO> it. I get the error message: > > EPO> amlabel: could not load tapelist "/etc/amanda/normal/tapelist" > > Do you really want to keep your config-files in /etc/amanda? > The default points to /usr/local/etc/amanda, for example. > Anything wrong in that? That's where the sample config is located. Of course I can easily change it if it makes any difference. Regards, Erik P. Olsen
Re: amlabel problem.
** Reply to message from "Stefan G. Weichinger" <[EMAIL PROTECTED]> on Tue, 17 Feb 2004 11:55:19 +0100 > Hi, Erik, > > on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: > > EPO> The command I issue from the amanda user is: > > EPO> amlabel /usr/sbin/amlabel normal normal00 > > EPO> and it doesn't help to use the force flag. What am I doing wrong? > > Oops, I shot too fast. > > The syntax is > > /usr/sbin/amlabel normal normal00 > > You had 2 times amlabel > Thanks Stefan, but it was a typo :) I did use the correct syntax. Regards, Erik P. Olsen
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO> The command I issue from the amanda user is: EPO> amlabel /usr/sbin/amlabel normal normal00 EPO> and it doesn't help to use the force flag. What am I doing wrong? Oops, I shot too fast. The syntax is /usr/sbin/amlabel normal normal00 You had 2 times amlabel -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO> I am installing amanda for the first time and have problems labeling tapes for EPO> it. I get the error message: EPO> amlabel: could not load tapelist "/etc/amanda/normal/tapelist" Do you really want to keep your config-files in /etc/amanda? The default points to /usr/local/etc/amanda, for example. But this is not your problem, I assume. EPO> This seems strange since it is the first tape I try to label and therefore EPO> there is no tapelist file and there should not be one. In fact the EPO> documentation says that it will be generated by amlabel and it should not be EPO> modified by the user/administrator. The command I issue from the amanda user is: EPO> amlabel /usr/sbin/amlabel normal normal00 EPO> and it doesn't help to use the force flag. What am I doing wrong? Nothing. Just try a touch /etc/amanda/normal/tapelist and amlabel again. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: AMLABEL Hard-Disk
Jeremy Aldrich wrote: Hello, I am running Red Hat 7.3 w/amanda 2.4.2p2-7 and I am trying to write to a hard-drive > [ ... ] Here is my problem...I keep getting this error when running amlabel: amlabel: could not load slot "1": file:/home/backup/t1: not a device file You need at least version 2.4.3 for the "file" driver. -- Paul @ Home
Re: AMLABEL Hard-Disk
On Thu, Nov 13, 2003 at 03:53:16PM -0700, Jeremy Aldrich wrote:
> Hello,
>
> I am running Red Hat 7.3 w/amanda 2.4.2p2-7 and I am trying to write to a hard-drive
> I have setup amanda to write to hard-drive like so:
> #AMANDA.CONF
> dumpcycle 6 days# the number of days in the normal dump cycle
> runspercycle 6 # the number of amdump runs in dumpcycle days
> tapecycle 3 tapes # the number of tapes in rotation
> tpchanger "chg-multi" # the tape-changer glue script
> #tapedev "/dev/null"# the no-rewind tape device to be used
> #rawtapedev "/dev/null" # the raw device to be used (ftape only)
> changerfile "/etc/amanda/test/chg-multi.conf"
> #changerdev "/dev/null"
> #tapetype HP-DAT# what kind of tape it is (see tapetypes below)
> tapetype full_to_disk_test # what kind of tape it is (see tapetypes below)
> define tapetype full_to_disk_test {
>comment "TEST FULL BACKUP TO DISK"
>length 9000 mbytes
> }
> #CHG-MULTI.CONF
> multieject 0
> gravity 0
> needeject 0
> ejectdelay 0
> statefile /etc/amanda/test/changer-status
> firstslot 1
> lastslot 3
> slot 1 file:/home/backup/t1
> slot 2 file:/home/backup/t2
> slot 3 file:/home/backup/t3
>
> I then put the amanda user and disk group priveleges on the amanda directories as
> well as the backup directories and have them all set with 766 permissions.
>
> Here is my problem...I keep getting this error when running amlabel:
> amlabel: could not load slot "1": file:/home/backup/t1: not a device file
>
> Does anyone have an idea as to what may be wrong?
> Thanks for any time that you spend on this.
I don't see any mention of creating a "data" sub-directories
in your t1 - t3 directories.
And do you really mean permissions 755, not 766? I hope so.
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel - segmentationfault
On Tue, Sep 30, 2003 at 09:26:35AM +0200, Mats Blomstrand wrote: > (Thanks Jon LaBadie and Paul Bijnens for your useful suggestion on my last > question) > > When i run amlabel it quits with an seg-fault. Like this: > > -bash-2.05b$ amlabel normal normal01 slot 1 > labeling tape in slot 1 (/dev/nst0): > rewinding, reading label normal01 > rewinding, writing label normal01, checking labelSegmentation fault > > -bash-2.05b$ amlabel normal normal01 slot 1 > amlabel: label normal01 already on a tape > > -bash-2.05b$ amlabel normal normal02 slot 2 > labeling tape in slot 2 (/dev/nst0): > rewinding, reading label normal02 > rewinding, writing label normal02, checking labelSegmentation fault > > Should i be worried? (Its an redhat 9 with amanda 2.4.4) Yes. Programs should not segmentation fault. Probably a core file was left behind. In what directory I'm not certain. Find that and run the file command on it to determine which program was faulting/core dumping. It may have been amlabel or a program amlabel runs. An example: # file /usr/dt/bin/core /usr/dt/bin/core: ELF 32-bit LSB core file 80386 Version 1, from 'dtterm' In this case it was the program "dtterm" that core dumped. BTW make sure the core file you check was actually from the amlabel run. One check is to remove it, run amlabel again to make it segment fault, and seeing if the core file reappears. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: amlabel not detecting a tape in device? BSDI5 and Tape.h
Thanks for your responses!
However it seems that the trouble is getting Amanda to build properly on
BSDi 5. There were some warnings that I originally ignored during the
configure script phase that I believe are impacting the way the binaries
are behaving.
The configure script doesn't fail, and the build process looks clean.
Building 2.4.4p1 on BSDi configure gives the following warnings:
configure: WARNING: netinet/ip.h: present but cannot be compiled
configure: WARNING: netinet/ip.h: check for missing prerequisite
headers?
configure: WARNING: netinet/ip.h: proceeding with the preprocessor's
result
Config.log detail:
/usr/include/netinet/ip.h:70: field `ip_src' has incomplete type
/usr/include/netinet/ip.h:70: field `ip_dst' has incomplete type
/usr/include/netinet/ip.h:152: syntax error before `n_int32_t'
/usr/include/netinet/ip.h:154: field `ipt_addr' has incomplete type
/usr/include/netinet/ip.h:155: syntax error before `n_int32_t'
configure: WARNING: sys/mount.h: present but cannot be compiled
configure: WARNING: sys/mount.h: check for missing prerequisite headers?
configure: WARNING: sys/mount.h: proceeding with the preprocessor's
result
Config.log detail:
/usr/include/sys/ucred.h:48: `NGROUPS' undeclared here (not in a
function)
/usr/include/sys/ucred.h:68: `MAXLOGNAME' undeclared here (not in a
function)
configure: WARNING: sys/tape.h: present but cannot be compiled
configure: WARNING: sys/tape.h: check for missing prerequisite headers?
configure: WARNING: sys/tape.h: proceeding with the preprocessor's
result
config.log Detail:
/usr/include/sys/tape.h:18: field `tp_dev' has incomplete type
/usr/include/sys/tape.h:23: syntax error before `tpr_t'
/usr/include/sys/tape.h:27: warning: `struct buf' declared
inside parameter list/usr/include/sys/tape.h:27: warning: its scope is
onlythis definition or declaration, which is probably not what you
want.
When building Amanda-2.5.0-20030716, two of these warnings go away.
However, I'm am still left with the tape.h warning.
checking sys/tape.h usability... no
checking sys/tape.h presence... yes
configure: WARNING: sys/tape.h: present but cannot be compiled
configure: WARNING: sys/tape.h: check for missing prerequisite headers?
configure: WARNING: sys/tape.h: proceeding with the preprocessor's
result
config.log detail:
/usr/include/sys/tape.h:18: field `tp_dev' has incomplete type
/usr/include/sys/tape.h:23: syntax error before `tpr_t'
/usr/include/sys/tape.h:27: warning: `struct buf' declared inside
parameter list/usr/include/sys/tape.h:27: warning: its scope is only
this definition or declaration, which is probably not what you want.
Reviewing the configure script in either release I can see that there is
a case statement that checks OS type. This case statement does not
include bsdi5*. I have edited the configure script to reflect the new
version but I am not sure that the options for Bsdi4 are appropriate for
Bsdi5:
bsdi4* | bsdi5*)
lt_cv_deplibs_check_method='file_magic ELF [0-9][0-9]*-bit [ML]SB
(shared object|dynamic lib)'
lt_cv_file_magic_cmd='/usr/bin/file -L'
lt_cv_file_magic_test_file=/shlib/libc.so
;;
and:
bsdi4* | bsdi5*)
version_type=linux
need_version=no
library_names_spec='${libname}${release}.so$versuffix
${libname}${release}.so$major $libname.so'
soname_spec='${libname}${release}.so$major'
finish_cmds='PATH="\$PATH:/sbin" ldconfig $libdir'
shlibpath_var=LD_LIBRARY_PATH
sys_lib_search_path_spec="/shlib /usr/lib /usr/X11/lib
/usr/contrib/lib /lib /usr/local/lib"
sys_lib_dlsearch_path_spec="/shlib /usr/lib /usr/local/lib"
export_dynamic_flag_spec=-rdynamic
# the default ld.so.conf also contains /usr/contrib/lib and
# /usr/X11R6/lib (/usr/X11 is a link to /usr/X11R6), but let us allow
# libtool to hard-code these into programs
;;
This does not fix the tape.h warning.
I assume that this is the cause for Amanda's inability to correctly
access the device (and not detect a tape).
Any insight would be greatly appreciated...
Thanks in Advance,
-Chris
Re: amlabel not detecting a tape in device?
On Wed, Aug 20, 2003 at 01:24:07PM -0700, Chris Fairman wrote: > Hi, > > > I'm having problems getting Amanda amanda-2.4.4p1 to > install/work on BSDi 5. I've read and re-read all the documentation, and > I'm using this list as a 'last resort.' > > > I'm hoping this may be just a simple configuration issue: > > I can successfully build and install the Amanda > package, but when running amlabel, it asks: "insert tape into slot and > press return" I do so and press but the message repeats itself. > I need to ctrl-c to get out of it. I am using a VXA-2 Tape Drive. > > > Things I have tried: > > > I can run mt and receive tape drive information as user: amanda Obvious "is the plug in the wall" type questions first. You say you can get status back from mt. Can you also write and read to the tape drive. And then use mt to move forward to the next file, or rewind, or ... Say you do this: $ mt -f /dev/nrst0 rewind $ cat /tmp/* | dd of=/dev/nrst0 bs=32k $ tar -cf /dev/nrst0 /etc $ tar -cf /dev/nrst0 /bin $ mt -f /dev/nrst0 rewind $ mt -f /dev/nrst0 fsf 1 $ tar -tvf /dev/nrst0 Do you get an "ls -l" type listing of your /etc directory? If so, then amanda should be able to work with your drive. And we have other things to consider. :< jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel i/o error
If there is not a label on the tape in the first time - i.e brand new tape i have seen i/o errors and the tape gets written fine. It is also perfectly usable. This happenned to me with LTO drives Tom > Pascal Robert wrote: > > > So I started to run amlabel on my 5 tapes. The first two went ok, but > > 3, 4 and 5 gave me this error: > > > > amlabel: tape_rewind: rewinding tape: /dev/nst0: Input/output error > > > > But it did create a new label, and 'amcheck' don't throw any errors. > > What can generate this error ? Thanks. > > Maybe hardware problems (bad cabling, scsi termination etc). > Did you sacrifice the chicken before connecting your drive? > Any kernel messages in /var/log/messages or dmesg? > > > > -- > 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: amlabel i/o error
Pascal Robert wrote: So I started to run amlabel on my 5 tapes. The first two went ok, but 3, 4 and 5 gave me this error: amlabel: tape_rewind: rewinding tape: /dev/nst0: Input/output error But it did create a new label, and 'amcheck' don't throw any errors. What can generate this error ? Thanks. Maybe hardware problems (bad cabling, scsi termination etc). Did you sacrifice the chicken before connecting your drive? Any kernel messages in /var/log/messages or dmesg? -- 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: amlabel
On Thu, Jul 17, 2003 at 11:16:12AM -0700, Joseph Andorful wrote: > I'm trying to run amlabel, but when I type in the > command, it says amlabel: could not load slot "1": > chg-multi: slot is empty You have provided little information which with to assist you. Here is a suggested approach. Amanda is set up in layers, going from a simpler, single task program to more complex, multi-task programs. These programs may be from amanda or from the system. Each may use one or more configuration files. For example, in my amanda setup some of the layers might include: CommandPurpose Config File mt or ammt manipulate tape none or amanda.conf for tape dev mtxmanipulate changer none chg-mtxinterface to mtxamanda.conf and changer.conf amtape interface to mt/mtx amanda.conf and changer.conf amdump, amrestore, amrecover, amcheck, amlabel, ... various tasks all the above and more You have in your config a similar stack but with chg-multi and ??? But I suspect you have not tested and debugged all the layers leading up to the amlabel/amdump layer. To simplify your debugging you should test and exercise all the lower layer commands before tackling the more complex commands. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel returning "Read-only file system" error
On Thu, 13 Mar 2003 at 2:09pm, Ron Bauman wrote amlabel: writing label: Read-only file system It's indeed very weird. Two possibilities: 1. Are you sure you are specifying the correct tapedevice in the amanda configuration? There is no "file system" on a tape, maybe you specified "file:..." or something. Investigate with: amgetconf YourConfig tpchanger amgetconf YourConfig tapedev 2. Do you have the drive allowed for variable blocksize? (of fixed at 32k is fine too). I've had some problems with reading/writing tapes with incompatible blocksizes (but never seen "read-only"). Try it out with "dd obs=...". If that one works with blocksize, it's something else. -- 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: amlabel returning "Read-only file system" error
On Thu, Mar 13, 2003 at 02:09:54PM -0500, Ron Bauman wrote: > Hi. I've installed Amanda 2.4.4 on Redhat Linux 7.3. We are using a > Spectra Logic TreeFrog 2000. I've got the changer working in Amanda > and can read/write tapes using mt and tar. When I attempt to use > amlabel to label the tapes I get: > > [EMAIL PROTECTED] daily]# amlabel -f daily D001 > + amlabel -f daily D001 > labeling tape in slot 01 (/dev/nst0): > rewinding, reading label, not an amanda tape > rewinding, writing label D001 > amlabel: writing label: Read-only file system > [EMAIL PROTECTED] daily] Write protect tab on tab is blocking writes? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: amlabel returning "Read-only file system" error
No. It's the same tape I'm able to write/read with tar. That's what is making it frustrating. Ron -Original Message- From: Joshua Baker-LePain [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2003 3:28 PM To: Ron Bauman Cc: [EMAIL PROTECTED] Subject: Re: amlabel returning "Read-only file system" error On Thu, 13 Mar 2003 at 2:09pm, Ron Bauman wrote > Hi. I've installed Amanda 2.4.4 on Redhat Linux 7.3. We are using a > Spectra Logic TreeFrog 2000. I've got the changer working in Amanda > and can read/write tapes using mt and tar. When I attempt to use > amlabel to label the tapes I get: > > [EMAIL PROTECTED] daily]# amlabel -f daily D001 > + amlabel -f daily D001 > labeling tape in slot 01 (/dev/nst0): > rewinding, reading label, not an amanda tape > rewinding, writing label D001 > amlabel: writing label: Read-only file system > [EMAIL PROTECTED] daily] Is that particular tape write protected? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amlabel returning "Read-only file system" error
On Thu, 13 Mar 2003 at 2:09pm, Ron Bauman wrote > Hi. I've installed Amanda 2.4.4 on Redhat Linux 7.3. We are using a > Spectra Logic TreeFrog 2000. I've got the changer working in Amanda > and can read/write tapes using mt and tar. When I attempt to use > amlabel to label the tapes I get: > > [EMAIL PROTECTED] daily]# amlabel -f daily D001 > + amlabel -f daily D001 > labeling tape in slot 01 (/dev/nst0): > rewinding, reading label, not an amanda tape > rewinding, writing label D001 > amlabel: writing label: Read-only file system > [EMAIL PROTECTED] daily] Is that particular tape write protected? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: amlabel
Hi, I get error with rpm version of amanda (2.4.2P2-9). I compile version 2.4.4 of amanda and all working fine thanks. -- Alexandre FOUREY Consultant Architecture de Systèmes T-Systems Soleri Groupe Deutsche Telekom Notre métier : la convergence informatique et télécoms Convergence is our Business - tél. : +33 (0)4 37 65 24 34 fax : +33 (0)4 37 65 24 24 mob : +33 (0)6 61 92 43 00 - www.t-systems.fr Hi, Which release of amanda? What's in amanda.conf What's in your changer conf file? Jean-Louis On Tue, Mar 11, 2003 at 10:01:00AM +0100, afourey wrote: I would like to create virtual tape on hard disk. mkdir -p /data/backups/tape01/data chown -R amanda.disk /data/backups chmod -R 770 /data/backups amlabel -f DailySet1 DailySet101 I get the following error : amlabel: could not load slot "current": file:/data/backups/tape01: not a device file Please help
Re: amlabel
Hi, Which release of amanda? What's in amanda.conf What's in your changer conf file? Jean-Louis On Tue, Mar 11, 2003 at 10:01:00AM +0100, afourey wrote: > I would like to create virtual tape on hard disk. > > mkdir -p /data/backups/tape01/data > chown -R amanda.disk /data/backups > chmod -R 770 /data/backups > amlabel -f DailySet1 DailySet101 > > I get the following error : > amlabel: could not load slot "current": file:/data/backups/tape01: not a > device file > > Please help > > -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amlabel: reading label: Value too large for defined data type
Hello Jean-Louis,
Thank you, the tape's variable block size was exactly the problem,
I have recompiled amanda with --with-max-tapeblocksize=32, and amlabel
is now working correctly.
Thanks again,
Tim
On Tue, 28 Jan 2003, Jean-Louis Martineau wrote:
> Hi Tim,
>
> Your tape drive is set to variable block size?
> You didn't set '--with-maxtapeblocksize=' at configure?
> Could you use 'dd if=/dev/nst0 of=/dev/null bs=32k' to read the tape.
> Try erasing your tape.
>
> Jean-Louis
>
> On Tue, Jan 28, 2003 at 12:13:31PM -0500, Tim Souder wrote:
> > Hello everyone,
> >
> > When I attempt to use amlabel to label a tape on a Tandberg/Quantum
> > SDLT 220, it produces the following error:
> >
> > [amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100
> > rewinding, reading label, reading label: Value too large for defined data type
> > rewinding, writing label DailySet100, checking label
> > amlabel: reading label: Value too large for defined data type
> >
> > On the same tape, (after a mt rewind), I attempted a dump/restore check to
> > the same tape on the same drive:
> >
> > [root@Jupiter amanda]# dump -0u -a -f /dev/nst0 -L "Jupiter:/" /
> > DUMP: Date of this level 0 dump: Tue Jan 28 11:56:00 2003
> > DUMP: Dumping /dev/sda5 (/) to /dev/nst0
> > DUMP: Added inode 7 to exclude list (resize inode)
> > DUMP: Label: Jupiter:/
> > DUMP: mapping (Pass I) [regular files]
> > DUMP: mapping (Pass II) [directories]
> > DUMP: estimated 81489 tape blocks.
> > DUMP: Volume 1 started with block 1 at: Tue Jan 28 11:56:01 2003
> > DUMP: dumping (Pass III) [directories]
> > DUMP: dumping (Pass IV) [regular files]
> > DUMP: Closing /dev/nst0
> > DUMP: Volume 1 completed at: Tue Jan 28 11:56:17 2003
> > DUMP: Volume 1 82180 tape blocks (80.25MB)
> > DUMP: Volume 1 took 0:00:16
> > DUMP: Volume 1 transfer rate: 5136 kB/s
> > DUMP: 82180 tape blocks (80.25MB) on 1 volume(s)
> > DUMP: finished in 14 seconds, throughput 5870 kBytes/sec
> > DUMP: Date of this level 0 dump: Tue Jan 28 11:56:00 2003
> > DUMP: Date this dump completed: Tue Jan 28 11:56:17 2003
> > DUMP: Average transfer rate: 5136 kB/s
> > DUMP: DUMP IS DONE
> > [root@Jupiter amanda]# restore -C -D / -f /dev/st0
> > restore: Tape read error on first record
> > restore interrupted, continue? [yn] n
> > [root@Jupiter amanda]# mt rewind
> > [root@Jupiter amanda]# restore -C -D / -f /dev/nst0
> > Dump date: Tue Jan 28 11:56:00 2003
> > Dumped from: the epoch
> > Level 0 dump of / on Jupiter:/dev/sda5
> > Label: Jupiter:/
> > filesys = /
> > ./etc/dumpdates: tape and disk copies are different
> > Some files were modified!
> > [root@Jupiter amanda]# mt rewind
> >
> > Then, i went back to the amanda user, and attempted amlabel and got the
> > same results:
> >
> > [amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100
> > rewinding, reading label, reading label: Value too large for defined data type
> > rewinding, writing label DailySet100, checking label
> > amlabel: reading label: Value too large for defined data type
> >
> > Just to be sure, the amanda:backup user has read/write access to /dev/nst0:
> >
> > [amanda@Jupiter amanda]$ ls -l /dev/tape /dev/nst0
> > crw-rw1 root backup 9, 128 Apr 11 2002 /dev/nst0
> > lrwxrwxrwx1 root root4 Jan 3 12:34 /dev/tape -> nst0
> >
> > ...and the tape definition that I use for the SDLT 220 is:
> > tapetype SDLT220# what kind of tape it is (see tapetypes below)
> >
> > define tapetype SDLT220 {
> > comment "Tandberg SDLT-220"
> > length 96868 mbytes
> > filemark 0 kbytes
> > speed 9142 kps
> > }
> >
> > Does anyone have any ideas? I've tried google searching to no avail...
> >
> > Thanks in advance for all of your help,
> >
> > Tim Souder
> > [EMAIL PROTECTED]
>
>
Re: amlabel: reading label: Value too large for defined data type
Hi Tim,
Your tape drive is set to variable block size?
You didn't set '--with-maxtapeblocksize=' at configure?
Could you use 'dd if=/dev/nst0 of=/dev/null bs=32k' to read the tape.
Try erasing your tape.
Jean-Louis
On Tue, Jan 28, 2003 at 12:13:31PM -0500, Tim Souder wrote:
> Hello everyone,
>
> When I attempt to use amlabel to label a tape on a Tandberg/Quantum
> SDLT 220, it produces the following error:
>
> [amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100
> rewinding, reading label, reading label: Value too large for defined data type
> rewinding, writing label DailySet100, checking label
> amlabel: reading label: Value too large for defined data type
>
> On the same tape, (after a mt rewind), I attempted a dump/restore check to
> the same tape on the same drive:
>
> [root@Jupiter amanda]# dump -0u -a -f /dev/nst0 -L "Jupiter:/" /
> DUMP: Date of this level 0 dump: Tue Jan 28 11:56:00 2003
> DUMP: Dumping /dev/sda5 (/) to /dev/nst0
> DUMP: Added inode 7 to exclude list (resize inode)
> DUMP: Label: Jupiter:/
> DUMP: mapping (Pass I) [regular files]
> DUMP: mapping (Pass II) [directories]
> DUMP: estimated 81489 tape blocks.
> DUMP: Volume 1 started with block 1 at: Tue Jan 28 11:56:01 2003
> DUMP: dumping (Pass III) [directories]
> DUMP: dumping (Pass IV) [regular files]
> DUMP: Closing /dev/nst0
> DUMP: Volume 1 completed at: Tue Jan 28 11:56:17 2003
> DUMP: Volume 1 82180 tape blocks (80.25MB)
> DUMP: Volume 1 took 0:00:16
> DUMP: Volume 1 transfer rate: 5136 kB/s
> DUMP: 82180 tape blocks (80.25MB) on 1 volume(s)
> DUMP: finished in 14 seconds, throughput 5870 kBytes/sec
> DUMP: Date of this level 0 dump: Tue Jan 28 11:56:00 2003
> DUMP: Date this dump completed: Tue Jan 28 11:56:17 2003
> DUMP: Average transfer rate: 5136 kB/s
> DUMP: DUMP IS DONE
> [root@Jupiter amanda]# restore -C -D / -f /dev/st0
> restore: Tape read error on first record
> restore interrupted, continue? [yn] n
> [root@Jupiter amanda]# mt rewind
> [root@Jupiter amanda]# restore -C -D / -f /dev/nst0
> Dump date: Tue Jan 28 11:56:00 2003
> Dumped from: the epoch
> Level 0 dump of / on Jupiter:/dev/sda5
> Label: Jupiter:/
> filesys = /
> ./etc/dumpdates: tape and disk copies are different
> Some files were modified!
> [root@Jupiter amanda]# mt rewind
>
> Then, i went back to the amanda user, and attempted amlabel and got the
> same results:
>
> [amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100
> rewinding, reading label, reading label: Value too large for defined data type
> rewinding, writing label DailySet100, checking label
> amlabel: reading label: Value too large for defined data type
>
> Just to be sure, the amanda:backup user has read/write access to /dev/nst0:
>
> [amanda@Jupiter amanda]$ ls -l /dev/tape /dev/nst0
> crw-rw1 root backup 9, 128 Apr 11 2002 /dev/nst0
> lrwxrwxrwx1 root root4 Jan 3 12:34 /dev/tape -> nst0
>
> ...and the tape definition that I use for the SDLT 220 is:
> tapetype SDLT220# what kind of tape it is (see tapetypes below)
>
> define tapetype SDLT220 {
> comment "Tandberg SDLT-220"
> length 96868 mbytes
> filemark 0 kbytes
> speed 9142 kps
> }
>
> Does anyone have any ideas? I've tried google searching to no avail...
>
> Thanks in advance for all of your help,
>
> Tim Souder
> [EMAIL PROTECTED]
--
Jean-Louis Martineau email: [EMAIL PROTECTED]
Departement IRO, Universite de Montreal
C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529
Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: amlabel: reading label: Value too large for defined data type
Hello Gene, Unfortunately, the labelstr parameter is: labelstr "^DailySet1[0-9][0-9]*$" Thanks though, Tim On Tue, 28 Jan 2003, Gene Heskett wrote: > On Tuesday 28 January 2003 12:13, Tim Souder wrote: > >Hello everyone, > > > >When I attempt to use amlabel to label a tape on a > > Tandberg/Quantum SDLT 220, it produces the following error: > > > >[amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100 > >rewinding, reading label, reading label: Value too large for > > defined data type rewinding, writing label DailySet100, checking > > label > >amlabel: reading label: Value too large for defined data type > > If your amanda.conf describes the labelstring as the default, like > this: > > labelstr "^DailySet1-[0-9][0-9]*$" > > then the real problem is the missing '-' between DailySet1 and the > rest of the number. If you intended to label the 100th tape, then > the applied label should have been: "DailySet1-100". > >
Re: amlabel: reading label: Value too large for defined data type
On Tuesday 28 January 2003 12:13, Tim Souder wrote: >Hello everyone, > >When I attempt to use amlabel to label a tape on a > Tandberg/Quantum SDLT 220, it produces the following error: > >[amanda@Jupiter amanda]$ amlabel -f DailySet1 DailySet100 >rewinding, reading label, reading label: Value too large for > defined data type rewinding, writing label DailySet100, checking > label >amlabel: reading label: Value too large for defined data type If your amanda.conf describes the labelstring as the default, like this: labelstr "^DailySet1-[0-9][0-9]*$" then the real problem is the missing '-' between DailySet1 and the rest of the number. If you intended to label the 100th tape, then the applied label should have been: "DailySet1-100". -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
Re: amlabel: Operation not permitted
On Wed, Sep 11, 2002 at 05:21:39PM -0400, Caitlyn M. Martin wrote: > > Hi, everyone, > > I'm trying to setup a new backup server running Red Hat and Amanda > 2.4.2p2. I'm using an Exabyte VXA-1 RakPaq, basically two LVD SCSI > VXA-1 tape drives which I have daisy chained together. vxaTool reports > that the first drive is /dev/sga and the second is /dev/sgb. I can > access either drive with mt or vxaTool, so I believe my issue is with > Amanda. > > I'm trying to label a tape before doing my first (test) backup with the > command: > > su -c amanda "amlabel DailySet1 DailySet101" > > The system first responds: > > rewinding > amlabel: rewinding tape: Operation not permitted > > I suspect a permissions issue as I can rewind the tape as root using > vxaTool. Also, if I run the amlabel command as root it will say: > > amlabel: running as user "root" instead of "amanda" > > I know I'm doing something simple and stupid wrong, but for the life of > me I can't see what. I can post relevant sections of my amanda.conf > file if it will help. > > I've setup Amanda before, but it was on Solaris and it was a few years > ago. Any clues where I'm being thickheaded? What are the permissions on sga and sgb and vxaTool? $ ls -l -L /dev/sga /dev/sgb What operations can you perform with mt. Is rewind one of them? Are sga and sgb the actual tape read and write devices or the changer mechanisms? What chg-XXX driver are you using and as amanda, can you cd to the config dir, then run chg-XXX status or info or slot # or ???. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel question
On Tuesday 10 September 2002 14:29, Galen Johnson wrote: >woohoo...I'm actually making progress...amcheck actually completed >mostly without errors (mainly because I stupidly left the disklist > at the default that came with amanda...silly...silly). I also > forgot to label my tapes (I am currently in the process of this). > Now the question...I have a 7 tape magazine...I'm gonna have to > set runtapes to 2...I was planning to start sequentially labeling > the tapes (daily000, daily001,...), should I label them 0-6 and > then label the next magazine 7-13 or some other scheme?...docs > aren't very clear on that. > >I still am not too clear on the dumpcycle, runcycle, tapecycle, >motorcycle, etc rules yet...alas more perusing of docs... > >=G= If you leave the scheduling to amanda, and not overpower her with the first disklist, you'll find that a good sized system can still be put on a single DDS2, 4 gig tape. I'm doing a 46 gig drive here on one tape a night. Amanda will adjust the schedule to level out the tape useage from night to night. Don't use hardware compression because that hides the tape size from amanda. Use software compression, which is usually much better at smunching tings anyway, and amanda who counts bytes going to the drive, will then know pretty exactly how much tape is available. Don't compress that which is already compressed, it will expand (usually). Label the tapes sequentialy, using a pattern you define in amanda.conf. See the current define in there now. Dumpcycle is how long amanda has to do a level 0 on everything in the disklist, '1 week' or '7 days' is typical. Motorcycle? I'm not sure amanda has that option, or even if I ever had a girl named Amanda on the princess pad. But they're fun, I put half a million+ miles on several down thru the years, at one point using one for a chair car for a couple of years, rain, snow or shine. Just make sure you've got a hard hat you'd trust your brains to, you never know when you might use it up. I used up 2 of them in 40 some years. Snell rated hats obviously. Tapecycle is how many tapes in the rotation, and one should have at least 2*runtapes*dumpcycle(in days) in the rotation. 3x is prefered by some including me in order to have at least 2 good fulls on tap if needed. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.14% setiathome rank, not too shabby for a WV hillbilly
Re: amlabel error
On Thursday 25 July 2002 17:44, Keith Nasman wrote: >On Thu, 25 Jul 2002, Gene Heskett wrote: >> On Thursday 25 July 2002 15:40, Keith Nasman wrote: >> >[root@presto DailySet1]# su amanda -c "amlabel DailySet1 >> > DailySet113" rewinding, reading label, reading label: Cannot >> > allocate memory rewinding, writing label DailySet113, checking >> > label, done. >> > >> >I assume that the tape got labeled correctly. Can anyone >> > enlighten me on the memory error? >> >> Hummm, not brand new tapes? Maybe a tape that was used with >> another backup util, probably proprietary? > >These are not brand new tapes. Leftovers from ArcServe for NT. > >> What it sounds like is that when amanda tried to read the >> initial header from the tape, its encountering a totally >> humungous value the tapes block size and can't allocate that >> much memory. >> >> My best guess... >> >> Anyway, dd can retrieve the tape label with this pair of >> commands: #>mt -f /dev/tape_device rewind >> #>dd if = /dev/tape_device count = 1 >> which should disgorge the first block of 512 bytes to the >> screen, showing you the label as written. > >Hmmm, this is what I get. > >[root@presto amanda]# mt -f /dev/nst0 rewind >[root@presto amanda]# dd if=/dev/nst0 count=1 >dd: reading `/dev/nst0': Cannot allocate memory >0+0 records in >0+0 records out > Odd indeed, this is what you should have gotten provided the tape was rewound. [root@coyote root]# dd if=/dev/st0 bs=512 count=1 AMANDA: TAPESTART DATE 20020725 TAPE DailySet1-11 1+0 records in 1+0 records out >yet, I get this output from amcheck > >[root@presto amanda]# su amanda -c "amcheck DailySet1" >Amanda Tape Server Host Check >- >Holding disk /var/tmp: 127389 KB disk space available, that's > plenty NOTE: skipping tape-writable test >Tape DailySet114 label ok > > > >so it looks like the tape label is fine. That it does indeed, so I'm scratching my aging head as it doesn't make 100% sense. Any other guesses I'd make ATM would be a very poor version of a (S)WAG. > > >Keith -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: amlabel error
On Thu, 25 Jul 2002, Gene Heskett wrote: > On Thursday 25 July 2002 15:40, Keith Nasman wrote: > >[root@presto DailySet1]# su amanda -c "amlabel DailySet1 > > DailySet113" rewinding, reading label, reading label: Cannot > > allocate memory rewinding, writing label DailySet113, checking > > label, done. > > > >I assume that the tape got labeled correctly. Can anyone enlighten > > me on the memory error? > > Hummm, not brand new tapes? Maybe a tape that was used with another > backup util, probably proprietary? > These are not brand new tapes. Leftovers from ArcServe for NT. > What it sounds like is that when amanda tried to read the initial > header from the tape, its encountering a totally humungous value > the tapes block size and can't allocate that much memory. > > My best guess... > > Anyway, dd can retrieve the tape label with this pair of commands: > #>mt -f /dev/tape_device rewind > #>dd if = /dev/tape_device count = 1 > which should disgorge the first block of 512 bytes to the screen, > showing you the label as written. > > Hmmm, this is what I get. [root@presto amanda]# mt -f /dev/nst0 rewind [root@presto amanda]# dd if=/dev/nst0 count=1 dd: reading `/dev/nst0': Cannot allocate memory 0+0 records in 0+0 records out yet, I get this output from amcheck [root@presto amanda]# su amanda -c "amcheck DailySet1" Amanda Tape Server Host Check - Holding disk /var/tmp: 127389 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet114 label ok so it looks like the tape label is fine. Keith
Re: amlabel error
On Thursday 25 July 2002 15:40, Keith Nasman wrote: >O' gurus, > >I initially labeled 10 tapes for my rotation and now I am labeling > another 10. My first couple of tapes got labeled fine but now I'm > getting this: > >[root@presto DailySet1]# su amanda -c "amlabel DailySet1 > DailySet113" rewinding, reading label, reading label: Cannot > allocate memory rewinding, writing label DailySet113, checking > label, done. > >I assume that the tape got labeled correctly. Can anyone enlighten > me on the memory error? Hummm, not brand new tapes? Maybe a tape that was used with another backup util, probably proprietary? What it sounds like is that when amanda tried to read the initial header from the tape, its encountering a totally humungous value the tapes block size and can't allocate that much memory. My best guess... Anyway, dd can retrieve the tape label with this pair of commands: #>mt -f /dev/tape_device rewind #>dd if = /dev/tape_device count = 1 which should disgorge the first block of 512 bytes to the screen, showing you the label as written. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.08% setiathome rank, not too shabby for a WV hillbilly
Re: amlabel problems
On Thu, Jul 11, 2002 at 02:30:20PM -0600, Trevor Morrison wrote: > > ... . When I run amlabel I > get this output: > > rewinding, reading label, no tape online I would interpret this as saying the system does not believe there is a tape in the drive. Why it is saying that I don't know. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amlabel error
Joshua Hoblitt <[EMAIL PROTECTED]> writes: > Hello, I'm installing amanda for the first time on solaris 8 with a dlt > 8000 drive. It seems like I need to manualing rewind the tape drive when > incerting a fresh tape. Otherwise I get this error - why > would mt rewind the drive and amlabel only on the 2nd try? > > > bash-2.01# su amanda -c "amlabel daily kolea04" rewinding > amlabel: tape_rewind: tape open: /dev/rmt/0cn: I/O error i got this error just after put the tape in. i have to wait a few seconds beforce launching amlabel try to wait a bit more. -- Fabien Seisen [EMAIL PROTECTED] dakol@opn GnuPG ID 1024D/112189D8
Re: amlabel & ftape
hello again! yes, and i am using it ( ln -s /dev/nqft0 /dev/tape ). but meanwhile i have found these lines in /var/log /messeges : Apr 22 17:18:17 tester kernel: [141] zftape-read.c (check_read_access) - req_len 32768 not a multiple of block size 10240. Apr 22 17:18:18 tester kernel: [142] zftape-write.c (check_write_access) - write-count 32768 must be multiple of block-size 10240. Apr 22 17:18:18 tester kernel: [143] zftape-write.c (_zft_write) - check_write_access(req_len, &volume,&zft_pos,zft_blk_sz) failed: so i guess i am using wrong buffer size. i will have a glimpse on the ftape homepage. tx for your efforts stefan Tom Beer wrote: >Hi Stefan, > >>the device is working properly. i am able to write and read tar archives. >>the mt command is working fine, too. >> > >I'm no expert but two possiblities come to my mind. > >1) you are using a non-rewinding driver. >2) it is simply not compatible with a qic or zip drive. > >Is there a non-rewinding driver for this drive? > >Greets Tom > >
Re: Amlabel
On Tue, Jun 11, 2002 at 03:55:53PM -0500, Craig Hancock wrote: > But everytime I try to label another tape > it keep referecing the first tape that I labeled > saying that label already exist is this > normal Sounds like you're trying to assign the same label to multiple tapes. You need to give each one a distinct label. e.g., $ /usr/sbin/amlabel Daily Daily01 $ /usr/sbin/amlabel Daily Daily02 $ /usr/sbin/amlabel Daily Daily03 etc.
Re: amlabel & ftape
hello johannes, tx for the hint, but it won't work. still the same probs. if you send me the configuration, i will appreciate it. greets stefan
Re: amlabel & ftape
Stefan Kiczerjak <[EMAIL PROTECTED]> writes: > hello everboby, > > before i am going to buy an expensive dlt-streamer i'd like to do some > testing with an old iomega 250 floppy-qic. > I have configured all as discripted in the man-pages but unfortunately > amlabel closes with an error. > here the amlabel output: > > amanda@tester:~> amlabel test tgl01 > rewinding, reading label, not an amanda tape > rewinding, writing label tgl01 > amlabel: writing label: Invalid argument > > has anybody any suggestion? Stefan, did you try this from "man amanda"? rawtapedev "string" Default: /dev/null. The path name of the raw tape device. This is only used if Amanda is compiled for Linux machines with floppy tapes and is needed for QIC volume table operations. IIRC you need /dev/nrawqft0 as device. I've a abandoned but working installation at home. I can send the configuration. Johannes Nieß
Re: amlabel & ftape
hello again! yes, and i am using it ( ln -s /dev/nqft0 /dev/tape ). but meanwhile i have found these lines in /var/log /messeges : Apr 22 17:18:17 tester kernel: [141] zftape-read.c (check_read_access) - req_len 32768 not a multiple of block size 10240. Apr 22 17:18:18 tester kernel: [142] zftape-write.c (check_write_access) - write-count 32768 must be multiple of block-size 10240. Apr 22 17:18:18 tester kernel: [143] zftape-write.c (_zft_write) - check_write_access(req_len, &volume,&zft_pos,zft_blk_sz) failed: so i guess i am using wrong buffer size. i will have a glimpse on the ftape homepage. tx for your efforts stefan Tom Beer wrote: >Hi Stefan, > >>the device is working properly. i am able to write and read tar archives. >>the mt command is working fine, too. >> > >I'm no expert but two possiblities come to my mind. > >1) you are using a non-rewinding driver. >2) it is simply not compatible with a qic or zip drive. > >Is there a non-rewinding driver for this drive? > >Greets Tom > >
Re: amlabel & ftape
Hi Stefan, > the device is working properly. i am able to write and read tar archives. > the mt command is working fine, too. I'm no expert but two possiblities come to my mind. 1) you are using a non-rewinding driver. 2) it is simply not compatible with a qic or zip drive. Is there a non-rewinding driver for this drive? Greets Tom
Re: amlabel & ftape
hi tom, the device is working properly. i am able to write and read tar archives. the mt command is working fine, too. clueless regards stefan
Re: amlabel & ftape
is this command, replacing /dev/tape with the correct value working sufficiently? mt -f /dev/tape rewind Greets Tom
Re: amlabel as different user than "dumpuser"
On 17/04 2002 16:06 Johannes Niess wrote: > Toralf Lund <[EMAIL PROTECTED]> writes: > > > Is there a way I can set up amanda (2.4.2p2) to allow someone who is > not > > the dumpuser to run "amlabel". > > > > I'm currently running dumps as root (I haven't yet looked into the > > possibility of setting up permissions etc. for a different account), > but I > > want someone without root access to be able to label the tapes. > (Actually, > > I would ideally want this user to be able to run straight amlabel > > commands, but not 'amlabel -f'.) > > > > I guess I might achieve what I want by using "sudo" or similar, but is > > there a way to do it within amanda itself? > > Toralf, > > not a Amanda solution, but the sgid bit on amlabel should help. Using > suid is a very bad move: Every local user can rename tapes. > > I'm using sudo for that purpose and strongly recommend it. Especially > the syslog entries of the command lines are useful. How exactly have you configured it? - I think I can figure out how I might be set up, but it's always good to know what other people are doing. - Toralf
RE: amlabel problem
Figured it out... Once the drive recognises the tape it takes another 4 to 5 seconds before it's actually ready to do anything with it. -Original Message- From: John R. Jackson [mailto:[EMAIL PROTECTED]] Sent: March 14, 2002 11:21 PM To: Stott, Trevor Cc: '[EMAIL PROTECTED]' Subject: Re: amlabel problem >This is what I'm getting when I try to do an amlabel to a new tape. Is this >an amlabel problem or a tape drive problem? What version of Amanda? What OS? >rewinding, reading label, reading label: Value too large for defined data type I *think* what this says is that amlabel was built for 32 bit file systems but the kernel (or libc?) is using 64 bit structures (but that's kind of a wild guess). Did you build Amanda yourself or use some evil, you get what you deserve, pre-packaged thing :-)? >Trevor. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
