Re: [Amanda-users] LTO drives
On Tuesday 17 February 2009, Archer wrote: >Hello Guys, > >Can you give a link where to find RHEL 5 driver for Tandberg LTO 3 SCSI > Drive? Its a scsi tape drive, albeit a very fast one I hear. If you have the driver for your scsi card, then mtx and amanda is probably all you need. What does dmesg say out it? >I've been going around the internet but cant find anything. I appreciate if > you can direct me where to get it. Thanks. > >+-- > >|This was sent by 650h...@gmail.com via Backup Central. >|Forward SPAM to ab...@backupcentral.com. > >+-- -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Being schizophrenic is better than living alone.
Re: [Amanda-users] LTO drives
On Tue, Feb 17, 2009 at 11:16 PM, Archer wrote: > So you mean to say, if I do cat /proc/scsi/scsi, I should be able to see the > LTO 3 HH SCSI drive? I will try it out. Yes -- you would be able to see it even if you didn't have the 'st' driver loaded, in fact. If you can't see it, check your SCSI. Dustin -- Storage Software Engineer http://www.zmanda.com
Re: changer problems with 2.6.1
On Tue, Feb 17, 2009 at 11:06 PM, stan wrote: > When we upgraded from 2.5.1p2 to 2.5.2p1, we had to copy the chg-multi script > from the 2.5.1p1 release into the new tree, as the newer script did not > work correctly. Interesting -- did you submit patches? > 2.5.1p2 chg-multi does not work with 2.6.1. We have observed a couple of > things. First it seems that the tape handler that we were using, ammt from > the earlier amanda release is depricated. Since this mahcine is a Linux > machine we are back to the bad old days of trying to figure out wheter to use > mt-st or > gnu-mt, and I honestly cannot remember which one of those used to work. I'm curious - what do you need mt for? > In addition, we seem to be having problems with some syntax in chg-multi. > There are lines that look like this: > > echo `_ '$var'` >> $logfile > > I (nor my sh interperter) understand these. Looks to me like we are trying > to execute something called + which does not exist. It's a rather ill-advised attempt at internationalization. It's not pretty, especially in shell. > So since we are no longer going to be able to use ammt, what commands can > we expect mt to be involed with & what are the expected returns. Cause both > versions of the Linux mt commands (gnu-mt & mt-st) available for Ubuntu > return something different for an, mt -f /dev/nst0 status than ammt -f > /dev/nst0 status (none of the three match results). Amanda does not use mt at all at this point. I do notice that chg-multi still begins with: 51 if ! error=try_find_mt; then 52 echo $error 53 exit 2 54 fi but the result ($MT) is never used. I'd rip that out if I weren't about to delete the whole file :) > We got past the syntax > problem after getting rid of all the '_ ' in chg-multi & then amcheck which > calls the changer script fails to be able to find a valid slot. We suspect > that this is because chg-multi expects different behavior from mt than > it used to get from ammt. We tried forcing the existing, working 2.5.2p1, > that normally uses chg-multi from 2.5.1p2 and ammt to not find ammt & so > use the system mt. It reproduces the same error just described (confirmed > suspicion that Ubuntu gnu-mt & mt-st are incompatible with the changer > code) OK, a few pieces of Amanda history may be relevant to your investigations here. First, Amanda no longer assumes it is using a tape drive (that is, something which 'mt' might be able to operate). This is a part of the Device API which was introduced in 2.6.0. The only point at which changer scripts need to interact with a device is to determine whether it's ready or not -- in chg-zd-mtx and chg-manual. For this, these scripts now use amdevcheck. This has brought its own set of issues, but is fully functional and does not involve 'mt' in any way. Second, there are a number of other changes to the changer API in 2.6.1 -- see amanda-changers(7) and http://wiki.zmanda.com/index.php/Changer_API for a taste. Among lots of other interesting action, we're deprecating and removing all of the old shell scripts. At the moment, the new Changer API is *always* used, via a C-to-perl (and old-to-new) wrapper script (changer-src/chg-glue.pl[1]) and a perl-to-shell (and new-to-old) wrapper script (perl/Amanda/Changer/compat.pm). There's room for problems at several points along this chain. I'm busily at work rewriting changers into the new API, and rewriting the Amanda taper in Perl so that it can utilize the new API directly. You can see the new Amanda::Changer::rait at http://github.com/djmitche/amanda/tree/chg-rait-pl/perl/Amanda/Changer/rait.pm (and, if you're willing to build Amanda from source, you may be able to use this to fix your chg-multi problems). I woul suggest looking into the source of chg-multi to see where it puts its debugging information, and potentially adding more debugging echo's as necessary to see what it's doing. Also look at the taper debug log to see what commands it's sending to the changer. You may be able to run simpler operations using 'amtape', rather than running an entire amdump just to replicate the failure. Good luck, happy hunting, and, if you've got some Perl-fu, please consider coding up a new-style Amanda::Changer::multi! Dustin [1] You can find the source at http://github.com/nikolasco/amanda/tree/ -- Storage Software Engineer http://www.zmanda.com
[Amanda-users] LTO drives
So you mean to say, if I do cat /proc/scsi/scsi, I should be able to see the LTO 3 HH SCSI drive? I will try it out. +-- |This was sent by 650h...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
changer problems with 2.6.1
We are trying to upgrade all of our machines to 2.6.1. Presently we are struggling with tape changer problems on the server, an Ubuntu 8.04 machine. A bit of history here. We have a somewaht different arrangement. We have a RAIT, one side of which consists of 25 vtapes, the other side of which consists of a single LTO drive, not a changer, just a plain single tape drive, not a changer. We have had this working for several years now. When we upgraded from 2.5.1p2 to 2.5.2p1, we had to copy the chg-multi script from the 2.5.1p1 release into the new tree, as the newer script did not work correctly. 2.5.1p2 chg-multi does not work with 2.6.1. We have observed a couple of things. First it seems that the tape handler that we were using, ammt from the earlier amanda release is depricated. Since this mahcine is a Linux machine we are back to the bad old days of trying to figure out wheter to use mt-st or gnu-mt, and I honestly cannot remember which one of those used to work. In addition, we seem to be having problems with some syntax in chg-multi. There are lines that look like this: echo `_ '$var'` >> $logfile I (nor my sh interperter) understand these. Looks to me like we are trying to execute something called + which does not exist. So since we are no longer going to be able to use ammt, what commands can we expect mt to be involed with & what are the expected returns. Cause both versions of the Linux mt commands (gnu-mt & mt-st) available for Ubuntu return something different for an, mt -f /dev/nst0 status than ammt -f /dev/nst0 status (none of the three match results). We got past the syntax problem after getting rid of all the '_ ' in chg-multi & then amcheck which calls the changer script fails to be able to find a valid slot. We suspect that this is because chg-multi expects different behavior from mt than it used to get from ammt. We tried forcing the existing, working 2.5.2p1, that normally uses chg-multi from 2.5.1p2 and ammt to not find ammt & so use the system mt. It reproduces the same error just described (confirmed suspicion that Ubuntu gnu-mt & mt-st are incompatible with the changer code) -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs.
Re: [Amanda-users] LTO drives
On Tue, Feb 17, 2009 at 9:25 PM, Archer wrote: > Hello Guys, > > Can you give a link where to find RHEL 5 driver for Tandberg LTO 3 SCSI Drive? > > I've been going around the internet but cant find anything. I appreciate if > you can direct me where to get it. Thanks. Basically all tape drives use the 'st' driver in the Linux kernel. There is no special driver for LTO3. Dustin -- Storage Software Engineer http://www.zmanda.com
[Amanda-users] LTO drives
Hello Guys, Can you give a link where to find RHEL 5 driver for Tandberg LTO 3 SCSI Drive? I've been going around the internet but cant find anything. I appreciate if you can direct me where to get it. Thanks. +-- |This was sent by 650h...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
[Amanda-users] Restoring amanda tapes without amanda
I did use the name of my virtual tape its a file on directory, it works, get back all from my backup without using amanda restore command, becouse did not have index # dd if=1.desktop.__tijuanaserver_www.0 bs=32k skip=1 | tar -zxvf - thanks for your post it help me to get this done. +-- |This was sent by amest...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
2.5.2p1 failing
Recently my amanda server has begun failing during amdump without any apparent reason. I was using straight debian etch and amanda packages, since the problem appeared, I build from source and I'm still getting the same thing. Amcheck runs fine, amdump will start normally, the clients start sending in the estimates, and about 3/4's of the time, the server processes just die. The end of the amdump log file just has estimate info at the end, no errors. Any suggestions on where to look would be greatly appreciated. -- George Kelbley System Support Group Computer Science Department University of New Mexico 505-277-6502Fax: 505-277-6927
Re: 2.6.2alpha-20090216 busted by typu (non-repeatable)
On Tuesday 17 February 2009, Dustin J. Mitchell wrote:
>On Tue, Feb 17, 2009 at 12:18 AM, Gene Heskett
>wrote:
>> restore.c: In function 'restore':
>> restore.c:989: error: stray '`' in program
>
>Weird - the last time that file was changed was on the 10th, and it
>wasn't anywhere near that line. I don't see a ` character anywhere in
>the file. Can you send the lines around line 989 in your version of
>that file?
>
>Dustin
972-1008
if (need_compress) {
/*
* Insert a compress pipe
*/
switch(myout->comp_enc_pid = fork()) {
case -1:
error(_("could not fork for %s: %s"), COMPRESS_PATH,
strerror(errno));
/*NOTREACHED*/
default:
aclose(pipes[stage].pipe[0]);
aclose(pipes[stage+1].pipe[1]);
stage++;
break;
case 0:
if(dup2(pipes[stage].pipe[0], 0) == -1) {
error(_("error compress stdin [dup2 %d %d: %s]"), stage,
pipes[stage].pipe[0], strerror(errno));
/*NOTREACHED*/
}
if(dup2(pipes[stage+1].pipe[1], 1) == -1) {
989error(_("error compress stdout [dup2 %d %d: %s]"), stage + 1,
pipes[stage+1].pipe[1], strerror(errno));
/*NOTREACHED*/
}
if (*flags->comp_type == '\0') {
flags->comp_type = NULL;
}
safe_fd(-1, 0);
(void) execlp(COMPRESS_PATH, COMPRESS_PATH, flags->comp_type, (char
*)0);
error(_("could not exec %s: %s"), COMPRESS_PATH, strerror(errno));
/*NOTREACHED*/
}
} else if(need_uncompress) {
And obviously I don't see it either, unless its hidden by the %stuffs. In
vim, a "/`"enter says not found. I'll try making it again. FWIW, I'm also
using ccache.
And this time, no error. /me, goes off scratching head, wondering where else
such an error might creep in silently.
Sorry for the noise/false alarm.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
As long as we're going to reinvent the wheel again, we might as well try making
it round this time.
- Mike Dennison
