Trying to amlabel for amvault

[Winston Sorfleet]

Hello all,

My regular routine is daily amdump to vtl and it works fine.

Once a month, I amvault to an LTO-2 single-tape drive.

On a successful amvault run (3 so far), my logs look like this:

INFO amvault amvault pid 2936250
START amvault date 20201209050002
STATS amvault hostname flamen
INFO amvault vaulting
DISK amvault pomerium.romanus.ca /
DISK amvault flamen.romanus.ca /
DISK amvault forum.romanus.ca /
DISK amvault flamen.romanus.ca /home
INFO taper Slot 45 without label can be labeled
START taper datestamp 20201209050002 "ST:tape_storage" label Vault-2 tape 1
INFO amvault reading from source volume 'vtl32'
PART taper "ST:tape_storage" Vault-2 1 pomerium.romanus.ca /
20201204024701 1/-1 0 [sec 1495.044753 bytes 4100912932 kps 2678.713792]
DONE taper "ST:tape_storage" pomerium.romanus.ca / 20201204024701 1 0
[sec 1496.00 bytes 4100912932 kps 2677.003342 orig-kb 12335450]
INFO amvault reading from source volume 'vtl33'
PART taper "ST:tape_storage" Vault-2 2 flamen.romanus.ca /
20201207024702 1/-1 0 [sec 3153.603246 bytes 8551283380 kps 2648.038243]
DONE taper "ST:tape_storage" flamen.romanus.ca / 20201207024702 1 0 [sec
3154.00 bytes 8551283380 kps 2647.705136 orig-kb 20230530]
INFO amvault reading from source volume 'vtl34'
PART taper "ST:tape_storage" Vault-2 3 forum.romanus.ca / 20201208024702
1/-1 0 [sec 4391.490093 bytes 15462689293 kps 3438.532635]
DONE taper "ST:tape_storage" forum.romanus.ca / 20201208024702 1 0 [sec
4392.00 bytes 15462689293 kps 3438.133424 orig-kb 38373610]
INFO amvault reading from source volume 'vtl35'
INFO amvault reading from source volume 'vtl36'
INFO amvault reading from source volume 'vtl37'
PART taper "ST:tape_storage" Vault-2 4 flamen.romanus.ca /home
20201208024702 1/-1 0 [sec 11243.396124 bytes 45409383883 kps 3944.101988]
DONE taper "ST:tape_storage" flamen.romanus.ca /home 20201208024702 1 0
[sec 11245.00 bytes 45409383883 kps 3943.539440 orig-kb 58547630]
INFO taper tape Vault-2 kb 71801044 fm 4 [OK]
FINISH driver fake driver finish
FINISH amvault date 20201209050002 time 20326
INFO amvault pid-done 2936250

My most recent amvaults have been failures with

INFO amvault amvault pid 2043546
START amvault date 20210309050003
STATS amvault hostname flamen
INFO amvault vaulting
DISK amvault flamen.romanus.ca /home
DISK amvault forum.romanus.ca /
DISK amvault pomerium.romanus.ca /
DISK amvault flamen.romanus.ca /
INFO taper Slot 43 with label Vault-3 is not reusable
INFO taper Slot 44 with label Vault-1 is not reusable
INFO taper Slot 45 with label Vault-2 is not reusable
INFO taper Slot 1 with label vtl1 is in pool vtl
INFO taper Slot 2 with label vtl2 is in pool vtl
INFO taper Slot 3 with label vtl3 is in pool vtl
...
INFO taper Slot 32 with label vtl32 is in pool vtl
INFO taper Slot 33 with label vtl33 is in pool vtl
INFO taper Slot 34 with label vtl34 is in pool vtl
INFO taper Slot 35 with label vtl35 is in pool vtl
INFO taper Slot 36 with label vtl36 is in pool vtl
INFO taper Slot 37 with label vtl37 is in pool vtl
INFO taper Slot 38 with label vtl38 is in pool vtl
INFO taper Slot 39 with label vtl39 is in pool vtl
INFO taper Slot 40 with label vtl40 is in pool vtl
INFO taper Slot 41 with label Vault-5 is not in the tapelist
INFO taper Slot 42 with label Vault-1 is not reusable
INFO taper all slots have been loaded
FATAL amvault No acceptable volumes found
FINISH driver fake driver finish
FINISH amvault date 20210309050003 time 10
INFO amvault pid-done 2043546

I am not sure why amanda thinks that tapes are in a "slot" like the vtl,
but I assume that's a coding idiosyncrasy.  I had thought that the "no
acceptable volumes found" could be because this is a blank tape, so I've
been trying various combinations to label it, e.g.

backup@flamen:/etc/amanda/vtl$ amlabel --storage tape_storage --pool
tape_storage  -o 'labelstr="Vault-[1-7]"' -o 'autolabel="Vault-%" any'
vtl Vault-4
Reading label...
Found label 'vtl14' but it doesn't match the labelstr 'vtl[0-9][0-9]*$'.
Not writing label.
Not writing label.

Note the overrides seemingly not being read.

Here's the config file:

|org "Romanus"   # your organization name for reports||
||mailto "w...@romanus.ca" # space separated list of operators at your site||
||dumpuser "backup"||
||
||dumpcycle 7            # the number of days in the normal dump cycle||
||runspercycle 5 # the number of amdump runs in
dumpcycle days||
||   # (1 week * 5 amdump runs per week --
just weekdays)||
||tapecycle 40 tapes # the number of tapes in rotation||
||   # 1 week (dumpcycle) times 30 tapes per
week (just||
||   # 

Re: amlabel (v3.4.3) doesn't write tape line when first creating tapelist file

[Nathan Stratton Treadway]

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: labelstr check missing in amlabel (v3.4.3)?

[Nathan Stratton Treadway]

On Thu, Mar 16, 2017 at 11:46:10 -0400, Jean-Louis Martineau wrote:
> Thanks for reporting the issue.
> I committed the attached patch.

I noticed if I have an already-labeled volume in a slot at then try to
put an invalid label on it, the error message printed is misleading:


# su backup -c "amtape TestBackup slot 2"
slot   2: time X  label TESTBACKUP-02
changed to slot 2
# su backup -c "amlabel TestBackup BLAH-03 slot 2"
Reading label...
Found label 'TESTBACKUP-02' but it doesn't match the labelstr 
'^TESTBACKUP-[0-9][0-9]*$'.
Not writing label.
Not writing label.


I guess this situation is really a combination of two error conditions:
1) the specified new label doesn't match labelstr, and 2) the current
tape is already labeled  


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: labelstr check missing in amlabel (v3.4.3)?

[Nathan Stratton Treadway]

On Thu, Mar 16, 2017 at 11:46:10 -0400, Jean-Louis Martineau wrote:
> Thanks for reporting the issue.
> I committed the attached patch.

Great, thanks.

I applied to the patch to Label.pm and can confirm it works as expected
now: 


# su backup -c "amlabel TestBackup BLAH-02 slot 2"
Reading label...
Found an empty tape.
Label 'BLAH-02' doesn't match the labelstr '^TESTBACKUP-[0-9][0-9]*$'.
Label 'BLAH-02' doesn't match the labelstr '^TESTBACKUP-[0-9][0-9]*$'.


However, as you can see, the error message is repeated twice, and
there's no explicit message telling me that the label attempt failed.

I tried some other failure-to-write-label situations and found the
warning/failure messages were inconsistent:


# su backup -c "amlabel TestBackup TESTBACKUP-03 slot 2"
Reading label...
Volume with label 'TESTBACKUP-02' is active and contains data from this 
configuration.
Not writing label.
Not writing label.
# su backup -c "amlabel TestBackup TESTBACKUP-02 slot 3"
Label 'TESTBACKUP-02' already on a volume
# su backup -c "amlabel TestBackup slot 3"
Reading label...
Found an empty tape.
template is not set, you must set autolabel
template is not set, you must set autolabel


How difficult would be it be to fix the program to consistently A) print
the error message just one time and B) print "Not writing label." (or
something similar) in all situation where the label is not successfully
written?

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

[Jean-Louis Martineau]

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: labelstr check missing in amlabel (v3.4.3)?

[Jean-Louis Martineau]

Nathan,

Thanks for reporting the issue.
I committed the attached patch.

Jean-Louis

On 15/03/17 05:45 PM, Nathan Stratton Treadway wrote:
> I'm running Amanda 3.4.3 (built under Ubuntu from Jose's Debian
> "experimental" source package, v3.4.3-1).
>
> The man page for "amlabel" includes the following paragraph:
> Label 'label' doesn't match labelstr 'labelstr'
> The given label does not match the configured labelstr. Even with
> -f, this is an error.
> ... but in practice it lets me create labels that don't match without
> any warning:
>
> ==
> # amgetconf TestBackup labelstr
> "^TESTBACKUP-[0-9][0-9]*$"
>
> # su backup -c "amlabel TestBackup BLAH-05 slot 5"
> Reading label...
> Found an empty tape.
> Writing label 'BLAH-05'...
> Checking label...
> Success!
>
> # grep BLAH tapelist
> 0 BLAH-05 reuse BLOCKSIZE:32 POOL:TestBackup STORAGE:TestBackup 
> CONFIG:TestBackup
> ==
>
>
> Other commands do show that the label doesn't match the labelstr, though:
> ==
> # su backup -c "amtape TestBackup show 1,5"
> slot   1: date X  label TESTBACKUP-01
> slot   5: date X  label BLAH-05 (label do not match labelstr)
> ==
>
>
> Am I correct that amlabel should be refusing to create this non-matching
> label?
>
> 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/installcheck/amlabel.pl b/installcheck/amlabel.pl
index 165f455..86619d9 100644
--- a/installcheck/amlabel.pl
+++ b/installcheck/amlabel.pl
@@ -138,7 +138,7 @@ like($Installcheck::Run::stdout,
 ok(!run('amlabel', 'TESTCONF', 'SomeTape'),
 "amlabel refuses to write on a  tape already labeled");
 like($Installcheck::Run::stdout,
-qr/Reading label...\nLabel 'TESTCONF92' doesn't match the labelstr 'TESTCONF\[0-9\]\[0-9\]'/,
+qr/Reading label...\nFound label 'TESTCONF92' but it doesn't match the labelstr 'TESTCONF\[0-9\]\[0-9\]'/,
 "with correct message on stdout");
 like($Installcheck::Run::stderr,
 qr/Not writing label./,
diff --git a/perl/Amanda/Label.pm b/perl/Amanda/Label.pm
index 6d3cb3e..ad16ece 100644
--- a/perl/Amanda/Label.pm
+++ b/perl/Amanda/Label.pm
@@ -669,7 +669,7 @@ sub label {
 		$self->user_msg(Amanda::Label::Message->new(
 	source_filename => __FILE__,
 	source_line => __LINE__,
-	code  => 113,
+	code  => 116,
 	severity  => $Amanda::Message::ERROR,
 	label => $label,
 	labelstr  => $labelstr));
@@ -768,7 +768,21 @@ sub label {
 	}
 	}
 
-	if ($dev_ok) {
+	if ($params{'label'} && $dev_ok) {
+	my $barcode = $res->{'barcode'};
+	my $meta = $meta;
+
+	if (!match_labelstr($labelstr, $autolabel, $params{'label'}, $barcode, $meta, $storage_name)) {
+		return $steps->{'releasing'}->(Amanda::Label::Message->new(
+	source_filename => __FILE__,
+	source_line => __LINE__,
+	code  => 113,
+	severity  => $Amanda::Message::ERROR,
+	label => $label,
+	labelstr  => $labelstr));
+	}
+	}
+	if ($dev_ok){
 	$self->user_msg(Amanda::Label::Message->new(
 source_filename => __FILE__,
 source_line => __LINE__,

amlabel (v3.4.3) doesn't write tape line when first creating tapelist file

[Nathan Stratton Treadway]

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

labelstr check missing in amlabel (v3.4.3)?

[Nathan Stratton Treadway]

I'm running Amanda 3.4.3 (built under Ubuntu from Jose's Debian
"experimental" source package, v3.4.3-1).

The man page for "amlabel" includes the following paragraph:
   Label 'label' doesn't match labelstr 'labelstr'
   The given label does not match the configured labelstr. Even with
   -f, this is an error.
... but in practice it lets me create labels that don't match without
any warning:

==
# amgetconf TestBackup labelstr
"^TESTBACKUP-[0-9][0-9]*$"

# su backup -c "amlabel TestBackup BLAH-05 slot 5"
Reading label...
Found an empty tape.
Writing label 'BLAH-05'...
Checking label...
Success!

# grep BLAH tapelist
0 BLAH-05 reuse BLOCKSIZE:32 POOL:TestBackup STORAGE:TestBackup 
CONFIG:TestBackup
==


Other commands do show that the label doesn't match the labelstr, though:
==
# su backup -c "amtape TestBackup show 1,5"
slot   1: date X  label TESTBACKUP-01
slot   5: date X  label BLAH-05 (label do not match labelstr)
==


Am I correct that amlabel should be refusing to create this non-matching
label?

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: What does this mean: "amlabel: could not load slot "1": unexpected EOF"

[Robert Heller]

OK, I solved this: it was a broken Perl install (I think cpanel caused this), 
reinstalling/updating Perl cured the problem.


At Fri, 18 Mar 2016 14:07:13 -0400 Robert Heller  wrote:

> 
> OS: CentOS 6
> Amanda version: 2.6.1p2-9.el6_6.x86_64
> 
> I am trying to use Amazon S3 as a tape changer, but I am getting an error 
> from 
> amlabel: "amlabel: could not load slot "1": unexpected EOF"
> 
> I set things up using the documentation at 
> http://wiki.zmanda.com/index.php/How_To:Backup_to_Amazon_S3#Old_chg-multi_.28Amanda_2.6_and_later.29
> 
> amanda.conf contains:
> 
> tapedev "null:" # the no-rewind tape device to be used
> device_property "S3_ACCESS_KEY" ""
> device_property "S3_SECRET_KEY" "**"
> device_property "S3_SSL" "YES"
> changerfile "/etc/amanda/xxx/changer.conf"   
> #changerdev "/dev/sg1"
> tapetype S3 # what kind of tape it is (see tapetypes below)   
>   
> define tapetype S3 {  
> comment "S3 Bucket"   
> length 10 gigabytes # Bucket size 10GB
> }
> 
> And in changer.conf contains:
> 
> multieject 0  
> gravity 0
> needeject 0
> ejectdelay 0
> statefile /etc/amanda/xxx/changer-status 
> firstslot 1
> lastslot 40
>
> slot  1  s3:xxx-backups/slot-01/ 
> slot  2  s3:xxx-backups/slot-02/ 
> slot  3  s3:xxx-backups/slot-03/ 
> slot  4  s3:xxx-backups/slot-04/ 
> slot  5  s3:xxx-backups/slot-05/ 
> slot  6  s3:xxx-backups/slot-06/ 
> slot  7  s3:xxx-backups/slot-07/ 
> slot  8  s3:xxx-backups/slot-08/ 
> slot  9  s3:xxx-backups/slot-09/ 
> slot  10 s3:xxx-backups/slot-10/ 
> (more slots)
> 
> And this is what is in the amlabel debug log:
> 
> 1458323720.494262: amlabel: pid 16385 ruid 33 euid 33 version 2.6.1p2: start 
> at Fri Mar 18 13:55:20 2016
> 1458323720.498339: amlabel: pid 16385 ruid 33 euid 33 version 2.6.1p2: rename 
> at Fri Mar 18 13:55:20 2016
> 1458323720.498880: amlabel: changer: >> -slot 1
> 1458323720.527899: amlabel: changer: ERROR  unexpected EOF
> 1458323720.527952: amlabel: critical (fatal): could not load slot "1": 
> unexpected EOF
> /usr/lib64/libamanda-2.6.1p2.so(+0x21a99)[0x7fa3e4c19a99]
> /lib64/libglib-2.0.so.0(g_logv+0x1b9)[0x7fa3e39e9519]
> /lib64/libglib-2.0.so.0(g_log+0x83)[0x7fa3e39e9933]
> amlabel(main+0x887)[0x7fa3e55014f7]
> /lib64/libc.so.6(__libc_start_main+0xfd)[0x7fa3e1e3ad5d]
> amlabel(+0x1b49)[0x7fa3e5500b49]
> 
> What am I doing wrong?
> 

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

What does this mean: "amlabel: could not load slot "1": unexpected EOF"

[Robert Heller]

OS: CentOS 6
Amanda version: 2.6.1p2-9.el6_6.x86_64

I am trying to use Amazon S3 as a tape changer, but I am getting an error from 
amlabel: "amlabel: could not load slot "1": unexpected EOF"

I set things up using the documentation at 
http://wiki.zmanda.com/index.php/How_To:Backup_to_Amazon_S3#Old_chg-multi_.28Amanda_2.6_and_later.29

amanda.conf contains:

tapedev "null:" # the no-rewind tape device to be used
device_property "S3_ACCESS_KEY" ""
device_property "S3_SECRET_KEY" "**"
device_property "S3_SSL" "YES"
changerfile "/etc/amanda/xxx/changer.conf"   
#changerdev "/dev/sg1"
tapetype S3 # what kind of tape it is (see tapetypes below)   
  
define tapetype S3 {  
comment "S3 Bucket"   
length 10 gigabytes # Bucket size 10GB
}

And in changer.conf contains:

multieject 0  
gravity 0
needeject 0
ejectdelay 0
statefile /etc/amanda/xxx/changer-status 
firstslot 1
lastslot 40
   
slot  1  s3:xxx-backups/slot-01/ 
slot  2  s3:xxx-backups/slot-02/ 
slot  3  s3:xxx-backups/slot-03/ 
slot  4  s3:xxx-backups/slot-04/ 
slot  5  s3:xxx-backups/slot-05/ 
slot  6  s3:xxx-backups/slot-06/ 
slot  7  s3:xxx-backups/slot-07/ 
slot  8  s3:xxx-backups/slot-08/ 
slot  9  s3:xxx-backups/slot-09/ 
slot  10 s3:xxx-backups/slot-10/     
(more slots)

And this is what is in the amlabel debug log:

1458323720.494262: amlabel: pid 16385 ruid 33 euid 33 version 2.6.1p2: start at 
Fri Mar 18 13:55:20 2016
1458323720.498339: amlabel: pid 16385 ruid 33 euid 33 version 2.6.1p2: rename 
at Fri Mar 18 13:55:20 2016
1458323720.498880: amlabel: changer: >> -slot 1
1458323720.527899: amlabel: changer: ERROR  unexpected EOF
1458323720.527952: amlabel: critical (fatal): could not load slot "1": 
unexpected EOF
/usr/lib64/libamanda-2.6.1p2.so(+0x21a99)[0x7fa3e4c19a99]
/lib64/libglib-2.0.so.0(g_logv+0x1b9)[0x7fa3e39e9519]
/lib64/libglib-2.0.so.0(g_log+0x83)[0x7fa3e39e9933]
amlabel(main+0x887)[0x7fa3e55014f7]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fa3e1e3ad5d]
amlabel(+0x1b49)[0x7fa3e5500b49]

What am I doing wrong?

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services

  

Re: amlabel problem

[Jean-Louis Martineau]

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'};

amlabel problem

[Kamil Jońca]

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

-- 
http://wolnelektury.pl/wesprzyj/teraz/
No line available at 300 baud.

Re: Question about --assign of amlabel

[Kazuhiro Takenaka]

Hi Jean-Louis.

> eg. If you change from a config that do not use the barcode to a config that 
> use it, you can use [--assign] to add the barcode to the tapelist.

This example is a very clear anwer to my question.

Thunks.

2014-05-27 20:26 GMT+09:00 Jean-Louis Martineau :
> [--assign] must be used only when the volume is already labeled and the
> label already in the tapelist file, you already ran amlabel for the volume.
>
> eg. If you change from a config that do not use the barcode to a config that
> use it, you can use [--assign] to add the barcode to the tapelist.
>
> Jean-Louis
>
>
>
> On 05/27/2014 03:24 AM, Kazuhiro Takenaka wrote:
>>
>> Hello, Everyone.
>>
>> I am reading the man page of the amlabel command of Amanda 3.3.3.
>>
>> There is an explanation about the '--assign' option in
>> the man page, it says;
>>
>> If [--assign] is given, the barcode and meta-label are assigned
>> to the label without labeling the volume. The label must already
>> be in the tapelist file.
>>
>> How can I define the label in the tapelist file before
>> I run the amlabel command?
>>
>> Should I write the label into the tapelist file by hand?
>>
>> Best regard.
>
>

Re: Question about --assign of amlabel

[Jean-Louis Martineau]

[--assign] must be used only when the volume is already labeled and the 
label already in the tapelist file, you already ran amlabel for the volume.


eg. If you change from a config that do not use the barcode to a config 
that use it, you can use [--assign] to add the barcode to the tapelist.


Jean-Louis


On 05/27/2014 03:24 AM, Kazuhiro Takenaka wrote:

Hello, Everyone.

I am reading the man page of the amlabel command of Amanda 3.3.3.

There is an explanation about the '--assign' option in
the man page, it says;

If [--assign] is given, the barcode and meta-label are assigned
to the label without labeling the volume. The label must already
be in the tapelist file.

How can I define the label in the tapelist file before
I run the amlabel command?

Should I write the label into the tapelist file by hand?

Best regard.

Question about --assign of amlabel

[Kazuhiro Takenaka]

Hello, Everyone.

I am reading the man page of the amlabel command of Amanda 3.3.3.

There is an explanation about the '--assign' option in
the man page, it says;

If [--assign] is given, the barcode and meta-label are assigned
to the label without labeling the volume. The label must already
be in the tapelist file.

How can I define the label in the tapelist file before
I run the amlabel command?

Should I write the label into the tapelist file by hand?

Best regard.
-- 
Kazuhiro Takenaka 

RE: amlabel segmentation fault

[Kervin L. Pierre]

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

[Jean-Louis Martineau]

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

[Jean-Louis Martineau]

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

[Kervin L. Pierre]

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

[Jean-Louis Martineau]

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/

amlabel segmentation fault

[Kervin L. Pierre]

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: error whith amlabel and chg-rait

[Jean-Louis Martineau]

Dennis,

Try the attached patch.

The barcode for the rait is '{D00225,D00225}', You must adjust the labelstr.

Jean-Louis


On 06/27/2013 10:30 AM, Dennis Benndorf wrote:


Hi,

amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'

Reading label...

Found Amanda volume 'D00225'.

Newly-generated label '' does not match labelstr '^D0[0-9]*$'

Dont know why this happend, because labelstr is set to "^D0[0-9]*$" 
and autolabel to "$b" any .


but if I set it by hand it works as expected:

amanda@dl380-54:~$ amlabel -f mirror D00225 slot '{225,225}'

Reading label...

Found Amanda volume 'D00225'.

Writing label 'D00225'...

Checking label...

Success!

amanda@dl380-54:~$ cat /etc/amanda/mirror/tapelist

0 D00225 reuse BLOCKSIZE:32

--

Big thanks,

Dennis


Am Donnerstag, 27. Juni 2013, 10:10:09 schrieb Jean-Louis Martineau:

> Dennis,

>

> Try the attached patch.

> You can patch the installed Amanda/Changer/rait.pm file.

>

> Jean-Louis



diff --git a/perl/Amanda/Changer/rait.pm b/perl/Amanda/Changer/rait.pm
index d6ba1dd..2234a2e 100644
--- a/perl/Amanda/Changer/rait.pm
+++ b/perl/Amanda/Changer/rait.pm
@@ -687,6 +687,8 @@ sub new {
 $self->{'child_reservations'} = $child_reservations;
 
 $self->{'device'} = $rait_device;
+my @barcodes = errmap { "" . $_->{'barcode'} } @$child_reservations;
+$self->{'barcode'} = collapse_braced_alternates(\@barcodes);
 
 my @slot_names;
 @slot_names = errmap { "" . $_->{'this_slot'} } @$child_reservations;

Re: error whith amlabel and chg-rait

[Dennis Benndorf]

Hi,

amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'
Reading label...
Found Amanda volume 'D00225'.
Newly-generated label '' does not match labelstr '^D0[0-9]*$'

Dont know why this happend, because labelstr is set to "^D0[0-9]*$" and 
autolabel to "$b" any .
but if I set it by hand it works as expected:

amanda@dl380-54:~$ amlabel -f mirror D00225 slot '{225,225}'
Reading label...
Found Amanda volume 'D00225'.
Writing label 'D00225'...
Checking label...
Success!
amanda@dl380-54:~$ cat /etc/amanda/mirror/tapelist
0 D00225 reuse BLOCKSIZE:32


-- 
Big thanks,
Dennis


> Dennis,
> 
> Try the attached patch.
> You can patch the installed Amanda/Changer/rait.pm file.
> 
> Jean-Louis

Re: error whith amlabel and chg-rait

[Jean-Louis Martineau]

Dennis,

Try the attached patch.
You can patch the installed Amanda/Changer/rait.pm file.

Jean-Louis

On 06/27/2013 08:41 AM, Dennis Benndorf wrote:


grep meta-autolabel /etc/amanda/mirror/amanda.conf show nothing.

--

Regards

Dennis Benndorf


Am Donnerstag, 27. Juni 2013, 08:39:11 schrieb Jean-Louis Martineau:

> Dennis,

>

> Do you have 'meta-autolabel' set in your amanda.conf? unset it.

>

> Jean-Louis

>

> On 06/27/2013 08:33 AM, Dennis Benndorf wrote:

> > Ok I understand but why does it tell me those messages:

> >

> > amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'

> >

> > Reading label...

> >

> > Found Amanda volume 'D00225'.

> >

> > amlabel: Can't call method "make_new_meta_label" on an undefined value

> > at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.

> >

> > amanda@dl380-54:~$ amlabel -f --barcode '{D00225,D00225}' mirror

> >

> > Reading label...

> >

> > Found Amanda volume 'D00225'.

> >

> > amlabel: Can't call method "make_new_meta_label" on an undefined value

> > at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.

> >

> >

> > Regards Dennis

> >

> > Am Donnerstag, 27. Juni 2013, 07:58:19 schrieb Jean-Louis Martineau:

> > > chg-rait and chg-robot do not use meta label, don't try to set it.

> > >

> > > Only chg-disk use meta-label.

> > >

> > >

> > >

> > > The barcode is the combination of all barcodes, as the inventory 
told


> > >

> > > you, the barcode is '{D00225,D00225}'

> > >

> > > amlabel -f --barcode '{D00225,D00225}' mirror

> > >

> > > The same is true for the slot number, you could do:

> > >

> > > amlabel -f mirror slot '{225,225}'

> > >

> > >

> > >

> > > It is not required to put the same barcode on both tape, it is 
generally


> > >

> > > a bad idea to do so, a barcode must be unique.

> > >

> > >

> > >

> > > Jean-Louis



diff --git a/perl/Amanda/Changer/rait.pm b/perl/Amanda/Changer/rait.pm
index e0ef276..d6ba1dd 100644
--- a/perl/Amanda/Changer/rait.pm
+++ b/perl/Amanda/Changer/rait.pm
@@ -268,6 +268,7 @@ sub _make_res {
 }
 
 my $combined_res = Amanda::Changer::rait::Reservation->new(
+	$self,
 	$kid_reservations, $rait_device);
 $rait_device->read_label();
 
@@ -676,9 +677,11 @@ sub errmap (&@) {
 
 sub new {
 my $class = shift;
-my ($child_reservations, $rait_device) = @_;
+my ($chg, $child_reservations, $rait_device) = @_;
 my $self = Amanda::Changer::Reservation::new($class);
 
+$self->{'chg'} = $chg;
+
 # note that $child_reservations may contain "ERROR" in place of a reservation
 
 $self->{'child_reservations'} = $child_reservations;

Re: error whith amlabel and chg-rait

[Dennis Benndorf]

grep meta-autolabel /etc/amanda/mirror/amanda.conf show nothing.

-- 
Regards
Dennis Benndorf


> Dennis,
> 
> Do you have 'meta-autolabel' set in your amanda.conf? unset it.
> 
> Jean-Louis
> 
> On 06/27/2013 08:33 AM, Dennis Benndorf wrote:
> > Ok I understand but why does it tell me those messages:
> > 
> > amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'
> > 
> > Reading label...
> > 
> > Found Amanda volume 'D00225'.
> > 
> > amlabel: Can't call method "make_new_meta_label" on an undefined value
> > at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.
> > 
> > amanda@dl380-54:~$ amlabel -f --barcode '{D00225,D00225}' mirror
> > 
> > Reading label...
> > 
> > Found Amanda volume 'D00225'.
> > 
> > amlabel: Can't call method "make_new_meta_label" on an undefined value
> > at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.
> > 
> > 
> > Regards Dennis
> > 
> > Am Donnerstag, 27. Juni 2013, 07:58:19 schrieb Jean-Louis Martineau:
> > > chg-rait and chg-robot do not use meta label, don't try to set it.
> > > 
> > > Only chg-disk use meta-label.
> > > 
> > > 
> > > 
> > > The barcode is the combination of all barcodes, as the inventory told
> > > 
> > > you, the barcode is '{D00225,D00225}'
> > > 
> > > amlabel -f --barcode '{D00225,D00225}' mirror
> > > 
> > > The same is true for the slot number, you could do:
> > > 
> > > amlabel -f mirror slot '{225,225}'
> > > 
> > > 
> > > 
> > > It is not required to put the same barcode on both tape, it is generally
> > > 
> > > a bad idea to do so, a barcode must be unique.
> > > 
> > > 
> > > 
> > > Jean-Louis

Re: error whith amlabel and chg-rait

[Jean-Louis Martineau]

Dennis,

Do you have 'meta-autolabel' set in your amanda.conf? unset it.

Jean-Louis


On 06/27/2013 08:33 AM, Dennis Benndorf wrote:


Ok I understand but why does it tell me those messages:

amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'

Reading label...

Found Amanda volume 'D00225'.

amlabel: Can't call method "make_new_meta_label" on an undefined value 
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.


amanda@dl380-54:~$ amlabel -f --barcode '{D00225,D00225}' mirror

Reading label...

Found Amanda volume 'D00225'.

amlabel: Can't call method "make_new_meta_label" on an undefined value 
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.


--

Regards Dennis


Am Donnerstag, 27. Juni 2013, 07:58:19 schrieb Jean-Louis Martineau:

> chg-rait and chg-robot do not use meta label, don't try to set it.

> Only chg-disk use meta-label.

>

> The barcode is the combination of all barcodes, as the inventory told

> you, the barcode is '{D00225,D00225}'

> amlabel -f --barcode '{D00225,D00225}' mirror

> The same is true for the slot number, you could do:

> amlabel -f mirror slot '{225,225}'

>

> It is not required to put the same barcode on both tape, it is generally

> a bad idea to do so, a barcode must be unique.

>

> Jean-Louis

Re: error whith amlabel and chg-rait

[Dennis Benndorf]

Ok I understand but why does it tell me those messages:

amanda@dl380-54:~$ amlabel -f mirror slot '{225,225}'
Reading label...
Found Amanda volume 'D00225'.
amlabel: Can't call method "make_new_meta_label" on an undefined value at 
/usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.

amanda@dl380-54:~$ amlabel -f --barcode '{D00225,D00225}' mirror
Reading label...
Found Amanda volume 'D00225'.
amlabel: Can't call method "make_new_meta_label" on an undefined value at 
/usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.

-- 
Regards Dennis


> chg-rait and chg-robot do not use meta label, don't try to set it.
> Only chg-disk use meta-label.
> 
> The barcode is the combination of all barcodes, as the inventory told
> you, the barcode is '{D00225,D00225}'
>  amlabel -f --barcode '{D00225,D00225}' mirror
> The same is true for the slot number, you could do:
>  amlabel -f mirror slot '{225,225}'
> 
> It is not required to put the same barcode on both tape, it is generally
> a bad idea to do so, a barcode must be unique.
> 
> Jean-Louis

Re: error whith amlabel and chg-rait

[Jean-Louis Martineau]

chg-rait and chg-robot do not use meta label, don't try to set it.
Only chg-disk use meta-label.

The barcode is the combination of all barcodes, as the inventory told 
you, the barcode is '{D00225,D00225}'

amlabel -f --barcode '{D00225,D00225}' mirror
The same is true for the slot number, you could do:
amlabel -f mirror slot '{225,225}'

It is not required to put the same barcode on both tape, it is generally 
a bad idea to do so, a barcode must be unique.


Jean-Louis

On 06/27/2013 07:37 AM, Dennis Benndorf wrote:


Hello,

I am trying to set up a mirror of too robots using chg-rait. Tapes in 
both robots have the same barcodes. Now I want to label them with the 
name of their barcodes, but the following happens:


amanda@dl380-54:~$ amlabel -f --meta META225 --barcode D00225 mirror

Reading label...

No volume with barcode 'D00225' available

amanda@dl380-54:~$ amtape mirror inventory |grep 225

slot {225,225}: label D00225 barcode {D00225,D00225} (in drive {1,1})

amanda@dl380-54:~$ amlabel -f --meta META225 --barcode D00225 mirror

Reading label...

No volume with barcode 'D00225' available

amanda@dl380-54:~$ amlabel -f --barcode D00225 mirror

Reading label...

No volume with barcode 'D00225' available

amanda@dl380-54:~$ amlabel -f mirror^C

amanda@dl380-54:~$ man amanda.conf

amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% --barcode 
D00225 mirror


Reading label...

No volume with barcode 'D00225' available

amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% mirror slot 225

Reading label...

Found Amanda volume 'D00225'.

amlabel: Can't call method "make_new_meta_label" on an undefined value 
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.


What I really want to do is to force both sites to label ( one site 
has a different label as you can see )


amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% mirror slot 457

Reading label...

Error reading volume label: Inconsistent volume labels/datestamps: Got 
D00457/20130408180904 on tape:/dev/L700/MRO-LW-1 against 
D10068/20130508071050 on tape:/dev/L700/OPELHAUS-LW-1.


amlabel: Can't call method "make_new_meta_label" on an undefined value 
at /usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.


--

Regards

Dennis

error whith amlabel and chg-rait

[Dennis Benndorf]

Hello,

I am trying to set up a mirror of too robots using chg-rait. Tapes in both 
robots 
have the same barcodes. Now I want to label them with the name of their 
barcodes, but the following happens:


/amanda@dl380-54:~$ amlabel -f --meta META225 --barcode D00225 mirror/
/Reading label.../
/No volume with barcode 'D00225' available/
/amanda@dl380-54:~$ amtape mirror inventory |grep 225/
/slot {225,225}: label D00225 barcode {D00225,D00225} (in drive {1,1})/
/amanda@dl380-54:~$ amlabel -f --meta META225 --barcode D00225 mirror/
/Reading label.../
/No volume with barcode 'D00225' available/
/amanda@dl380-54:~$ amlabel -f --barcode D00225 mirror/
/Reading label.../
/No volume with barcode 'D00225' available/
/amanda@dl380-54:~$ amlabel -f mirror^C/
/amanda@dl380-54:~$ man amanda.conf/
/amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% --barcode D00225 
mirror/
/Reading label.../
/No volume with barcode 'D00225' available/
/amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% mirror slot 225/
/Reading label.../
/Found Amanda volume 'D00225'./
/amlabel: Can't call method "make_new_meta_label" on an undefined value at 
/usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632./


What I really want to do is to force both sites to label ( one site has a 
different 
label as you can see )

amanda@dl380-54:~$ amlabel -f -o meta-autolabel=META%%% mirror slot 457
Reading label...
Error reading volume label: Inconsistent volume labels/datestamps: Got 
D00457/20130408180904 on tape:/dev/L700/MRO-LW-1 against 
D10068/20130508071050 on tape:/dev/L700/OPELHAUS-LW-1.
amlabel: Can't call method "make_new_meta_label" on an undefined value at 
/usr/local/share/perl/5.14.2/Amanda/Changer.pm line 1632.


-- 
Regards
Dennis

Re: Error for amlabel

[Amit Karpe]

On Tue, Feb 26, 2013 at 3:50 AM, Marcus Pless  wrote:

> On 02/25/2013 01:14:22 AM, Amit Karpe wrote:
>
>> On Mon, Feb 25, 2013 at 4:55 PM, Amit Karpe  wrote:
>>
>> >
>> >
>> > On Fri, Nov 30, 2012 at 12:32 PM, Jon LaBadie  wrote:
>> >
>> >> On Fri, Nov 30, 2012 at 11:20:37AM +0800, Amit Karpe wrote:
>> >> > Any idea for my problem.
>> >>
>> >> The last line of your first message seems critical:
>> >>
>> >> ...
>> >>
>> >> > > I could not able to write anything using amdump or dd.
>> >>
>> >> If you can't read or write using standard system tools
>> >> like dd, there is nothing amanda can do about it.
>> >> Sounds to me like you have hardware problems, either
>> >> the tape drive or maybe the cables.
>> >>
>> >> Jon
>> >> --
>> >> Jon H. LaBadie j...@jgcomp.com
>> >>  11226 South Shore Rd.  (703) 787-0688 (H)
>> >>  Reston, VA  20190  (609) 477-8330 (C)
>> >>
>> >
>> >
>> > I had ask HP for support. Their log tool saying my labels are the
>> culprit.
>> > He is asking me to use only barcode labeling:
>> > "As per the Amanda Tool output and logs there is one cartridge in the
>> MSL
>> > which has either missing or worng barcode label or the barcode label is
>> > properly aligned as per Tape Cartridge
>> >
>> > Please remove all the tapes and check if you find such cartridge and if
>> > you find that then put the Barcode Lable correctly on it and insert it
>> back
>> > in the same slot
>> >
>> > This error occurs because during initialzation before beackup the MSL
>> take
>> > the Inventory of the cartridges in the MSL and if there is any mislatch
>> > cartridge, it halts the process of backup"
>> >
>> >
>> > As far as my understanding amanda don't required any barcode labeling.
>> > Then what is a problem ?
>> > How can I cross check and confirm that "hardware problems, either the
>> tape
>> > drive or maybe the cables." ??
>> >
>> >
>> >
>>
>> Following link have photos of my tapes. Can someone confirm that having
>> such label will be the problem ???
>>
>> http://news.karpe.net.in/hp-**storageworks-msl2024-tape-**library-1-lto-4
>>
>
>
>
> My old LTO-1 and LTO-2 tape libraries didn't care about barcode labels.
> My LTO-4 (StorageTek SL-500) libraries won't load a tape and bring it
> online unless it has a correctly formatted barcode label. You can buy
> them pre-printed but we just make our own using a simple "Brother Ptouch"
> label maker and 3/4 inch (18mm) tape. I think a proper label has up to
> 8 alpha-numerics but the last 2 characters have to be "L4" (if it's an
> LTO4 tape) or the library/drive won't know what to do with it.
>
> My cleaning cartridge with a factory barcode is labeled "CLNU01CU".
>
> I like to do my own barcode labels so that the human readable label
> matches the amanda software label. The L4 extension doesn't actually
> show when I do something like an "mtx status" so I don't include that
> in the amanda label.
>
> IBM has a pdf of the LTO label spec here:
>
> http://www-1.ibm.com/support/**docview.wss?rs=543&context=**
> STCVQ6R&q1=ssg1*&uid=**ssg1S7000429&loc=en_US&cs=utf-**8&lang=en+en
>
> or
>
> http://tinyurl.com/LTO-label-**spec 
>
>
> Good luck!
>
>
Thank Marcus.
I will check these docs and will updated you.

Re: Error for amlabel

[Marcus Pless]

On 02/25/2013 01:14:22 AM, Amit Karpe wrote:
On Mon, Feb 25, 2013 at 4:55 PM, Amit Karpe   
wrote:


>
>
> On Fri, Nov 30, 2012 at 12:32 PM, Jon LaBadie   
wrote:

>
>> On Fri, Nov 30, 2012 at 11:20:37AM +0800, Amit Karpe wrote:
>> > Any idea for my problem.
>>
>> The last line of your first message seems critical:
>>
>> ...
>>
>> > > I could not able to write anything using amdump or dd.
>>
>> If you can't read or write using standard system tools
>> like dd, there is nothing amanda can do about it.
>> Sounds to me like you have hardware problems, either
>> the tape drive or maybe the cables.
>>
>> Jon
>> --
>> Jon H. LaBadie j...@jgcomp.com
>>  11226 South Shore Rd.  (703) 787-0688 (H)
>>  Reston, VA  20190  (609) 477-8330 (C)
>>
>
>
> I had ask HP for support. Their log tool saying my labels are the  
culprit.

> He is asking me to use only barcode labeling:
> "As per the Amanda Tool output and logs there is one cartridge in  
the MSL
> which has either missing or worng barcode label or the barcode  
label is

> properly aligned as per Tape Cartridge
>
> Please remove all the tapes and check if you find such cartridge  
and if
> you find that then put the Barcode Lable correctly on it and insert  
it back

> in the same slot
>
> This error occurs because during initialzation before beackup the  
MSL take
> the Inventory of the cartridges in the MSL and if there is any  
mislatch

> cartridge, it halts the process of backup"
>
>
> As far as my understanding amanda don't required any barcode  
labeling.

> Then what is a problem ?
> How can I cross check and confirm that "hardware problems, either  
the tape

> drive or maybe the cables." ??
>
>
>

Following link have photos of my tapes. Can someone confirm that  
having

such label will be the problem ???

http://news.karpe.net.in/hp-storageworks-msl2024-tape-library-1-lto-4




My old LTO-1 and LTO-2 tape libraries didn't care about barcode labels.
My LTO-4 (StorageTek SL-500) libraries won't load a tape and bring it
online unless it has a correctly formatted barcode label. You can buy
them pre-printed but we just make our own using a simple "Brother  
Ptouch"

label maker and 3/4 inch (18mm) tape. I think a proper label has up to
8 alpha-numerics but the last 2 characters have to be "L4" (if it's an
LTO4 tape) or the library/drive won't know what to do with it.

My cleaning cartridge with a factory barcode is labeled "CLNU01CU".

I like to do my own barcode labels so that the human readable label
matches the amanda software label. The L4 extension doesn't actually
show when I do something like an "mtx status" so I don't include that
in the amanda label.

IBM has a pdf of the LTO label spec here:

http://www-1.ibm.com/support/docview.wss?rs=543&context=STCVQ6R&q1=ssg1*&uid=ssg1S7000429&loc=en_US&cs=utf-8&lang=en+en

or

http://tinyurl.com/LTO-label-spec


Good luck!


--Marcus



> --
> Regards
> Amit Karpe.
> http://www.amitkarpe.com/
> http://news.karpe.net.in/
>



--
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/

Re: Error for amlabel

[Jon Brown]

 
There should be an option for 'Ignore Barcode Media ID'
 
Have you tried enabling that?


>>> Amit Karpe  2/25/2013 2:14 AM >>>

On Mon, Feb 25, 2013 at 4:55 PM, Amit Karpe  wrote:




On Fri, Nov 30, 2012 at 12:32 PM, Jon LaBadie  wrote:


On Fri, Nov 30, 2012 at 11:20:37AM +0800, Amit Karpe wrote:
> Any idea for my problem.

The last line of your first message seems critical:

...

> > I could not able to write anything using amdump or dd.

If you can't read or write using standard system tools
like dd, there is nothing amanda can do about it.
Sounds to me like you have hardware problems, either
the tape drive or maybe the cables.

Jon
--
Jon H. LaBadie j...@jgcomp.com
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (609) 477-8330 (C)



I had ask HP for support. Their log tool saying my labels are the culprit.
He is asking me to use only barcode labeling:
"As per the Amanda Tool output and logs there is one cartridge in the MSL which 
has either missing or worng barcode label or the barcode label is properly 
aligned as per Tape Cartridge

Please remove all the tapes and check if you find such cartridge and if you 
find that then put the Barcode Lable correctly on it and insert it back in the 
same slot

This error occurs because during initialzation before beackup the MSL take the 
Inventory of the cartridges in the MSL and if there is any mislatch cartridge, 
it halts the process of backup"


As far as my understanding amanda don't required any barcode labeling. Then 
what is a problem ?
How can I cross check and confirm that "hardware problems, either the tape 
drive or maybe the cables." ??





Following link have photos of my tapes. Can someone confirm that having such 
label will be the problem ???

http://news.karpe.net.in/hp-storageworks-msl2024-tape-library-1-lto-4



-- 
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/




-- 
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/

Re: Error for amlabel

[Amit Karpe]

On Mon, Feb 25, 2013 at 4:55 PM, Amit Karpe  wrote:

>
>
> On Fri, Nov 30, 2012 at 12:32 PM, Jon LaBadie  wrote:
>
>> On Fri, Nov 30, 2012 at 11:20:37AM +0800, Amit Karpe wrote:
>> > Any idea for my problem.
>>
>> The last line of your first message seems critical:
>>
>> ...
>>
>> > > I could not able to write anything using amdump or dd.
>>
>> If you can't read or write using standard system tools
>> like dd, there is nothing amanda can do about it.
>> Sounds to me like you have hardware problems, either
>> the tape drive or maybe the cables.
>>
>> Jon
>> --
>> Jon H. LaBadie j...@jgcomp.com
>>  11226 South Shore Rd.  (703) 787-0688 (H)
>>  Reston, VA  20190  (609) 477-8330 (C)
>>
>
>
> I had ask HP for support. Their log tool saying my labels are the culprit.
> He is asking me to use only barcode labeling:
> "As per the Amanda Tool output and logs there is one cartridge in the MSL
> which has either missing or worng barcode label or the barcode label is
> properly aligned as per Tape Cartridge
>
> Please remove all the tapes and check if you find such cartridge and if
> you find that then put the Barcode Lable correctly on it and insert it back
> in the same slot
>
> This error occurs because during initialzation before beackup the MSL take
> the Inventory of the cartridges in the MSL and if there is any mislatch
> cartridge, it halts the process of backup"
>
>
> As far as my understanding amanda don't required any barcode labeling.
> Then what is a problem ?
> How can I cross check and confirm that "hardware problems, either the tape
> drive or maybe the cables." ??
>
>
>

Following link have photos of my tapes. Can someone confirm that having
such label will be the problem ???

http://news.karpe.net.in/hp-storageworks-msl2024-tape-library-1-lto-4



> --
> Regards
> Amit Karpe.
> http://www.amitkarpe.com/
> http://news.karpe.net.in/
>



-- 
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/

Re: Error for amlabel

[Amit Karpe]

On Fri, Nov 30, 2012 at 12:32 PM, Jon LaBadie  wrote:

> On Fri, Nov 30, 2012 at 11:20:37AM +0800, Amit Karpe wrote:
> > Any idea for my problem.
>
> The last line of your first message seems critical:
>
> ...
>
> > > I could not able to write anything using amdump or dd.
>
> If you can't read or write using standard system tools
> like dd, there is nothing amanda can do about it.
> Sounds to me like you have hardware problems, either
> the tape drive or maybe the cables.
>
> Jon
> --
> Jon H. LaBadie j...@jgcomp.com
>  11226 South Shore Rd.  (703) 787-0688 (H)
>  Reston, VA  20190  (609) 477-8330 (C)
>


I had ask HP for support. Their log tool saying my labels are the culprit.
He is asking me to use only barcode labeling:
"As per the Amanda Tool output and logs there is one cartridge in the MSL
which has either missing or worng barcode label or the barcode label is
properly aligned as per Tape Cartridge

Please remove all the tapes and check if you find such cartridge and if you
find that then put the Barcode Lable correctly on it and insert it back in
the same slot

This error occurs because during initialzation before beackup the MSL take
the Inventory of the cartridges in the MSL and if there is any mislatch
cartridge, it halts the process of backup"


As far as my understanding amanda don't required any barcode labeling. Then
what is a problem ?
How can I cross check and confirm that "hardware problems, either the tape
drive or maybe the cables." ??


-- 
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/

Re: Error for amlabel

[Jon LaBadie]

On Fri, Nov 30, 2012 at 11:20:37AM +0800, Amit Karpe wrote:
> Any idea for my problem.

The last line of your first message seems critical:

...

> > I could not able to write anything using amdump or dd.

If you can't read or write using standard system tools
like dd, there is nothing amanda can do about it.
Sounds to me like you have hardware problems, either
the tape drive or maybe the cables.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (609) 477-8330 (C)

Re: Error for amlabel

[Amit Karpe]

Any idea for my problem.
Very recently I buy new cleaning cartridge. I have confirm than cleaning
process works.
But while again trying for Labeling I got following errors.

-bash-4.0$ for ((i=1; $i<=3;i++)); do amlabel DailySet1 DailySet1-$i slot
$i; done
labeling tape in slot 1 (tape:/dev/st0):
Reading label...
Error reading 32768 bytes from /dev/st0: Input/output error
Error reading Amanda header.
Found an unlabeled tape.
Writing label DailySet1-1..
Got EIO on /dev/st0, assuming end of tape.
amlabel: Error writing label.

labeling tape in slot 2 (tape:/dev/st0):
Reading label...
Found Amanda tape DailySet1-017
Writing label DailySet1-2..
Error writing final filemark: Input/output error
amlabel: Error closing device.

labeling tape in slot 3 (tape:/dev/st0):
Reading label...
Error reading 32768 bytes from /dev/st0: Input/output error
Error reading Amanda header.
Found an unlabeled tape.
Writing label DailySet1-3..
Got EIO on /dev/st0, assuming end of tape.
amlabel: Error writing label.

Someone please guide me !

On Thu, Oct 11, 2012 at 7:38 PM, Amit Karpe  wrote:

> Hi All,
> While writing label by using following command I got these errors.
> -bash-4.0$ amlabel DailySet1 reset
> amlabel: label reset doesn't match labelstr "^DailySet1-[0-9][0-9]*$"
> -bash-4.0$ amlabel DailySet1 reset
> labeling tape in slot 22 (tape:/dev/nst0):
> Reading label...
> Error reading 32768 bytes from /dev/nst0: Input/output error
> Error reading Amanda header.
> Found an unlabeled tape.
> Writing label reset..
> Error writing final filemark: Input/output error
> amlabel: Error closing device.
>
>
> -bash-4.0$ mtx -f /dev/sg2 status
>   Storage Changer /dev/sg2:1 Drives, 24 Slots ( 1 Import/Export )
> Data Transfer Element 0:Full (Storage Element 22 Loaded)
>   Storage Element 1:Empty
>   Storage Element 2:Full
>   Storage Element 3:Full
>   Storage Element 4:Full
>   Storage Element 5:Full
>   Storage Element 6:Full
>   Storage Element 7:Full
>   Storage Element 8:Full
>   Storage Element 9:Full
>   Storage Element 10:Full
>   Storage Element 11:Full
>   Storage Element 12:Full
>   Storage Element 13:Full
>   Storage Element 14:Full
>   Storage Element 15:Full
>   Storage Element 16:Full
>   Storage Element 17:Full
>   Storage Element 18:Full
>   Storage Element 19:Full
>   Storage Element 20:Full
>   Storage Element 21:Full
>   Storage Element 22:Empty
>   Storage Element 23:Full
>   Storage Element 24 IMPORT/EXPORT:Empty
>
>
> #tail -f /var/log/messages
> Oct 11 18:58:37 borneo kernel: mptscsih: ioc0: task abort: SUCCESS
> (sc=88012db85600)
> Oct 11 18:58:37 borneo kernel: st0: Error 8 (driver bt 0x0, host bt
> 0x8).
> Oct 11 19:22:30 borneo kernel: st0: Sense Key : Medium Error [current]
> Oct 11 19:22:30 borneo kernel: Info fld=0x1
> Oct 11 19:22:30 borneo kernel: st0: Add. Sense: Write error
>
>
> tpchanger "chg-zd-mtx"
> #tapedev "tape:/dev/st0"# the no-rewind tape device to be
> used
> tapedev "tape:/dev/nst0"# the no-rewind tape device to be
> used
> changerfile "/etc/amanda/DailySet1/changer.conf"
> changerdev "/dev/sg2"
> tapetype HP-LTO4# what kind of tape it is (see tapetypes
> below)
> define tapetype HP-LTO4 {
> comment "just produced by tapetype prog (hardware compression on)"
> length 772096 mbytes
> filemark 0 kbytes
> speed 71093 kps
> }
>
>
> Any suggestions ?
> I could not able to write anything using amdump or dd.
>



-- 
Regards
Amit Karpe.
http://www.amitkarpe.com/
http://news.karpe.net.in/

Re: amlabel --barcode fails

[Jean-Louis Martineau]

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

[Dennis Benndorf]

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

[Dennis Benndorf]

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

[Jean-Louis Martineau]

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

amlabel --barcode fails

[Dennis Benndorf]

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 ''...
**
ERROR:device.c:1144:device_start: assertion failed: (mode != ACCESS_WRITE || 
label != NULL)
Aborted

amlabel debug file is attached.

Regards,
Dennis

-- 
NEU: FreePhone - kostenlos mobil telefonieren und surfen!   
Jetzt informieren: http://www.gmx.net/de/go/freephone


amlabel.20110418152241.debug
Description: application/extension-debug

Re: [Amanda-users] amlabel error on 3.1.0beta1

[Jean-Louis Martineau]

Look in the amlabel.*.debug file, it might gives a better error message.

Jean-Louis

whale wrote:

Hi,
I testing amanda-3.1.0rc08-20100317 with chg:robot on ubuntu server 8.04 LTS 
and everything is working fine. I tried to upgrade to beta1

I'm able to compile and install from source. Config options are the same like 
on rc08


  

./configure --prefix=/usr --bindir=/usr/sbin --libexecdir=/usr/lib/amanda 
--without-amlibexecdir --without-amperldir --sysconfdir=/etc 
--sharedstatedir=/var/lib --localstatedir=/var/lib --with-user=amandabackup 
--with-group=disk --with-tcpportrange=5,50100 --with-udpportrange=840,860 
--with-debugging=/var/log/amanda 
--with-gnutar-listdir=/var/lib/amanda/gnutar-lists 
--with-index-server=localhost --with-bsd-security 
--with-smbclient=/usr/bin/smbclient --with-amandahosts --with-ssh-security 
--with-bsdtcp-security --with-bsdudp-security --without-ipv6




when I run:
amlabel -f DailySet1 DLL4 slot 1

I get this error:



  

amlabel: Undefined subroutine &Amanda::Changer::cluck called at 
/usr/lib/amanda/perl/Amanda/Changer.pm line 970




whan can be the cause of this problem?

my amanda.conf:


  

org "Test DailySet1"  # your organization name for reports
mailer "/usr/bin/mail"   
mailto "t...@test"# space separated list of operators at your site
send-amreport-on all   
dumpuser "amandabackup"


tapetype "DIL"# what kind 
of tape it is

dumpcycle 7 days# the number of 
days in the normal dump cycle
runspercycle 5 days # the number of 
amdump runs in dumpcycle days
tapecycle 15# the number of tapes in rotation
usetimestamps yes
runtapes 10 # number of tapes to be used in a single run of amdump
maxdumpsize 1gb   


labelstr "^DL[0-9][0-9][0-9][0-9][A-Z][0-9]*$"  # label 
constraint regex: all tapes must match
   


diskfile "/etc/amanda/DailySet1/disklist"
infofile "/etc/amanda/DailySet1/curinfo"# database 
DIRECTORY
logdir   "/etc/amanda/DailySet1/logs"   # log directory 
indexdir "/etc/amanda/DailySet1/index"  # index directory   
tapelist "/etc/amanda/DailySet1/tapelist"   # list of used tapes


dtimeout 43200 # number of idle 
seconds before a dump is aborted
ctimeout 60 # max number of 
secconds amcheck waits for each client
etimeout 43200   # number of seconds per filesystem for estimates 
inparallel 10 
dumporder "sssS"  
taperalgo first   
displayunit "g"   
netusage 1 gbps   
maxdumps 1
bumpsize20m   
bumppercent 20
bumpdays1 day 
amrecover_changer   "changer" 
device_output_buffer_size 1280k   
reserve 20  

[Amanda-users] amlabel error on 3.1.0beta1

[whale]

Hi,
I testing amanda-3.1.0rc08-20100317 with chg:robot on ubuntu server 8.04 LTS 
and everything is working fine. I tried to upgrade to beta1

I'm able to compile and install from source. Config options are the same like 
on rc08


> ./configure --prefix=/usr --bindir=/usr/sbin --libexecdir=/usr/lib/amanda 
> --without-amlibexecdir --without-amperldir --sysconfdir=/etc 
> --sharedstatedir=/var/lib --localstatedir=/var/lib --with-user=amandabackup 
> --with-group=disk --with-tcpportrange=5,50100 --with-udpportrange=840,860 
> --with-debugging=/var/log/amanda 
> --with-gnutar-listdir=/var/lib/amanda/gnutar-lists 
> --with-index-server=localhost --with-bsd-security 
> --with-smbclient=/usr/bin/smbclient --with-amandahosts --with-ssh-security 
> --with-bsdtcp-security --with-bsdudp-security --without-ipv6


when I run:
amlabel -f DailySet1 DLL4 slot 1

I get this error:



> amlabel: Undefined subroutine &Amanda::Changer::cluck called at 
> /usr/lib/amanda/perl/Amanda/Changer.pm line 970


whan can be the cause of this problem?

my amanda.conf:


> 
> org "Test DailySet1"  # your organization name for reports
> mailer "/usr/bin/mail"   
> mailto "t...@test"# space separated list 
> of operators at your site
> send-amreport-on all  
>  
> dumpuser "amandabackup"   
>  
> 
> tapetype "DIL"# what kind 
> of tape it is
> 
> dumpcycle 7 days# the number 
> of days in the normal dump cycle
> runspercycle 5 days # the number 
> of amdump runs in dumpcycle days
> tapecycle 15# the number 
> of tapes in rotation
> usetimestamps yes 
>
> runtapes 10 # number of 
> tapes to be used in a single run of amdump
> maxdumpsize 1gb   
> 
> 
> labelstr "^DL[0-9][0-9][0-9][0-9][A-Z][0-9]*$"  # 
> label constraint regex: all tapes must match
>   
>  
> 
> diskfile "/etc/amanda/DailySet1/disklist"
> infofile "/etc/amanda/DailySet1/curinfo"# 
> database DIRECTORY
> logdir   "/etc/amanda/DailySet1/logs"   # log 
> directory 
> indexdir "/etc/amanda/DailySet1/index"  # index 
> directory   
> tapelist "/etc/amanda/DailySet1/tapelist"   # list of 
> used tapes
> 
> dtimeout 43200 # number of 
> idle seconds before a dump is aborted
> ctimeout 60 # max number 
> of secconds amcheck waits for each client
> etimeout 43200   # number of 
> seconds per filesystem for estimates 
> inparallel 10 
> 
> dumporder "sssS"  
> 
> taperalgo first   
> 
> displayunit "g"   
> 
> netusage 1 gbps   
> 
> maxdumps 1
> 
> bumpsize20m   
> 
> bumppercent 20
> 
> bumpdays1 day 
> 
> amrecover_chan

Re: [Amanda-users] amlabel syntax error

[Chris Hoogendyk]

crom84 wrote:

I had a reply at another forum that is linked to this one, but I do not see the 
reply anywhere in this forum.

I'm still stuck  anybody? Anybody at all?


I don't see a response to Jean-Louis Martineau's suggestions.

You did "su backup ./amlabel daily daily-21 slot21" originally. I see 
two or three issues with that.


For starters, I would use "su - backup ..." so that you actually get the 
environment of the backup user.


Second, "./..." has no meaning out of context of what your environment 
is and what your working directory is. You should use the full path as 
Jean-Louis suggested. Your use of "./..." implies that you have a script 
to do the labels or that you have cd'd into /usr/local/sbin, which is 
not standard procedure at all.


Third, as Jean-Louis said, you want to tell amlabel "slot 21" (note the 
space). The syntax (see `man amlabel`) is to give it the slot keyword 
followed by the slot number, not to tell it the name of a directory 
corresponding to the slot.


So, try

# su - backup amlabel daily daily-21 slot 21


--
---

Chris Hoogendyk

-
  O__   Systems Administrator
 c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst 




--- 


Erdös 4

[Amanda-users] amlabel syntax error

[crom84]

I had a reply at another forum that is linked to this one, but I do not see the 
reply anywhere in this forum.

I'm still stuck  anybody? Anybody at all?  :D

+--
|This was sent by cro...@hotmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: [Amanda-users] amlabel syntax error

[Jean-Louis Martineau]

The syntax is: amlabel daily daily-21 slot 21

Which amlabel are you executing? Specify the full path of the installed 
binary.


Jean-Louis

crom84 wrote:

Hi all :)

I am trying to use amlabel to label some more slots that I have created for my 
"daily" backup configuration.

Here is the command I am running: "su backup ./amlabel daily daily-21 slot21".  The set is "daily", the label 
I want to set is "daily-21" and the name of the folder (e.g. slot) is "slot21". Also, the backup user is 
"backup".

It results in the following error: "./amlabel: 1: Syntax error: "(" unexpected".

Any help would be greatly appreciated :)

+--
|This was sent by cro...@hotmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


  

[Amanda-users] amlabel syntax error

[crom84]

Hi all :)

I am trying to use amlabel to label some more slots that I have created for my 
"daily" backup configuration.

Here is the command I am running: "su backup ./amlabel daily daily-21 slot21".  
The set is "daily", the label I want to set is "daily-21" and the name of the 
folder (e.g. slot) is "slot21". Also, the backup user is "backup".

It results in the following error: "./amlabel: 1: Syntax error: "(" unexpected".

Any help would be greatly appreciated :)

+--
|This was sent by cro...@hotmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

Re: multiple questions: amlabel, solaris device for tape drive etc.

[Stefan G. Weichinger]

Dustin J. Mitchell schrieb:
> On Mon, Jun 22, 2009 at 4:04 PM, Stefan G. Weichinger wrote:
>> Could you describe briefly why?
> 
> Amanda used to need a non-rewinding tape device because it would close
> and re-open the device (sometimes in a different process) between
> files.  It no longer does this.

Umm, sounds like improvement ... this different-process-thing sounds
unreliable to me ...

>> What has changed in the code/behavior?
> 
> Everything -- the Device API was a complete rewrite of all device
> handling in Amanda.

fine ;-)

Thanks, Stefan

Re: multiple questions: amlabel, solaris device for tape drive etc.

[Dustin J. Mitchell]

On Mon, Jun 22, 2009 at 4:04 PM, Stefan G. Weichinger wrote:
> Could you describe briefly why?

Amanda used to need a non-rewinding tape device because it would close
and re-open the device (sometimes in a different process) between
files.  It no longer does this.

> What has changed in the code/behavior?

Everything -- the Device API was a complete rewrite of all device
handling in Amanda.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: multiple questions: amlabel, solaris device for tape drive etc.

[Stefan G. Weichinger]

Dustin J. Mitchell schrieb:
> On Mon, Jun 22, 2009 at 9:00 AM, Darin
> Perusich wrote:
>> I always use /dev/rmt/0cn device on Solaris but if I'm not mistaken you
>> no longer need to specify the no-rewind device for the 2.6 release of
>> Amanda. The 'b' is to use BSD behavior instead of SRV4 for error
>> handling, see the mtio man page for more details.
> 
> You are correct -- amanda no longer needs a non-rewinding tape.

Could you describe briefly why?
What has changed in the code/behavior?

Thanks, Stefan

Re: multiple questions: amlabel, solaris device for tape drive etc.

[Dustin J. Mitchell]

On Mon, Jun 22, 2009 at 9:00 AM, Darin
Perusich wrote:
> I always use /dev/rmt/0cn device on Solaris but if I'm not mistaken you
> no longer need to specify the no-rewind device for the 2.6 release of
> Amanda. The 'b' is to use BSD behavior instead of SRV4 for error
> handling, see the mtio man page for more details.

You are correct -- amanda no longer needs a non-rewinding tape.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: multiple questions: amlabel, solaris device for tape drive etc.

[Brian Cuttler]

Andreas,

The type device is described in # man st(7D).

Amanda has a value in amanda.conf called labelstr

(One) of mine looks like this
labelstr "^INFO[0-9][0-9]*$"

that is (starts with) INFO and has at least two numerics (then ends)

I believe there are newer faster ways to label tapes, even a label
blank tape option during amdump, but I still tend to label them 
manually, or in the case of a jukebox (I have several, including
2 SL24s) a magazine at a time using a very simple script (and that
only to avoid my own command line editing errors).


On Mon, Jun 22, 2009 at 10:38:24AM +0200, Andreas Kuntzagk wrote:
> Hi,
> 
> I'm quite new to amanda (and to backing up to tape as well). I already 
> managed to create a conf for our changer (Sun SL24). But I'm still 
> unsure what is the right device for the tape drive.
> 
>  # ls /dev/rmt/
> 0 0b0bn   0c0cb   0cbn  0cn   0h0hb   0hbn  0hn   0l 
> 0lb   0lbn  0ln   0m0mb   0mbn  0mn   0n0u0ub   0ubn  0un
> 
> So far I'm using /dev/rmt/0ubn AFAIK the u stands for Ultra-density, the 
> n for non-rewinding (Amanda needs that, right?) But I'm unsure about the 
> b. What does it mean? I managed to read and write to this device with 
> tar. Also amtapetype gave me some sensible values for this. (actually I 
> used the rewinding device at that time, but the non-rewinding shouldn't 
> differ)
> 
> I now also managed to label a tape using amlabel. Now my question is: 
> How do I label all tapes in the changer? Do I use some kind of pattern 
> or can I label them as I like?
> Is there a command to label all tapes at once?
> 
> regards, Andreas
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   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: multiple questions: amlabel, solaris device for tape drive etc.

[Darin Perusich]

I always use /dev/rmt/0cn device on Solaris but if I'm not mistaken you
no longer need to specify the no-rewind device for the 2.6 release of
Amanda. The 'b' is to use BSD behavior instead of SRV4 for error
handling, see the mtio man page for more details.

Use amlabel to label the tapes, you'll need to load and unload each of
them. The pattern is derived from the 'labelstr' and 'tapecycle' which
was specified in your amanda.conf. If 'labelstr=^nightly_0-9*$' and
'tapecycle=23' then your tape labels would be nightly_1 through nightly_23.

Andreas Kuntzagk wrote:
> Hi,
> 
> I'm quite new to amanda (and to backing up to tape as well). I already
> managed to create a conf for our changer (Sun SL24). But I'm still
> unsure what is the right device for the tape drive.
> 
>  # ls /dev/rmt/
> 0 0b0bn   0c0cb   0cbn  0cn   0h0hb   0hbn  0hn   0l
> 0lb   0lbn  0ln   0m0mb   0mbn  0mn   0n0u0ub   0ubn  0un
> 
> So far I'm using /dev/rmt/0ubn AFAIK the u stands for Ultra-density, the
> n for non-rewinding (Amanda needs that, right?) But I'm unsure about the
> b. What does it mean? I managed to read and write to this device with
> tar. Also amtapetype gave me some sensible values for this. (actually I
> used the rewinding device at that time, but the non-rewinding shouldn't
> differ)
> 
> I now also managed to label a tape using amlabel. Now my question is:
> How do I label all tapes in the changer? Do I use some kind of pattern
> or can I label them as I like?
> Is there a command to label all tapes at once?
> 
> regards, Andreas

-- 
Darin Perusich
Unix Systems Administrator
Cognigen Corporation
395 Youngs Rd.
Williamsville, NY 14221
Phone: 716-633-3463
Email: darin...@cognigencorp.com

multiple questions: amlabel, solaris device for tape drive etc.

[Andreas Kuntzagk]

Hi,

I'm quite new to amanda (and to backing up to tape as well). I already 
managed to create a conf for our changer (Sun SL24). But I'm still 
unsure what is the right device for the tape drive.


 # ls /dev/rmt/
0 0b0bn   0c0cb   0cbn  0cn   0h0hb   0hbn  0hn   0l 
0lb   0lbn  0ln   0m0mb   0mbn  0mn   0n0u0ub   0ubn  0un


So far I'm using /dev/rmt/0ubn AFAIK the u stands for Ultra-density, the 
n for non-rewinding (Amanda needs that, right?) But I'm unsure about the 
b. What does it mean? I managed to read and write to this device with 
tar. Also amtapetype gave me some sensible values for this. (actually I 
used the rewinding device at that time, but the non-rewinding shouldn't 
differ)


I now also managed to label a tape using amlabel. Now my question is: 
How do I label all tapes in the changer? Do I use some kind of pattern 
or can I label them as I like?

Is there a command to label all tapes at once?

regards, Andreas

Re: amlabel problem - reading chunks from holding area

[Stefan G. Weichinger]

Brian Cuttler schrieb:
> Chris,
> 
> I _so_ love amanda!

Nice to hear that ;)

Stefan

Re: amlabel problem - reading chunks from holding area

[Brian Cuttler]

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

[Chris Hoogendyk]

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

[Brian Cuttler]

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

Re: amlabel problem

[Brian Cuttler]

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

[Stefan G. Weichinger]

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

amlabel problem

[Brian Cuttler]

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

I am running the amanda server 2.4.4p1-20030716
on IRIX 6.5.28m.

I've checked the tapes, they are labeled as proper for the
SDLT 220 drive, and the first few where ok, nothing has changed
since we started to have failures with the amlabel command.

I've tried resetting the drive (HW reset as well as SW reset), cleaning
it (cleaning light was NOT on), but to no avail.

Any suggestions are welcome,

TIA,

Brian
---
   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: not an amanda tape ??? [ SOLVED ]

[Michael D Schleif]

[ [ [ 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 ???

[Paul Bijnens]

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

Please, ANY ideas ???


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

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

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

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

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

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


What do you think?



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

Pure guesses:

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

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


--
Paul Bijnens, xplanation Technology ServicesTel  +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax  +32 16 397.512
http://www.xplanation.com/  email:  [EMAIL PROTECTED]
***
* I think I've got the hang of it now:  exit, ^D, ^C, ^\, ^Z, ^Q, ^^, *
* F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  abort,  hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  shutdown, *
* init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... *
* ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm out  *
***

Re: amlabel: not an amanda tape ???

[Stefan G. Weichinger]

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

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

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

Stefan

amlabel: not an amanda tape ???

[Michael D Schleif]

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?

-- 
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

amlabel: amlabel: not an amanda tape ???

[Michael D Schleif]

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?

-- 
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: newbie ? - tapeless operation -> amlabel error

[Paul Bijnens]

On 2007-05-29 22:11, Robert Echlin wrote:
> Hi, Stefan,
> In your HOWTO, you have the following configuration for tapedev:
> 
>   tapedev  "file:/amandatapes/daily" 
> 
> Should that be file:// ?

No a single slash is fine.

> 
> Ref: http://forums.zmanda.com/archive/index.php/t-470.html

Note the original poster had:

   tapedev "file:/space/amanda-vtapes/tape"

but explained that the subdir of amanda-vtapes is "daily" and not "tape"
So this is the correct value:

   tapedev "file:/space/amanda-vtapes/daily/slots"

and you may add as many slashes as you want, as Unix does not
threat those special:
  "ls //"   is equivalent to "ls /"  or even "ls ///"


-- 
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: newbie ? - tapeless operation -> amlabel error

[Stefan G. Weichinger]

Jeanna Geier schrieb:
> Thanks so much to both you and Rob for the great info; I'll
> start over and follow this HOWTO from the get-go and see
> where I end up.

Feel free to come back again here before you end up completely.

;)

Stefan

-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 

Re: newbie ? - tapeless operation -> amlabel error

[Stefan G. Weichinger]

Jeanna Geier schrieb:
> Thanks so much for the reply!
> 
> I can change that parameter value, however, in the 'HOWTO'
> I was following, it tells me to comment out that specific
> parameter so I don't think that will help:
> 
>-
>/etc/amanda/DailySet1/amanda.conf
>-
># These are the options that differ from  
>examples/amanda.conf
> 
>dumpcycle 14 days
>tapecycle 14
>#runspercycle  # defaults to 1 per day
> 
>runtapes 1
>tpchanger "chg-multi"
>changerfile "/etc/amanda/DailySet1/changer.conf"
># Comment out tapedev and changerdev
> 
> Thanks for the input, though - I'll make sure to
> double-check the value so when I do get ready to write it
> to tape, the value is correct!

This is OK for using the changer-script chg-multi.
chg-disk is preferred for quite a while now by most people.

Stefan

-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 

Re: newbie ? - tapeless operation -> amlabel error

[Stefan G. Weichinger]

Robert Echlin schrieb:
> Hi, Stefan,
> In your HOWTO, you have the following configuration for tapedev:
> 
>   tapedev  "file:/amandatapes/daily" 
> 
> Should that be file:// ?

What works for you?

;)

Checked a working vtape-setup of one of my customers right now (got a
valid report from that system an hour ago):

It should be

file:/

(one slash) as mentioned in the HOWTO.

"file:" chooses the driver (would have to browse the docs for the spot
where this is described in detail), the part after the ":" gives the
directory in this case.

Greets,
Stefan

-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 

Re: newbie ? - tapeless operation -> amlabel error

[Jeanna Geier]

Thanks so much to both you and Rob for the great info; I'll
start over and follow this HOWTO from the get-go and see
where I end up.

Thanks again for your time and input, it is very much
appreciated!!
-jg

On Tue, 29 May 2007 21:57:02 +0200
 "Stefan G. Weichinger" <[EMAIL PROTECTED]> wrote:
> Jeanna Geier schrieb:
> > Hello- Thank you for the reply.
> > 
> > "Are you *sure* you want your vtapes in /usr/src/amanda
> ?"
> > No - I'm not sure of anything for sure, I'm just trying
> to
> > get this running! =)  But, have not been successful!
> 
> Jeanna,
> 
> storing backups in /usr/src isn't compliant to the way of
> doing things.
> /usr/src is for source-text, like the linux kernel, but
> not for backups.
> 
> But this is not your primary problem in setting up
> amanda.
> 
> > I started with that HOWTO
> > (http://www.amanda.org/docs/howto-filedriver.html), and
> was
> > told that for testing, they wanted it to write to the
> > harddisk vs. tapes, so I found the other link; how do I
> > know what to parameters to change exactly?
> 
> Simple answer (simple for me): Follow the HOWTO exactly.
> 
> Longer answer (A bit simpler for you):
> 
> You didn't follow the HOWTO.
> 
> For example:
> 
> tpchanger "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
> 
> should be more like
> 
> tpchanger "chg-disk"
> 
> Your config points to *something* but does not configure
> amanda
> correctly. No need for paths here. This parameter chooses
> a script
> inside amanda's own directories, not inside a slot of
> your virtual changer.
> 
> --
> 
> Just read and follow the HOWTO from start, again.
> It has worked for quite a lot of people so far.
> 
> I'll be happy to improve it when necessary, but I think
> you didn't read
> it in detail.
> 
> Also think about your paths.
> 
> It is important for you and your backups (*and restores*)
> to understand
> what you do and why you do things.
> 
> --
> 
> And Rob has provided lots of infos in the meantime as
> well ;)
> 
> Stefan
> 
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 



Jeanna Geier
System Administrator
Webteam, Inc.
[EMAIL PROTECTED]
http://www.webteam.net

ph: 608.788.8100
fx: 608.788.6613
tf: 866.788.0023

RE: newbie ? - tapeless operation -> amlabel error

[Robert Echlin]

Hi, Stefan,
In your HOWTO, you have the following configuration for tapedev:

  tapedev  "file:/amandatapes/daily" 

Should that be file:// ?

Ref: http://forums.zmanda.com/archive/index.php/t-470.html

Thanks,
Rob

--
Rob Echlin
Software Development Environment Prime
Espial IPTV
Rechlin -at- espial.com
Phone: +1 613-230-4770 ext 1150
www.espial.com

 Espial Group Inc. Confidential 
Important Notice: This communication is intended to be received only by
the individual or entity to whom or to which it is addressed and may
contain information that is privileged, confidential and/or subject to
copyright. Any unauthorized use, copying, review or disclosure of this
communication is strictly prohibited. If you have received this
communication in error, please delete the message and notify the sender
by reply email. Thank you for your cooperation.
 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stefan G. Weichinger
Sent: Tuesday, May 29, 2007 3:57 PM
To: amanda-users@amanda.org
Subject: Re: newbie ? - tapeless operation -> amlabel error


Jeanna Geier schrieb:
> Hello- Thank you for the reply.
> 
> "Are you *sure* you want your vtapes in /usr/src/amanda ?"
> No - I'm not sure of anything for sure, I'm just trying to
> get this running! =)  But, have not been successful!

Jeanna,

storing backups in /usr/src isn't compliant to the way of doing things.
/usr/src is for source-text, like the linux kernel, but not for backups.

But this is not your primary problem in setting up amanda.

> I started with that HOWTO
> (http://www.amanda.org/docs/howto-filedriver.html), and was
> told that for testing, they wanted it to write to the
> harddisk vs. tapes, so I found the other link; how do I
> know what to parameters to change exactly?

Simple answer (simple for me): Follow the HOWTO exactly.

Longer answer (A bit simpler for you):

You didn't follow the HOWTO.

For example:

tpchanger "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"

should be more like

tpchanger "chg-disk"

Your config points to *something* but does not configure amanda
correctly. No need for paths here. This parameter chooses a script
inside amanda's own directories, not inside a slot of your virtual
changer.

--

Just read and follow the HOWTO from start, again.
It has worked for quite a lot of people so far.

I'll be happy to improve it when necessary, but I think you didn't read
it in detail.

Also think about your paths.

It is important for you and your backups (*and restores*) to understand
what you do and why you do things.

--

And Rob has provided lots of infos in the meantime as well ;)

Stefan

-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 

Re: newbie ? - tapeless operation -> amlabel error

[Jeanna Geier]

Thanks so much for the reply!

I can change that parameter value, however, in the 'HOWTO'
I was following, it tells me to comment out that specific
parameter so I don't think that will help:

   -
   /etc/amanda/DailySet1/amanda.conf
   -
   # These are the options that differ from  
   examples/amanda.conf

   dumpcycle 14 days
   tapecycle 14
   #runspercycle  # defaults to 1 per day

   runtapes 1
   tpchanger "chg-multi"
   changerfile "/etc/amanda/DailySet1/changer.conf"
   # Comment out tapedev and changerdev

Thanks for the input, though - I'll make sure to
double-check the value so when I do get ready to write it
to tape, the value is correct!

-jg
> 
> 
> On Tue, 29 May 2007 15:23:27 -0400
>  "Robert Echlin" <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I ran into a similar message :
> > "
> > amlabel: could not load slot "1": could not read result
> > from
> > "/usr/lib/amanda/chg-disk"
> > "
> > 
> > I found the answer on the forums:
> > http://forums.zmanda.com/archive/index.php/t-470.html
> > 
> > In your amanda.conf, you need to define:
> > tapedev "file://path/to/your/slots"
> > 
> > Rob
> > 
> > 
> > -Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of
> > Jeanna Geier
> > Sent: Tuesday, May 29, 2007 3:01 PM
> > To: amanda-users@amanda.org
> > Subject: newbie ? - tapeless operation -> amlabel error
> > 
> > 
> > Hi All!
> > 
> > I'm new to Amanda and am trying to configure it for
> > tapeless operation using the instructions in the
> > following
> > link:
> > http://amanda.sourceforge.net/fom-serve/cache/191.html.
> > I'm
> > down to the labeling in step #5 'Use amlabel to label
> the
> > tapes'; however, when I run the amlabel command, I get
> > the
> > following error:
> > [EMAIL PROTECTED]:/usr/src/amanda-2.5.2/sbin$ amlabel
> > DailySet3 DailySet301 slot 1
> > amlabel: could not load slot "1": could not read result
> > from "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
> > 
> > I'm running VERSION 2.5.2 on Linux.
> > 
> > My 'amanda.conf' file:
> > 
> > ... Stuff cut ...
> > 
> > runtapes 1 # number of tapes to be used in a single run
> > of
> > amdump
> > tpchanger
> "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
> > #
> > the tape-changer glue script
> > #tapedev "/dev/nst0" # the no-rewind tape device to be
> > used
> > rawtapedev "/dev/null" # the raw device to be used
> (ftape
> > only)
> > 
> > ... Stuff cut ...
> > 
> > --
> > Rob Echlin
> > Software Development Environment Prime
> > Espial IPTV
> > Rechlin -at- espial.com
> > Phone: +1 613-230-4770 ext 1150
> > www.espial.com
> > 
> >  Espial Group Inc. Confidential 
> > Important Notice: This communication is intended to be
> > received only by
> > the individual or entity to whom or to which it is
> > addressed and may
> > contain information that is privileged, confidential
> > and/or subject to
> > copyright. Any unauthorized use, copying, review or
> > disclosure of this
> > communication is strictly prohibited. If you have
> > received this
> > communication in error, please delete the message and
> > notify the sender
> > by reply email. Thank you for your cooperation.
> >  
> 
> 
> 
> Jeanna Geier
> System Administrator
> Webteam, Inc.
> [EMAIL PROTECTED]
> http://www.webteam.net
> 
> ph: 608.788.8100
> fx: 608.788.6613
> tf: 866.788.0023



Jeanna Geier
System Administrator
Webteam, Inc.
[EMAIL PROTECTED]
http://www.webteam.net

ph: 608.788.8100
fx: 608.788.6613
tf: 866.788.0023

Re: newbie ? - tapeless operation -> amlabel error

[Stefan G. Weichinger]

Stefan G. Weichinger schrieb:

> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 


g  stupid thunderbird-extension again 

sorry

S

Re: newbie ? - tapeless operation -> amlabel error

[Stefan G. Weichinger]

Jeanna Geier schrieb:
> Hello- Thank you for the reply.
> 
> "Are you *sure* you want your vtapes in /usr/src/amanda ?"
> No - I'm not sure of anything for sure, I'm just trying to
> get this running! =)  But, have not been successful!

Jeanna,

storing backups in /usr/src isn't compliant to the way of doing things.
/usr/src is for source-text, like the linux kernel, but not for backups.

But this is not your primary problem in setting up amanda.

> I started with that HOWTO
> (http://www.amanda.org/docs/howto-filedriver.html), and was
> told that for testing, they wanted it to write to the
> harddisk vs. tapes, so I found the other link; how do I
> know what to parameters to change exactly?

Simple answer (simple for me): Follow the HOWTO exactly.

Longer answer (A bit simpler for you):

You didn't follow the HOWTO.

For example:

tpchanger "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"

should be more like

tpchanger "chg-disk"

Your config points to *something* but does not configure amanda
correctly. No need for paths here. This parameter chooses a script
inside amanda's own directories, not inside a slot of your virtual changer.

--

Just read and follow the HOWTO from start, again.
It has worked for quite a lot of people so far.

I'll be happy to improve it when necessary, but I think you didn't read
it in detail.

Also think about your paths.

It is important for you and your backups (*and restores*) to understand
what you do and why you do things.

--

And Rob has provided lots of infos in the meantime as well ;)

Stefan

-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 
Stefan G. Weichinger
amanda core team member
mailto: [EMAIL PROTECTED]
pgp:3C64175D
-- 
oops! linux consulting & implementation
http://www.oops.co.at
-- 

RE: newbie ? - tapeless operation -> amlabel error

[Robert Echlin]

Hi, Jeanna,

The setting I mentioned, pointing tapedev at the "slots" directory on
disk, is what I use for writing to virtual tapes, i.e. writing to disk.
Did you notice that the HOWTO you are using is dated Nov 2001? A lot has
changed since then. Try the HOWTO in the wiki at:
http://wiki.zmanda.com/index.php/Test_environment_with_virtual_tapes
<http://wiki.zmanda.com/index.php/Test_environment_with_virtual_tapes> 

I also referred to other pages on the wiki:
http://wiki.zmanda.com/index.php/File_driver
<http://wiki.zmanda.com/index.php/File_driver> 
http://wiki.zmanda.com/index.php/Changers
<http://wiki.zmanda.com/index.php/Changers> 

And when I was creating many slots this afternoon, I recorded the
following notes (copied from the wiki I use internally at work). Lots of
this is specific to my configuration, like the user names. Note that the
phrase `seq 1 50` and similar are enclosed in back-quotes and all of
this was done in the bash shell:

Mount the new disk on /mnt/Amanda/Set2 where 2 is the number for the
backup disk, could be 3 for instance 

*   As root, create vtapes folder on the backup disk, set owner
amandabackup user, group disk, not readable or executable by "other" 

1.  mkdir vtapes 

2.  chown amandabackup:disk vtapes 

3.  chmod 750 vtapes 

*   Change to the amandabackup user. 

*   Create a DailySet2 folder inside vtapes 

*   Create slots inside vtapes/DailySet2 

*   for i in `seq 1 50`; do mkdir slot$i; done 

*   Put it "online" by creating the required data symlink 

*   ln -s slot1 data 

*   Check it - this command should return ONLINE 

*   ammt -f file:/mnt/Amanda/Set2/vtapes/DailySet2/slots/ status 

*   Label the tapes - the changer must be "online" first 

*   for i in `seq 1 9`; do amlabel DailySet2 DailySet2-0${i}; done 

*   for i in `seq 10 50`; do amlabel DailySet2 DailySet2-${i}; done 

*   Check it's OK 

*   amcheck DailySet2

Rob

-Original Message-
From: Jeanna Geier [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ]
Sent: Tuesday, May 29, 2007 3:33 PM
To: amanda-users@amanda.org; Robert Echlin
Subject: Re: newbie ? - tapeless operation -> amlabel error


Thanks so much for the reply!

I can change that parameter value, however, in the 'HOWTO'
I was following, it tells me to comment out that specific
parameter so I don't think that will help:

   -
   /etc/amanda/DailySet1/amanda.conf
   -
   # These are the options that differ from 
   examples/amanda.conf

   dumpcycle 14 days
   tapecycle 14
   #runspercycle  # defaults to 1 per day

   runtapes 1
   tpchanger "chg-multi"
   changerfile "/etc/amanda/DailySet1/changer.conf"
   # Comment out tapedev and changerdev

Thanks for the input, though - I'll make sure the
double-check the value so when I do get ready to write it
to tape, the value is correct!

-jg


On Tue, 29 May 2007 15:23:27 -0400
 "Robert Echlin" <[EMAIL PROTECTED]> wrote:
> Hi,
> I ran into a similar message :
> "
> amlabel: could not load slot "1": could not read result
> from
> "/usr/lib/amanda/chg-disk"
> "
>
> I found the answer on the forums:
> http://forums.zmanda.com/archive/index.php/t-470.html
<http://forums.zmanda.com/archive/index.php/t-470.html> 
>
> In your amanda.conf, you need to define:
> tapedev "file://path/to/your/slots  "
>
> Rob
>
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> ] On Behalf Of
> Jeanna Geier
> Sent: Tuesday, May 29, 2007 3:01 PM
> To: amanda-users@amanda.org
> Subject: newbie ? - tapeless operation -> amlabel error
>
>
> Hi All!
>
> I'm new to Amanda and am trying to configure it for
> tapeless operation using the instructions in the
> following
> link:
> http://amanda.sourceforge.net/fom-serve/cache/191.html
<http://amanda.sourceforge.net/fom-serve/cache/191.html> .
> I'm
> down to the labeling in step #5 'Use amlabel to label the
> tapes'; however, when I run the amlabel command, I get
> the
> following error:
> [EMAIL PROTECTED]:/usr/src/amanda-2.5.2/sbin$ amlabel
> DailySet3 DailySet301 slot 1
> amlabel: could not load slot "1": could not read result
> from "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
>
> I'm running VERSION 2.5.2 on Linux.
>
> My 'amanda.conf' file:
>
> ... Stuff cut ...
>
> runtapes 1 # number of tapes to be used in a single run
> of
> amdump
> tpchanger "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
> #
> the tape-changer glue script
> #tapedev "/

RE: newbie ? - tapeless operation -> amlabel error

[Robert Echlin]

Hi,
I ran into a similar message :
"
amlabel: could not load slot "1": could not read result from
"/usr/lib/amanda/chg-disk"
"

I found the answer on the forums:
http://forums.zmanda.com/archive/index.php/t-470.html

In your amanda.conf, you need to define:
tapedev "file://path/to/your/slots"

Rob


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeanna Geier
Sent: Tuesday, May 29, 2007 3:01 PM
To: amanda-users@amanda.org
Subject: newbie ? - tapeless operation -> amlabel error


Hi All!

I'm new to Amanda and am trying to configure it for
tapeless operation using the instructions in the following
link:
http://amanda.sourceforge.net/fom-serve/cache/191.html. I'm
down to the labeling in step #5 'Use amlabel to label the
tapes'; however, when I run the amlabel command, I get the
following error:
[EMAIL PROTECTED]:/usr/src/amanda-2.5.2/sbin$ amlabel
DailySet3 DailySet301 slot 1
amlabel: could not load slot "1": could not read result
from "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"

I'm running VERSION 2.5.2 on Linux.

My 'amanda.conf' file:

... Stuff cut ...

runtapes 1 # number of tapes to be used in a single run of
amdump
tpchanger "/usr/src/amanda/etc/amanda/DailySet3/chg.disk" #
the tape-changer glue script
#tapedev "/dev/nst0" # the no-rewind tape device to be used
rawtapedev "/dev/null" # the raw device to be used (ftape
only)

... Stuff cut ...

--
Rob Echlin
Software Development Environment Prime
Espial IPTV
Rechlin -at- espial.com
Phone: +1 613-230-4770 ext 1150
www.espial.com

 Espial Group Inc. Confidential 
Important Notice: This communication is intended to be received only by
the individual or entity to whom or to which it is addressed and may
contain information that is privileged, confidential and/or subject to
copyright. Any unauthorized use, copying, review or disclosure of this
communication is strictly prohibited. If you have received this
communication in error, please delete the message and notify the sender
by reply email. Thank you for your cooperation.
 

Re: newbie ? - tapeless operation -> amlabel error

[Jeanna Geier]

Hello- Thank you for the reply.

"Are you *sure* you want your vtapes in /usr/src/amanda ?"
No - I'm not sure of anything for sure, I'm just trying to
get this running! =)  But, have not been successful!

I started with that HOWTO
(http://www.amanda.org/docs/howto-filedriver.html), and was
told that for testing, they wanted it to write to the
harddisk vs. tapes, so I found the other link; how do I
know what to parameters to change exactly?

Thanks!
-jg



On Tue, 29 May 2007 21:09:24 +0200
 "Stefan G. Weichinger" <[EMAIL PROTECTED]> wrote:
> Jeanna Geier schrieb:
> > Hi All!
> > 
> > I'm new to Amanda and am trying to configure it for
> > tapeless operation using the instructions in the
> following
> > link:
> > http://amanda.sourceforge.net/fom-serve/cache/191.html.
> I'm
> > down to the labeling in step #5 'Use amlabel to label
> the
> > tapes'; however, when I run the amlabel command, I get
> the
> > following error:
> > [EMAIL PROTECTED]:/usr/src/amanda-2.5.2/sbin$ amlabel
> > DailySet3 DailySet301 slot 1
> > amlabel: could not load slot "1": could not read result
> > from "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
> 
> Are you *sure* you want your vtapes in /usr/src/amanda ?
> 
> Apart from that I recommend the official howto:
> 
> http://www.amanda.org/docs/howto-filedriver.html
> 
> Your changerfile is wrong ... at least ... you dropped a
> load of
> information here ...
> 
> -- 
> Stefan G. Weichinger
> amanda core team member
> mailto:   [EMAIL PROTECTED]
> pgp:  3C64175D
> -- 
> oops! linux consulting & implementation
> http://www.oops.co.at
> -- 



Jeanna Geier
System Administrator
Webteam, Inc.
[EMAIL PROTECTED]
http://www.webteam.net

ph: 608.788.8100
fx: 608.788.6613
tf: 866.788.0023

newbie ? - tapeless operation -> amlabel error

[Jeanna Geier]

Hi All!

I'm new to Amanda and am trying to configure it for
tapeless operation using the instructions in the following
link:
http://amanda.sourceforge.net/fom-serve/cache/191.html. I'm
down to the labeling in step #5 'Use amlabel to label the
tapes'; however, when I run the amlabel command, I get the
following error:
[EMAIL PROTECTED]:/usr/src/amanda-2.5.2/sbin$ amlabel
DailySet3 DailySet301 slot 1
amlabel: could not load slot "1": could not read result
from "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"

I'm running VERSION 2.5.2 on Linux.

My 'amanda.conf' file:

org "DailySet3" # your organization name for reports
mailto "amanda" # space separated list of operators at your
site
dumpuser "amanda" # the user to run dumps under

inparallel 4 # maximum dumpers that will run in parallel
(max 63)
# this maximum can be increased at compile-time,
# modifying MAX_DUMPERS in server-src/driverio.h
dumporder "sssS" # specify the priority order of each
dumper
# s -> smallest size
# S -> biggest size
# t -> smallest time
# T -> biggest time
# b -> smallest bandwitdh
# B -> biggest bandwitdh
# try "BTBTBTBTBTBT" if you are not holding
# disk constrained

taperalgo first # The algorithm used to choose which dump
image to send
# to the taper.
# Possible values:
# [first|firstfit|largest|largestfit|smallest|last]
# Default: first.
# first First in - first out.
# firstfit The first dump image that will fit
# on the current tape.
# largest The largest dump image.
# largestfit The largest dump image that will fit
# on the current tape.
# smallest The smallest dump image.
# last Last in - first out.

displayunit "k" # Possible values: "k|m|g|t"
# Default: k.
# The unit used to print many numbers.
# k=kilo, m=mega, g=giga, t=tera

netusage 90 mbps # maximum net bandwidth for Amanda, in KB
per sec

dumpcycle 7 # the number of days in the normal dump cycle
#runspercycle 7 # the number of amdump runs in dumpcycle
days
# (4 weeks * 5 amdump runs per week -- just weekdays)
tapecycle 7 tapes # the number of tapes in rotation
# 4 weeks (dumpcycle) times 5 tapes per week (just
# the weekdays) plus a few to handle errors that
# need amflush and so we do not overwrite the full
# backups performed at the beginning of the previous
# cycle

bumpsize 20 Mb # minimum savings (threshold) to bump level
1 -> 2
bumppercent 20 # minimum savings (threshold) to bump level
1 -> 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)

etimeout 600 # number of seconds per filesystem for
estimates.
dtimeout 1800 # number of idle seconds before a dump is
aborted.
ctimeout 30 # maximum number of seconds that amcheck waits
# for each client host

tapebufs 20 # A positive integer telling taper how many
# 32k buffers to allocate. The default is 20 (640k).

usetimestamps yes

runtapes 1 # number of tapes to be used in a single run of
amdump
tpchanger "/usr/src/amanda/etc/amanda/DailySet3/chg.disk" #
the tape-changer glue script
#tapedev "/dev/nst0" # the no-rewind tape device to be used
rawtapedev "/dev/null" # the raw device to be used (ftape
only)
#changerfile "/usr/src/amanda/etc/amanda/DailySet3/changer"
#changerfile
"/usr/src/amanda/etc/amanda/DailySet3/changer-status"
changerfile "/usr/src/amanda/etc/amanda/DailySet3/chg.disk"
#changerdev "/dev/sg3"

# Use with caution.
## label_new_tapes "DailySet1-%%%"

maxdumpsize -1 # Maximum number of bytes the planner will
schedule
# for a run (default: runtapes * tape_length).
tapetype HARD-DISK # what kind of tape it is (see tapetypes
below)
labelstr "^DailySet3[0-9][0-9]*$" # label constraint regex:
all tapes must match

amrecover_do_fsf yes # amrecover will call amrestore with
the
# -f flag for faster positioning of the tape.
amrecover_check_label yes # amrecover will call amrestore
with the
# -l flag to check the label.
amrecover_changer "/dev/null" # amrecover will use the
changer if you restore
# from this device.
# It could be a string like 'changer' and
# amrecover will use your changer if you
# set your tape with 'settape changer'

# Specify holding disks.
holdingdisk hd1 {
comment "main holding disk"
directory "/backup" # where the holding disk is
use -1000 Mb # how much space can we use on it
# a non-positive value means:
# use all space but that value
chunksize 1Gb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split images in chunks of size N
# The maximum value should be
# (MAX_FILE_SIZE - 1Mb)
# 0 same as INT_MAX bytes
}
#holdingdisk hd2 {
# directory "/dumps2/amanda"
# use 1000 Mb
# }
#holdingdisk hd3 {
# directory "/mnt/disk4"
# use 1000 Mb
# }


# If amanda cannot find a tape on which to stor

Re: amlabel problem

[Jeffrey Anderson]

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

[Joshua Baker-LePain]

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

[Franz-Heinrich Massmann]

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]
-

amlabel problem

[Natalia García Nebot]

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?

Re: amlabel: writing label: Device or resource busy

[Jon LaBadie]

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

[Franz-Heinrich Massmann]

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]
-

amlabel: writing label: Device or resource busy

[Sven Rudolph]

(This is on Debian GNU/Linux, kernel 2.6.16.20)

With amanda 2.5.0p2 I cannot label new tapes:

  backup:~$ /usr/sbin/amlabel WeeklySet1 Set1-4-12 slot 12
  changer: got exit: 0 str: 12 /dev/overland-sdlt600-tape
  labeling tape in slot 12 (/dev/overland-sdlt600-tape):
  rewinding, reading label, not an amanda tape (Read 0 bytes)
  rewinding, writing label Set1-4-12
  amlabel: writing label: Device or resource busy
  amlabel: writing label: Device or resource busy
  amlabel: pid 22206 finish time Wed Aug  2 10:54:28 2006

It didn't work with 2.5.0 either, but is OK with 2.4.5:

  backup:~$ /usr/sbin/amlabel WeeklySet1 Set1-4-12 slot 12
  labeling tape in slot 12 (/dev/overland-sdlt600-tape):
  rewinding, reading label, not an amanda tape
  rewinding, writing label Set1-4-12, checking label, done.

Relevant part of strace:

write(2, "changer: got exit: 0 str: 12 /de"..., 56changer: got exit: 0 str: 12 
/dev/overland-sdlt600-tape
) = 56
fstat64(1, {st_mode=S_IFREG|0644, st_size=88182, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7eee000
write(1, "labeling tape in slot 12 (/dev/o"..., 64labeling tape in slot 12 
(/dev/overland-sdlt600-tape):
rewinding) = 64
open("/dev/overland-sdlt600-tape", O_RDONLY|O_LARGEFILE) = 3
ioctl(3, MGSL_IOCGPARAMS or MTIOCTOP or SNDCTL_MIDI_MPUMODE, 0xbff05644) = 0
close(3)= 0
write(1, ", reading label", 15, reading label) = 15
open("/dev/overland-sdlt600-tape", O_RDONLY|O_LARGEFILE) = 3
mmap2(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0xb7c5
ioctl(3, MGSL_IOCGPARAMS or MTIOCTOP or SNDCTL_MIDI_MPUMODE, 0xbff044d4) = 0
read(3, "", 262144) = 0
munmap(0xb7c5, 266240)  = 0
close(3)= 0
write(1, ", not an amanda tape (Read 0 byt"..., 45, not an amanda tape (Read 0 
bytes)
rewinding) = 45
open("/dev/overland-sdlt600-tape", O_RDONLY|O_LARGEFILE) = 3
ioctl(3, MGSL_IOCGPARAMS or MTIOCTOP or SNDCTL_MIDI_MPUMODE, 0xbff05644) = 0
close(3)= 0
write(1, ", writing label Set1-4-12", 25, writing label Set1-4-12) = 25
open("/dev/overland-sdlt600-tape", O_RDWR|O_LARGEFILE) = 3
ioctl(3, MGSL_IOCGPARAMS or MTIOCTOP or SNDCTL_MIDI_MPUMODE, 0xbff044f4) = 0
write(3, "AMANDA: TAPESTART DATE X TAPE Se"..., 32768) = -1 EBUSY (Device or 
resource busy)
close(3)= 0
write(2, "amlabel: writing label: Device o"..., 48amlabel: writing label: 
Device or resource busy
) = 48
write(2, "amlabel: writing label: Device o"..., 48amlabel: writing label: 
Device or resource busy
) = 48
time([1154508266])  = 1154508266
getpid()= 21480
write(2, "amlabel: pid 21480 finish time W"..., 56amlabel: pid 21480 finish 
time Wed Aug  2 10:44:26 2006
) = 56
close(2)= 0
write(1, "\n", 1
)   = 1
munmap(0xb7eee000, 4096)= 0
exit_group(1)   = ?

Does anyone have an idea what could cause EBUSY or what changed in
this area in amanda 2.5.0 ?

Sven

RE: short write error on amlabel

[donald.ritchey]

Olivier:

Check to see if you can read/write the tape with other tools.

Do something like this for an old Amanda tape you will be relabeling:
mt rewind
dd if=/dev/ of=/tmp/foofile bs=32k
Check the contents of foofile and make sure it is valid.
dd if=/tmp/foofile of=/dev/

I suspect from the errors you are getting that one of two things are
present:

1.  You have a tape drive fault and amlabel cannot write to the drive
successfully.
2.  The tape is write protected (either explicitly or with a fault in
the write protect detector).

Good luck with the troubleshooting.

Don

Donald L. (Don) Ritchey
Information Technology
Exelon Corporation


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Olivier Nicole
Sent: Tuesday, June 27, 2006 1:57 AM
To: amanda-users@amanda.org
Subject: short write error on amlabel


Hi,

I suddenly find out that amlable is givingthe following error:

  amlabel: writing endmark: short write

whether I use a new tape or reuse an old tape. The label seems to be
correct, amcheck can check thattape, but it is not added to tapelist.

Any idea what is going on?

Best regards,

Olivier

$ amlabel normal CSIM-set-3-00
rewinding, reading label, not an amanda tape
rewinding, writing label CSIM-set-3-00
amlabel: writing endmark: short write
$

-
***
*
This e-mail and any of its attachments may contain Exelon
Corporation proprietary information, which is privileged,
confidential, or subject to copyright belonging to the Exelon
Corporation family of Companies.
This e-mail is intended solely for the use of the individual or
entity to which it is addressed.  If you are not the intended
recipient of this e-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation
to the contents of and attachments to this e-mail is strictly
prohibited and may be unlawful.  If you have received this e-mail
in error, please notify the sender immediately and permanently
delete the original and any copy of this e-mail and any printout.
Thank You.
***
*

short write error on amlabel

[Olivier Nicole]

Hi,

I suddenly find out that amlable is givingthe following error:

  amlabel: writing endmark: short write

whether I use a new tape or reuse an old tape. The label seems to be
correct, amcheck can check thattape, but it is not added to tapelist.

Any idea what is going on?

Best regards,

Olivier

$ amlabel normal CSIM-set-3-00
rewinding, reading label, not an amanda tape
rewinding, writing label CSIM-set-3-00
amlabel: writing endmark: short write
$

Re: Debugging amlabel?

[Jon LaBadie]

On Thu, May 04, 2006 at 07:10:39PM +0200, Arnd wrote:
> 
> Paul Bijnens wrote:
> >Normal scsi voodoo:  is the cable terminated?  Did you sacrifice
> >a chicken? ...
> >
> >Can you read/write to the tape when not using amanda tools, e.g.
> >simple:   dd if=somefile bs=32k of=/dev/st0
> 
> I must say that my first thought really was the chicken ;-).
> 
> Well, it was your second tip... While choosing the bloksize of 32k for 
> "dd" I was running into I/O errors on the tape drive so the next step is 
> to check the blocksize of that tapedrive:
> 
> $ mt -f /dev/st0 status
> SCSI 2 tape drive:
> File number=0, block number=1, partition=0.
> Tape block size 65536 bytes. Density code 0x42 (no translation).
> Soft error count since last status=0
> General status bits on (101):
>  ONLINE IM_REP_EN
> 
> While I couldn't find the option to specify the blocksize in the 
> tapetype I simply changed the blocksize of that tapedrive:
> 

Its called blocksize :)


-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Re: Debugging amlabel?

[Arnd]

Hi Paul

Paul Bijnens wrote:

Normal scsi voodoo:  is the cable terminated?  Did you sacrifice
a chicken? ...

Can you read/write to the tape when not using amanda tools, e.g.
simple:   dd if=somefile bs=32k of=/dev/st0


I must say that my first thought really was the chicken ;-).

Well, it was your second tip... While choosing the bloksize of 32k for 
"dd" I was running into I/O errors on the tape drive so the next step is 
to check the blocksize of that tapedrive:


$ mt -f /dev/st0 status
SCSI 2 tape drive:
File number=0, block number=1, partition=0.
Tape block size 65536 bytes. Density code 0x42 (no translation).
Soft error count since last status=0
General status bits on (101):
 ONLINE IM_REP_EN

While I couldn't find the option to specify the blocksize in the 
tapetype I simply changed the blocksize of that tapedrive:


$ mt -f /dev/nst0 setblk 32768

and (while still thinking about the chicken):

 $ amlabel tapeBackup tapeBackup-01
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label, reading label: Input/output error
rewinding, writing label tapeBackup-01, checking label, done.

Let's start dumping ;-)
Thank you!
Arnd

Re: Debugging amlabel?

[Paul Bijnens]

On 2006-05-04 17:13, Arnd wrote:

Hello.

Is there a possibility to log the activities of amlabel? I can load any 
tape with amtape but amlabel doesn't work. After loading the tape from 
the first slot amlabel tries to label it but this seems to hang:


$ amlabel tapeBackup tapeBackup-01
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label

This command now runs for more than 30 minutes without any debugging 
information. The drive seems to be in use so it might still be trying to 
rewind it?:


 $ mtx -f /dev/nst0 status
cannot open SCSI device '/dev/nst0' - Device or resource busy

Maybe the tapetype is misconfigured?:

define tapetype ULTRIUM2 {
comment "Ultrium 2 HP Tape"
length 20 mbytes
}

I was running strace but couldn't find the reason why it hangs.


This seems to be a kernel or hardware error.

Any details in the system logs?  or dmesg?

From the description is seems like simply open() or read() hangs.

Normal scsi voodoo:  is the cable terminated?  Did you sacrifice
a chicken? ...

Can you read/write to the tape when not using amanda tools, e.g.
simple:   dd if=somefile bs=32k of=/dev/st0


--
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  *
***

Debugging amlabel?

[Arnd]

Hello.

Is there a possibility to log the activities of amlabel? I can load any 
tape with amtape but amlabel doesn't work. After loading the tape from 
the first slot amlabel tries to label it but this seems to hang:


$ amlabel tapeBackup tapeBackup-01
labeling tape in slot 1 (/dev/nst0):
rewinding, reading label

This command now runs for more than 30 minutes without any debugging 
information. The drive seems to be in use so it might still be trying to 
rewind it?:


 $ mtx -f /dev/nst0 status
cannot open SCSI device '/dev/nst0' - Device or resource busy

Maybe the tapetype is misconfigured?:

define tapetype ULTRIUM2 {
comment "Ultrium 2 HP Tape"
length 20 mbytes
}

I was running strace but couldn't find the reason why it hangs.

Regards
Arnd

Re: Problem with amlabel

[Pavel Pragin]

Carl Holzhauer wrote:


That's part of the problem Paul, thanks for catching that.  When I make
that change however, I get an error:

-bash-3.00$ amlabel dailyset dailyset0 slot 0
changer: got exit: 2 str: please check your config and use a config file
for chg-scsi
amlabel: could not load slot "0": check your config and use a config
file for chg-scsi
amlabel: could not load slot "0": check your config and use a config
file for chg-scsi
amlabel: pid 593 finish time Thu Apr 27 14:05:06 2006
-bash-3.00$ 

Where do I specify a config file for chg-scsi? 

thanks 


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Bijnens
Sent: Thursday, April 27, 2006 3:36 AM
To: Carl Holzhauer
Cc: amanda-users@amanda.org
Subject: Re: Problem with amlabel

On 2006-04-27 08:46, Christoph Scheeder wrote:
 


Carl Holzhauer schrieb:
   

I'm sure I just have something written incorrectly, but here's the 
error I'm getting


-bash-3.00$ amlabel dailyset dailyset0 slot 0
changer: got exit: 1 str:  could not read result from 
"/usr/local/libexec/chg-scsi-solaris.conf"
 




This seems to me like you have the changer configuration file specified
in the place of the changer script file.

  tpchanger "the-glue-program-that-drives-the-changer"
  changerfile "a-parameter-used-by-that-program"

So you need to specify the glue program, which lives in libexec.

  tpchanger "chg-scsi"

When the program does not start with a '/', Amanda prepends the
libexecdir (and possibly a version suffix) to to locate the program.

That program uses a configuration file, which you specify with the
"changerfile" parameter:

  changerfile "chg-sci-solaris.conf"

When that file does not start with a '/', it is supposed to live in the
same directory as the amanda.conf file.



 


amanda.conf example:

tpchanger "chg-scsi"  # the tape-changer glue script
tapedev "0"   # the no-rewind tape device to be used
rawtapedev "/dev/null"# the raw device to be used (ftape only)
changerfile "chg-scsi.conf" #Make sure you specify the full path if this file is not in 
you "/etc/amanda/DailySet1"
changerdev "/dev/sg0"  # device configuration in changerfile.

RE: Problem with amlabel

[Carl Holzhauer]

That's part of the problem Paul, thanks for catching that.  When I make
that change however, I get an error:

-bash-3.00$ amlabel dailyset dailyset0 slot 0
changer: got exit: 2 str: please check your config and use a config file
for chg-scsi
amlabel: could not load slot "0": check your config and use a config
file for chg-scsi
amlabel: could not load slot "0": check your config and use a config
file for chg-scsi
amlabel: pid 593 finish time Thu Apr 27 14:05:06 2006
-bash-3.00$ 

Where do I specify a config file for chg-scsi? 

thanks 

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Bijnens
Sent: Thursday, April 27, 2006 3:36 AM
To: Carl Holzhauer
Cc: amanda-users@amanda.org
Subject: Re: Problem with amlabel

On 2006-04-27 08:46, Christoph Scheeder wrote:
> Carl Holzhauer schrieb:
>> I'm sure I just have something written incorrectly, but here's the 
>> error I'm getting
>>  
>> -bash-3.00$ amlabel dailyset dailyset0 slot 0
>> changer: got exit: 1 str:  could not read result from 
>> "/usr/local/libexec/chg-scsi-solaris.conf"


This seems to me like you have the changer configuration file specified
in the place of the changer script file.

   tpchanger "the-glue-program-that-drives-the-changer"
   changerfile "a-parameter-used-by-that-program"

So you need to specify the glue program, which lives in libexec.

   tpchanger "chg-scsi"

When the program does not start with a '/', Amanda prepends the
libexecdir (and possibly a version suffix) to to locate the program.

That program uses a configuration file, which you specify with the
"changerfile" parameter:

   changerfile "chg-sci-solaris.conf"

When that file does not start with a '/', it is supposed to live in the
same directory as the amanda.conf file.



-- 
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  *
***




__
Message transport security by GatewayDefender.com
3:49:32 AM ET - 4/27/2006


__
Message transport security by GatewayDefender.com
2:04:33 PM ET - 4/27/2006

Re: Problem with amlabel

[Paul Bijnens]

On 2006-04-27 08:46, Christoph Scheeder wrote:

Carl Holzhauer schrieb:

I'm sure I just have something written incorrectly, but here's the error
I'm getting
 
-bash-3.00$ amlabel dailyset dailyset0 slot 0

changer: got exit: 1 str:  could not read result from
"/usr/local/libexec/chg-scsi-solaris.conf"



This seems to me like you have the changer configuration file specified
in the place of the changer script file.

  tpchanger "the-glue-program-that-drives-the-changer"
  changerfile "a-parameter-used-by-that-program"

So you need to specify the glue program, which lives in libexec.

  tpchanger "chg-scsi"

When the program does not start with a '/', Amanda prepends the
libexecdir (and possibly a version suffix) to to locate the program.

That program uses a configuration file, which you specify with
the "changerfile" parameter:

  changerfile "chg-sci-solaris.conf"

When that file does not start with a '/', it is supposed to live
in the same directory as the amanda.conf file.



--
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: Problem with amlabel

[Christoph Scheeder]

Carl Holzhauer schrieb:

I'm sure I just have something written incorrectly, but here's the error
I'm getting
 
-bash-3.00$ amlabel dailyset dailyset0 slot 0

changer: got exit: 1 str:  could not read result from
"/usr/local/libexec/chg-scsi-solaris.conf"
amlabel: could not load slot "0": could not read result from
"/usr/local/libexec/chg-scsi-solaris.conf"
amlabel: could not load slot "0": could not read result from
"/usr/local/libexec/chg-scsi-solaris.conf"
amlabel: pid 1812 finish time Wed Apr 26 16:27:24 2006
-bash-3.00$ 
 
Output of that file:
 
-bash-3.00$ cat "/usr/local/libexec/chg-scsi-solaris.conf"

number_configs  1
eject   0   # Tapedrives need an eject command
sleep   15  # Seconds to wait until the tape gets ready
cleanmax10  # How many times could a cleaning tape get used
changerdev  /dev/0bn
#
# Next comes the data for drive 0
#
config  0
drivenum0
dev /dev/rmt/0bn# the device that is used for the
tapedrive 0 (BSD type, no rewind, no compression)
startuse0   # The slots associated with the drive 0
enduse  17  # 
statfile/usr/local/etc/amanda/dailyset/tape0-slot  # The file

where the actual slot is stored
cleancart   18  # the slot where the cleaningcartridge for drive
0 is located
cleanfile   /usr/local/etc/amanda/dailyset/tape0-clean # The file
where the cleanings are recorded
usagecount  /usr/local/etc/amanda/dailyset/totaltime
tapestatus  /usr/local/etc/amanda/dailyset/tape0-status
#labelfile  /usr/local/etc/amanda/dailyset/labelfile # Use this if
you have an barcode reader
-bash-3.00$ 
 
Amanada user has read/write access to /usr/local/libexec and to the

chg-scsi-solaris.conf file.
 
can anyone point me in the right direction?
 
Thanks




__
Message transport security by GatewayDefender.com
4:29:05 PM ET - 4/26/2006


Hi there,
i use chg-scsi since a few years on diffrent linux-servers and have 
found it has a problem with the comments in chg-scsi.conf.

Try to remove all comments from that file an retry  it, perhaps it fixes
all your problems.
Christoph

Re: Problem with amlabel

[Jon LaBadie]

On Wed, Apr 26, 2006 at 04:28:33PM -0400, Carl Holzhauer wrote:
> I'm sure I just have something written incorrectly, but here's the error
> I'm getting
>  
> -bash-3.00$ amlabel dailyset dailyset0 slot 0
> changer: got exit: 1 str:  could not read result from
> "/usr/local/libexec/chg-scsi-solaris.conf"
> amlabel: could not load slot "0": could not read result from
> "/usr/local/libexec/chg-scsi-solaris.conf"
> amlabel: could not load slot "0": could not read result from
> "/usr/local/libexec/chg-scsi-solaris.conf"
> amlabel: pid 1812 finish time Wed Apr 26 16:27:24 2006
> -bash-3.00$ 
>  
> Output of that file:
>  
> -bash-3.00$ cat "/usr/local/libexec/chg-scsi-solaris.conf"
> number_configs  1
> eject   0   # Tapedrives need an eject command
> sleep   15  # Seconds to wait until the tape gets ready
> cleanmax10  # How many times could a cleaning tape get used
> changerdev  /dev/0bn

Haven't used chg-scsi.  But, I doubt the above device is correct.
First, it is not in rmt.
Second, is your changer device really the same as your drive device?
Often they are different lun's or scsi id's.  Either would result
in a different rmt device number.  However to see lun's > 0 you
probably will have to edit /kernel/drv/st.conf (scsi tape)then do a
reconfigure reboot.  Another possibility is to look at sgen.conf
(scsi generic?general?) in the same directory.  If it recognizes
your changer mechanism you may have have a device /dev/changer and/or
/dev/scsi/changer/#

> #
> # Next comes the data for drive 0
> #
> config  0
> drivenum0
> dev /dev/rmt/0bn# the device that is used for the
> tapedrive 0 (BSD type, no rewind, no compression)

Certain about that "no compression"?  The zero tape device (without
an added l,m,h,c,u) is the default of one of the others (l,m,...).
It could be any or them, compression or not.

> startuse0   # The slots associated with the drive 0
> enduse  17  # 
> statfile/usr/local/etc/amanda/dailyset/tape0-slot  # The file
> where the actual slot is stored
> cleancart   18  # the slot where the cleaningcartridge for drive
> 0 is located
> cleanfile   /usr/local/etc/amanda/dailyset/tape0-clean # The file
> where the cleanings are recorded
> usagecount  /usr/local/etc/amanda/dailyset/totaltime
> tapestatus  /usr/local/etc/amanda/dailyset/tape0-status
> #labelfile  /usr/local/etc/amanda/dailyset/labelfile # Use this if
> you have an barcode reader
> -bash-3.00$ 
>  
> Amanada user has read/write access to /usr/local/libexec and to the
> chg-scsi-solaris.conf file.
>  
> can anyone point me in the right direction?
>  
> Thanks
> 
> 
> 
> __
> Message transport security by GatewayDefender.com
> 4:29:05 PM ET - 4/26/2006
>>> End of included message <<<

-- 
Jon H. LaBadie  [EMAIL PROTECTED]
 JG Computing
 4455 Province Line Road(609) 252-0159
 Princeton, NJ  08540-4322  (609) 683-7220 (fax)

Problem with amlabel

[Carl Holzhauer]

I'm sure I just 
have something written incorrectly, but here's the error I'm 
getting
 
-bash-3.00$ 
amlabel dailyset dailyset0 slot 0changer: got exit: 1 str:  
could not read result from 
"/usr/local/libexec/chg-scsi-solaris.conf"amlabel: could not load slot "0": 
could not read result from 
"/usr/local/libexec/chg-scsi-solaris.conf"amlabel: could not load slot "0": 
could not read result from 
"/usr/local/libexec/chg-scsi-solaris.conf"amlabel: pid 1812 finish time Wed 
Apr 26 16:27:24 2006-bash-3.00$ 
 
Output of that 
file:
 
-bash-3.00$ cat 
"/usr/local/libexec/chg-scsi-solaris.conf"number_configs  
1eject   
0   # Tapedrives need an eject 
commandsleep   
15  # Seconds to wait until the tape gets 
readycleanmax    
10  # How many times could a cleaning tape get 
usedchangerdev  /dev/0bn## Next comes 
the data for drive 
0#config  
0drivenum    
0dev 
/dev/rmt/0bn    # the device that is used for the tapedrive 0 
(BSD type, no rewind, no 
compression)startuse    
0   # The slots associated with the drive 
0enduse  
17  # 
statfile    
/usr/local/etc/amanda/dailyset/tape0-slot  # The file where the actual slot 
is storedcleancart   
18  # the slot where the cleaningcartridge for 
drive 0 is locatedcleanfile   
/usr/local/etc/amanda/dailyset/tape0-clean # The file where the cleanings are 
recordedusagecount  
/usr/local/etc/amanda/dailyset/totaltimetapestatus  
/usr/local/etc/amanda/dailyset/tape0-status#labelfile  
/usr/local/etc/amanda/dailyset/labelfile # Use this if you have an barcode 
reader-bash-3.00$ 
 
Amanada user has 
read/write access to /usr/local/libexec and to the chg-scsi-solaris.conf 
file.
 
can anyone point 
me in the right direction?
 
Thanks

 



Message transport security by 
GatewayDefender4:29:05 PM ET - 4/26/2006

Re: amlabel: command not found (was Re: port 35280 not secure)

[Gene Heskett]

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)

[Anne Wilson]

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