Re: amlabel problem
When reporting a problem, can you at least report which version you are
using.
We also need a way to reproduce the issue, the minum it hat case is the
amlabel command line argument and all setting related to the changer.
Bug get fixed a lot faster when enough information to reproduce the
issue is provided.
I committed the attached patch to fix the issue.
Jean-Louis
On 17/10/15 08:39 AM, Kamil Jońca wrote:
I want to add some new virtual tapes, but I got:
--8<---cut here---start->8---
Reading label...
Found an empty tape.
amlabel: Can't use an undefined value as a subroutine reference at
/usr/sbin/amlabel line 120.
--8<---cut here---end--->8---
lines from sbin/amlabel:
--8<---cut here---start->8---
117 if ($res) {
118 $res->release(finished_cb => sub {
119 # ignore error
120 $finished_cb->()
121 });
--8<---cut here---end--->8---
KJ
diff --git a/config/compile b/config/compile
old mode 100644
new mode 100755
diff --git a/config/config.guess b/config/config.guess
old mode 100644
new mode 100755
diff --git a/server-src/amlabel.pl b/server-src/amlabel.pl
index 307af07..b3c8aa4 100644
--- a/server-src/amlabel.pl
+++ b/server-src/amlabel.pl
@@ -255,7 +255,7 @@ sub main {
my ($err, $meta) = @_;
if (defined $meta && defined $opt_meta && $meta ne $opt_meta) {
- return failure();
+ return failure("Device meta '$meta' is not the same as the --meta argument '$opt_meta'", $finished_cb);
}
$meta = $opt_meta if !defined $meta;
($meta, my $merr) = $res->make_new_meta_label() if !defined $meta;
@@ -347,7 +347,7 @@ sub main {
if (defined $meta) {
if (defined($tle->{'meta'}) && $meta ne $tle->{'meta'} &&
!$opt_force) {
- return failure("Can't change meta-label with --force, old meta-label is '$tle->{'meta'}'");
+ return failure("Can't change meta-label with --force, old meta-label is '$tle->{'meta'}'", $finished_cb);
}
} else {
$meta = $tle->{'meta'};
@@ -357,7 +357,7 @@ sub main {
if (defined($tle->{'barcode'}) &&
$barcode ne $tle->{'barcode'} &&
!$opt_force) {
- return failure("Can't change barcode with --force, old barcode is '$tle->{'barcode'}'");
+ return failure("Can't change barcode with --force, old barcode is '$tle->{'barcode'}'", $finished_cb);
}
} else {
$barcode = $tle->{'barcode'};
Re: amlabel problem
Brian Cuttler schrieb: Hello Amanda users, I had the jukebox I use on one of my SGI/IRIX Amanda servers fail and we reverted to the attached standalone SDLT 220. I modified amanda.conf to use the different tape drive and to not use any changer config. I was able to label (one/day) a few tapes (and write them that evening), but I'm having difficulty with subsequent tapes. samar 8# /usr/local/sbin/amlabel -f samar SAMAR30 rewinding, reading label, reading label: Invalid argument rewinding, writing label SAMAR30 amlabel: writing label: Invalid argument So you use another tapetype. What does it look like? Any specific settings in there? Using some unusual blocksize or something? Also browse the log- and debugfiles for anything related. Stefan
Re: amlabel problem
Stefan,
I didn't realize the amlabel command wrote a log, I have it,
unfortunately not as informative as one might like in these
circumstances.
samar 5# more amlabel.20080229105753.debug
amlabel: debug 1 pid 873486 ruid 0 euid 0: start at Fri Feb 29 10:57:53 2008
amlabel: writing label: Invalid argument
amlabel: pid 873486 finish time Fri Feb 29 10:57:53 2008
The change from the jukebox to the standalone drive involved
these changes to amanda.conf.
samar 11# diff amanda.conf amanda.conf-20080221-jukebox
93,95c93,94
#runtapes 2 # number of tapes to be used in a single run of amdump
runtapes 1# number of tapes to be used in a single run of amdump
#tpchanger chg-zd-mtx # the tape-changer glue script
---
runtapes 2# number of tapes to be used in a single run of amdump
tpchanger chg-zd-mtx# the tape-changer glue script
97,98c96
#tapedev /dev/sdlt2 # the no-rewind tape device to be used
tapedev /dev/sdlt # the no-rewind tape device to be used
---
tapedev /dev/sdlt2 # the no-rewind tape device to be used
101,102c99,100
#changerfile /usr5/amanda/chg-zd-mtx
#changerdev /dev/scsi/sc7d1l0
---
changerfile /usr5/amanda/chg-zd-mtx
changerdev /dev/scsi/sc7d1l0
Apparently I didn't change the tape type, I probably should have
but I don't know that the tapes differ except for capacity as the
current drive is an SDLT 220.
samar 13# mt -f /dev/sdlt status
Controller: SCSI
Device: QUANTUM: SuperDLT1 3737?7
Status: 0x20262
Drive type: unknown
Media : READY, writable, at BOT
samar 14# mt -f /dev/sdlt2 status
Controller: SCSI
Device: QUANTUM: SDLT320 3838?8
Status: 0xa00
Drive type: unknown
Media : Not READY
From amanda.conf, the tapetype definition. Nothing terribly odd
here I don't think.
define tapetype SDLT {
comment QUAMTUM SDLT320
length 16 mbytes
filemark 100 kbytes # don't know a better value
speed 100 kbytes# dito
}
And again, I was able to label and write the first several tapes
without addititional changes to the config.
I was also unable to dump or tar to the drive, I wonder if we
don't have a general failure.
I will ask a user to see if they can access the drive properly
with whatever tapes they normally use in this drive (it was used
for user data archiving before I commendeered it.
thanks,
Brian
On Fri, Feb 29, 2008 at 09:57:07AM +0100, Stefan G. Weichinger wrote:
Brian Cuttler schrieb:
Hello Amanda users,
I had the jukebox I use on one of my SGI/IRIX Amanda servers fail
and we reverted to the attached standalone SDLT 220.
I modified amanda.conf to use the different tape drive and to
not use any changer config.
I was able to label (one/day) a few tapes (and write them that evening),
but I'm having difficulty with subsequent tapes.
samar 8# /usr/local/sbin/amlabel -f samar SAMAR30
rewinding, reading label, reading label: Invalid argument
rewinding, writing label SAMAR30
amlabel: writing label: Invalid argument
So you use another tapetype.
What does it look like? Any specific settings in there?
Using some unusual blocksize or something?
Also browse the log- and debugfiles for anything related.
Stefan
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure. It
is intended only for the addressee. If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments. Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.
Re: amlabel problem - reading chunks from holding area
Stefan, et al,
We have decided that the standalone tape drive has failed, it
will not read nor write known good tapes.
We are thinking of allocating a large NFS partition (I know, bad
mojo and performace but apparently/supposedly its going to be temporary)
and just letting the files live in the amanda work area.
The question then becomes one of file restores.
How do you restore data from holding area chunks ?
Do I just cat them together (is there an easy way to get
them in order ?), if there a good method of reading them ?
Or can I create readable files that aren't chunked ?
I know that the right way is to build a new version of amanda,
using vtapes, and install it on the server that has the large
partition - but that machine too is scheduled to move offsite.
Big investment in time for a solution that is about to walk out
of the door, but I have to at least try and get backups done for
the machines our site will retain.
thanks,
Brian
On Fri, Feb 29, 2008 at 11:13:06AM -0500, Brian Cuttler wrote:
Stefan,
I didn't realize the amlabel command wrote a log, I have it,
unfortunately not as informative as one might like in these
circumstances.
samar 5# more amlabel.20080229105753.debug
amlabel: debug 1 pid 873486 ruid 0 euid 0: start at Fri Feb 29 10:57:53 2008
amlabel: writing label: Invalid argument
amlabel: pid 873486 finish time Fri Feb 29 10:57:53 2008
The change from the jukebox to the standalone drive involved
these changes to amanda.conf.
samar 11# diff amanda.conf amanda.conf-20080221-jukebox
93,95c93,94
#runtapes 2 # number of tapes to be used in a single run of amdump
runtapes 1# number of tapes to be used in a single run of amdump
#tpchanger chg-zd-mtx # the tape-changer glue script
---
runtapes 2# number of tapes to be used in a single run of amdump
tpchanger chg-zd-mtx# the tape-changer glue script
97,98c96
#tapedev /dev/sdlt2 # the no-rewind tape device to be used
tapedev /dev/sdlt # the no-rewind tape device to be used
---
tapedev /dev/sdlt2 # the no-rewind tape device to be used
101,102c99,100
#changerfile /usr5/amanda/chg-zd-mtx
#changerdev /dev/scsi/sc7d1l0
---
changerfile /usr5/amanda/chg-zd-mtx
changerdev /dev/scsi/sc7d1l0
Apparently I didn't change the tape type, I probably should have
but I don't know that the tapes differ except for capacity as the
current drive is an SDLT 220.
samar 13# mt -f /dev/sdlt status
Controller: SCSI
Device: QUANTUM: SuperDLT1 3737?7
Status: 0x20262
Drive type: unknown
Media : READY, writable, at BOT
samar 14# mt -f /dev/sdlt2 status
Controller: SCSI
Device: QUANTUM: SDLT320 3838?8
Status: 0xa00
Drive type: unknown
Media : Not READY
From amanda.conf, the tapetype definition. Nothing terribly odd
here I don't think.
define tapetype SDLT {
comment QUAMTUM SDLT320
length 16 mbytes
filemark 100 kbytes # don't know a better value
speed 100 kbytes# dito
}
And again, I was able to label and write the first several tapes
without addititional changes to the config.
I was also unable to dump or tar to the drive, I wonder if we
don't have a general failure.
I will ask a user to see if they can access the drive properly
with whatever tapes they normally use in this drive (it was used
for user data archiving before I commendeered it.
thanks,
Brian
On Fri, Feb 29, 2008 at 09:57:07AM +0100, Stefan G. Weichinger wrote:
Brian Cuttler schrieb:
Hello Amanda users,
I had the jukebox I use on one of my SGI/IRIX Amanda servers fail
and we reverted to the attached standalone SDLT 220.
I modified amanda.conf to use the different tape drive and to
not use any changer config.
I was able to label (one/day) a few tapes (and write them that evening),
but I'm having difficulty with subsequent tapes.
samar 8# /usr/local/sbin/amlabel -f samar SAMAR30
rewinding, reading label, reading label: Invalid argument
rewinding, writing label SAMAR30
amlabel: writing label: Invalid argument
So you use another tapetype.
What does it look like? Any specific settings in there?
Using some unusual blocksize or something?
Also browse the log- and debugfiles for anything related.
Stefan
---
Brian R Cuttler [EMAIL PROTECTED]
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 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
Re: amlabel problem - reading chunks from holding area
Brian Cuttler wrote: Stefan, et al, We have decided that the standalone tape drive has failed, it will not read nor write known good tapes. We are thinking of allocating a large NFS partition (I know, bad mojo and performace but apparently/supposedly its going to be temporary) and just letting the files live in the amanda work area. The question then becomes one of file restores. How do you restore data from holding area chunks ? Do I just cat them together (is there an easy way to get them in order ?), if there a good method of reading them ? Or can I create readable files that aren't chunked ? Amanda will restore files from dle's that are still on the holding disk just as easily as from tapes, only faster. Same procedure. Amanda knows where they are and that they haven't been flushed to tape yet. I've done it before just to see. --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst [EMAIL PROTECTED] --- Erdös 4
Re: amlabel problem - reading chunks from holding area
Chris, I _so_ love amanda! thank you! On Fri, Feb 29, 2008 at 02:43:50PM -0500, Chris Hoogendyk wrote: Brian Cuttler wrote: Stefan, et al, We have decided that the standalone tape drive has failed, it will not read nor write known good tapes. We are thinking of allocating a large NFS partition (I know, bad mojo and performace but apparently/supposedly its going to be temporary) and just letting the files live in the amanda work area. The question then becomes one of file restores. How do you restore data from holding area chunks ? Do I just cat them together (is there an easy way to get them in order ?), if there a good method of reading them ? Or can I create readable files that aren't chunked ? Amanda will restore files from dle's that are still on the holding disk just as easily as from tapes, only faster. Same procedure. Amanda knows where they are and that they haven't been flushed to tape yet. I've done it before just to see. --- Chris Hoogendyk - O__ Systems Administrator c/ /'_ --- Biology Geology Departments (*) \(*) -- 140 Morrill Science Center ~~ - University of Massachusetts, Amherst [EMAIL PROTECTED] --- Erd?s 4 --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: amlabel problem - reading chunks from holding area
Brian Cuttler schrieb: Chris, I _so_ love amanda! Nice to hear that ;) Stefan
Re: amlabel problem
Natalia García Nebot wrote: Hi! I have installed amanda on my server host. The server is conected to a tape device. I have created a configuration named DiariaPrueba. I have configured all parameters in amanda.conf and I want to label only one tape to make tests before. In my amanda.conf I have configures de parameter labelstr to labelstr ^DiariaPruebaTape[0-9][0-9]*$ When I try to label my first tape amlabe says me: amlabel: could not load tapelist /etc/amanda/DiariaPrueba/tapelist So i tried this command: su amanda -c amlabel -f DiariaPrueba DiariaPrueba01 And amlabel says me: amlabel: label DiariaPrueba01 doesn't match labelstr ^DiariaPruebaTape[0-9][0-9]*$ What's wrong? Why can't I label a tape? Natalia, Your labelstr contains ..Tape.. while the amlabel command does not. You should make it matching. Franz - Franz-Heinrich Massmann GeoForschungsZentrum Potsdam (GFZ) Department 1: Geodesy and Remote Sensing, Section 1.2 c/o DLR Oberpfaffenhofen 82230 Wessling, Germany Tel./Fax: (+49) 8153-28-1206/1735 email: [EMAIL PROTECTED] -
Re: amlabel problem
On Thu, 17 Aug 2006 at 12:15pm, Natalia García Nebot wrote Hi! I have installed amanda on my server host. The server is conected to a tape device. I have created a configuration named DiariaPrueba. I have configured all parameters in amanda.conf and I want to label only one tape to make tests before. In my amanda.conf I have configures de parameter labelstr to labelstr ^DiariaPruebaTape[0-9][0-9]*$ When I try to label my first tape amlabe says me: amlabel: could not load tapelist /etc/amanda/DiariaPrueba/tapelist su amanda -c touch /etc/amanda/DiariaPrueba/tapelist -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amlabel problem
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.
Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO I am installing amanda for the first time and have problems labeling tapes for EPO it. I get the error message: EPO amlabel: could not load tapelist /etc/amanda/normal/tapelist Do you really want to keep your config-files in /etc/amanda? The default points to /usr/local/etc/amanda, for example. But this is not your problem, I assume. EPO This seems strange since it is the first tape I try to label and therefore EPO there is no tapelist file and there should not be one. In fact the EPO documentation says that it will be generated by amlabel and it should not be EPO modified by the user/administrator. The command I issue from the amanda user is: EPO amlabel /usr/sbin/amlabel normal normal00 EPO and it doesn't help to use the force flag. What am I doing wrong? Nothing. Just try a touch /etc/amanda/normal/tapelist and amlabel again. -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO The command I issue from the amanda user is: EPO amlabel /usr/sbin/amlabel normal normal00 EPO and it doesn't help to use the force flag. What am I doing wrong? Oops, I shot too fast. The syntax is /usr/sbin/amlabel normal normal00 You had 2 times amlabel -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
** Reply to message from Stefan G. Weichinger [EMAIL PROTECTED] on Tue, 17 Feb 2004 11:55:19 +0100 Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO The command I issue from the amanda user is: EPO amlabel /usr/sbin/amlabel normal normal00 EPO and it doesn't help to use the force flag. What am I doing wrong? Oops, I shot too fast. The syntax is /usr/sbin/amlabel normal normal00 You had 2 times amlabel Thanks Stefan, but it was a typo :) I did use the correct syntax. Regards, Erik P. Olsen
Re: amlabel problem.
** Reply to message from Stefan G. Weichinger [EMAIL PROTECTED] on Tue, 17 Feb 2004 11:54:09 +0100 Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO I am installing amanda for the first time and have problems labeling tapes for EPO it. I get the error message: EPO amlabel: could not load tapelist /etc/amanda/normal/tapelist Do you really want to keep your config-files in /etc/amanda? The default points to /usr/local/etc/amanda, for example. Anything wrong in that? That's where the sample config is located. Of course I can easily change it if it makes any difference. Regards, Erik P. Olsen
Re: amlabel problem.
** Reply to message from Stefan G. Weichinger [EMAIL PROTECTED] on Tue, 17 Feb 2004 11:54:09 +0100 Hi, Erik, on Dienstag, 17. Februar 2004 at 11:21 you wrote to amanda-users: EPO I am installing amanda for the first time and have problems labeling tapes for EPO it. I get the error message: EPO amlabel: could not load tapelist /etc/amanda/normal/tapelist [snip] EPO modified by the user/administrator. The command I issue from the amanda user is: EPO amlabel /usr/sbin/amlabel normal normal00 EPO and it doesn't help to use the force flag. What am I doing wrong? Nothing. Just try a touch /etc/amanda/normal/tapelist and amlabel again. Thanks, that did it. I now have labels on my tapes and may move on to the next problem. Regards, Erik P. Olsen
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 12:06 you wrote to amanda-users: Do you really want to keep your config-files in /etc/amanda? The default points to /usr/local/etc/amanda, for example. EPO Anything wrong in that? That's where the sample config is located. Of course I EPO can easily change it if it makes any difference. I don't know from which sources you compiled on what OS, but for me the default setting for AMANDA-2.4.4p2 (and earlier versions, too) is /usr/local/etc/amanda (it's Linux here). It's not WRONG to put configs in /etc, but it ain't the place they should go when you read the FHS (Filesystem Hierarchy Standard). From FHS: The /etc directory contains configuration unique to the system and is required for boot time. You see? Just configure your AMANDA-sources with --with-configdir=/usr/local/etc/amanda/ put your configs in there and feel the satisfaction of meeting the standard ;) -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
** Reply to message from Stefan G. Weichinger [EMAIL PROTECTED] on Tue, 17 Feb 2004 14:05:11 +0100 Hi, Erik, on Dienstag, 17. Februar 2004 at 12:06 you wrote to amanda-users: Do you really want to keep your config-files in /etc/amanda? The default points to /usr/local/etc/amanda, for example. EPO Anything wrong in that? That's where the sample config is located. Of course I EPO can easily change it if it makes any difference. [snip] From FHS: The /etc directory contains configuration unique to the system and is required for boot time. You see? Just configure your AMANDA-sources with --with-configdir=/usr/local/etc/amanda/ put your configs in there and feel the satisfaction of meeting the standard ;) I realize I have a lot to learn. I am new to Linux and before I can move my production to Linux I need a reliable backup system. I am all for standards, so I'll see to that my system complies to it - as long as I know about it :) Regards, Erik P. Olsen
Re: amlabel problem.
Hi, Erik, on Dienstag, 17. Februar 2004 at 14:19 you wrote to amanda-users: EPO I realize I have a lot to learn. I am new to Linux and before I can move my EPO production to Linux I need a reliable backup system. Very reasonable ;) EPO I am all for standards, so I'll see to that my system complies to EPO it - as long as I know about it :) Don't fear the steps you have to take. I assume you try to install and setup the most recent AMANDA-release 2.4.4p2. This should take most of the standard-issues off your shoulders. Here parts of my config-string, maybe it helps you: ./configure --with-user=amanda --with-group=disk --with-owner=amanda --with-tape-device=/dev/nst0 --prefix=/usr/local --with-debugging=/tmp/amanda/ --with-tape-server=YOUR-AMANDA-SERVER --with-amandahosts --with-config=daily --with-configdir=/usr/local/etc/amanda/ With this you get a pretty standard-directories-Linux-setup. Create directories if you need to. Edit parameters like --with-user to meet your needs ... -- best regards, Stefan Stefan G. Weichinger mailto:[EMAIL PROTECTED]
Re: amlabel problem.
** Reply to message from Stefan G. Weichinger [EMAIL PROTECTED] on Tue, 17 Feb 2004 14:29:51 +0100 Don't fear the steps you have to take. I assume you try to install and setup the most recent AMANDA-release 2.4.4p2. This should take most of the standard-issues off your shoulders. Here parts of my config-string, maybe it helps you: ./configure --with-user=amanda --with-group=disk --with-owner=amanda --with-tape-device=/dev/nst0 --prefix=/usr/local --with-debugging=/tmp/amanda/ --with-tape-server=YOUR-AMANDA-SERVER --with-amandahosts --with-config=daily --with-configdir=/usr/local/etc/amanda/ With this you get a pretty standard-directories-Linux-setup. Create directories if you need to. Edit parameters like --with-user to meet your needs ... Thanks, you have been most helpful. Regards, Erik P. Olsen
RE: amlabel problem
Figured it out... Once the drive recognises the tape it takes another 4 to 5 seconds before it's actually ready to do anything with it. -Original Message- From: John R. Jackson [mailto:[EMAIL PROTECTED]] Sent: March 14, 2002 11:21 PM To: Stott, Trevor Cc: '[EMAIL PROTECTED]' Subject: Re: amlabel problem This is what I'm getting when I try to do an amlabel to a new tape. Is this an amlabel problem or a tape drive problem? What version of Amanda? What OS? rewinding, reading label, reading label: Value too large for defined data type I *think* what this says is that amlabel was built for 32 bit file systems but the kernel (or libc?) is using 64 bit structures (but that's kind of a wild guess). Did you build Amanda yourself or use some evil, you get what you deserve, pre-packaged thing :-)? Trevor. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amlabel problem
This is what I'm getting when I try to do an amlabel to a new tape. Is this an amlabel problem or a tape drive problem? What version of Amanda? What OS? rewinding, reading label, reading label: Value too large for defined data type I *think* what this says is that amlabel was built for 32 bit file systems but the kernel (or libc?) is using 64 bit structures (but that's kind of a wild guess). Did you build Amanda yourself or use some evil, you get what you deserve, pre-packaged thing :-)? Trevor. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amlabel problem
Dave, Amanda is installed and configured on SUN Ultra I, Solaris 8. I don't have a tape drive physically connected to this machine, I am accessing a tape device on another SUN box. Run amlabel on the machine with the tape drive... You anyway need physical access to that machine, if only to load the tape, so you could even run the command from that machine too. I don't know if there is a way to do remote amlabel (well something else that rsh other.machine.com amlabel...) but I wouldn't see much use for it, except if you have a tape robot that can handle 200 cartridges (and in that case you have big $$ and would go by something else than Amanda I beleive). Olivier
