Re: A solution for taper and dumps larger than a single tape?
Bernhard R. Erdmann <[EMAIL PROTECTED]> wrote: > How do you know the exact EOT when using hardware compression? With DDS tape drives, you will get a CHECK CONDITION with all data successfully written a bit before the final EOT (where you will get a CHECK CONDITION, VOLUME OVERFLOW, where there will be some unwritten data -- that the drive WILL report). Assuming a proper drive, OS and mtio interface, you can safely write until actual EOT, look at the residual bytes or blocks, and safely determine how many bytes where written. Alternatively, you write only till the first early warning, and even if the tape drive/OS is in buffered mode and doesn't report correctly residual bytes, you have about 50-100 MByte of data till the actual EOT. That's the theory. However, I fully agree that the above is the ideal case: there are so many buggy OSes out there, and also many faulty hardware. That's why it could be an option. If that option isn't enabled, a way to do it would be to split backups on the tape at the filemark level (a filemark flushes the drive buffers as per SCSI specification). As soon as EOT occurs, discard the last written file as incomplete/uncertain, and rewrite it on the next tape. This is exactly what Amanda does, except that Amanda does it on a backup file level, which might well be e.g. 1 GB. Assuming those backups could be cut in chunk of say, 100 MB, there would be less wasted space -- at the cost of more complicated recovery.
Re: An idea for different size tapes
from the quill of "Bernhard R. Erdmann" <[EMAIL PROTECTED]> on scroll <[EMAIL PROTECTED]> > > That's not the way Amanda runs. She tries to fill each tape to the > same > level. Would doing a level zero backup everynight not achieve that? This is really only a sidebar issue now anyway. :-) > Split it up using tar or backup it in a different way. Sorry, I was not clear. I was not asking how to solve the "filesystem bigger than medium" issue. I know about splitting filesystems with tar/exclude. I was offering an idea for an alternative. There is a problem with using tar to try to split a large filesystem. It depends on being able to pinpoint a single point in the filesystem to isolate a decent portion of that filesystem. If your filesystem is 8GB in 80 equal sized top level subdirectories you cannot do this. b. -- Brian J. Murrell
Re: A solution for taper and dumps larger than a single tape?
from the quill of "Bernhard R. Erdmann" <[EMAIL PROTECTED]> on scroll <[EMAIL PROTECTED]> > > How do you know the exact EOT when using hardware compression? Very good point. I would answer that with: a) it is suggested that you don't use hardware compression due to other difficulties it poses for amanda b) if you want to split dumps across tapes, then you CANNOT use hardware compression I think this sounds reasonable. No it does not correct the problem in *all* cases but does correct it for a number of people, and does provide some kind of a solution for those that want it. b. -- Brian J. Murrell
RE: amrecover gives strange error message
Found it! Hehe... I thought you could have comments in /etc/inetd.conf, as # at the end of the line, which you can't... well, that's that! Thanks for your patience! /Fredrik Persson > -Original Message- > From: Fredrik Persson P (QRA) [SMTP:[EMAIL PROTECTED]] > Sent: den 23 oktober 2000 18:43 > To: '[EMAIL PROTECTED]' > Subject: amrecover gives strange error message > > Hi folks! > > I think I've done a slight typo in some config file, I just can't (I've > tried!) find out what I've done. I'd be bery happy if someone could > explain > this to me. > > I've done a backup, no error messages. Just did amdump DailySet1 right at > the prompt. (DailySet1 is my only configuration.) > > Now, I'm on one of the slaves, and I'm trying to run amrecover. For test > purposes, I simply typed "amrecover" (as root). This is what I got back: > > AMRECOVER Version 2.4.1. Contacting server on backupserver ... > 501 Couldn't cd into /opt/amanda/etc/amanda/#added. Misconfiguration? > > ... and then I'm thrown back to the prompt again. > > I *suppose* I have done a misconfig somewhere but... I've looked and I > can't > seem to find it. > > Please, any help will be greatly appreciated! Thanks! > > /Fredrik Persson
Re: Not sure why chunker failed
On Oct 23, 2000, "Brian J. Murrell" <[EMAIL PROTECTED]>
wrote:
> find diskspace: size 186848 hf 153920 df 153888 da 153888 ha 153920
> find diskspace: not enough diskspace. Left with 32960 K
> driver: send-cmd time 15539.031 to chunker1: (null)chunker: error [bad command after
>RQ-MORE-DISK: 4]
> So there is that mesage "not enough diskspace. Left with 32960 K" but a
> df -k of my holding disk shows:
How much space did you tell Amanda to `use'?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: amrecover - testing file restore
On Oct 23, 2000, Denise Ives <[EMAIL PROTECTED]> wrote:
> No - that didn't check out. There is no - /admin1/home/user/dives on
> admin1. No sybase_error.log anywhere to be found on admin1.
It should be in the machine on which you run amrecover.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Backups on CD-RW
Hi! Anyone ever attempted to use amanda for creating backups on CD-RW disks? We currently use amanda with DDS tapes and it works great. However, having a way of backing up to CD-RW disks or dedicated hard disks would be very interesting. Thanks for any info. Patrik Rak
Problem with taper?
Below is the log I was sent for an amanda run last night. This started several days ago (while I was out of town, imagine *that*) after having amanda set up and running perfectly for several days. The error shows unable to allocate memory, but the server shows plenty of available memory. Does anyone have any ideas about this? System Operator wrote: > > *** THE DUMPS DID NOT FINISH PROPERLY! > > These dumps were to tapes . > Tonight's dumps should go onto 1 tape: Daily1. > > FAILURE AND STRANGE DUMP SUMMARY: > taper: FATAL shmget: Cannot allocate memory > > > DUMP SUMMARY: > DUMPER STATS TAPER STATS > HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s > -- -- -- > admin.pla / 1 8955 4096 45.70:05 801.0 FAILED -- > admin.pla /usr 18698917664 20.32:28 119.2 FAILED -- > db.planet /a 1 9706 2752 28.42:11 21.0 FAILED -- > > (brought to you by Amanda version 2.4.1p1) -- Drew Sanford Systems Administrator Planetwe.com Email: [EMAIL PROTECTED]
Re: Changing a tape's density
On Tue, 24 Oct 2000, Bernhard R. Erdmann wrote: >Paul Tomblin wrote: [snip] >> reformat? I don't have a bulk eraser. I tried using "mt setdensity >> DDS-2", but it didn't take. > >mt weof 5 >or >mt erase >or >dd if=/dev/zero bs=32k of=$TAPE In my own experience, using only a dd won't change the tape's format. My drives all see and use the original drive blocksize and compressions setting and use it until I overwrite it with a weof. I don't know if the erase will do it or not. I know when my drive is shoeshining on a tape header, an erase won't do it. I'm certain the dd won't... (4mm DAT of various vintanges, EXB-8500, EXB-8505). (Did you mean for the dd to overwrite the whole tape? Usually just whacking the header is sufficient. If not, add a count=NN to it.) -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: Using a cname for the amanda server
On Fri, 20 Oct 2000, Dean Pentcheff wrote: >Joi Ellis wrote: >> On Tue, 17 Oct 2000, Jonathan D. Proulx wrote: >... >> I'm also not sure I'd want the identity of my tape backup server >> visible with simple DNS queries, either. That makes it a juicy >> target. >> >You should be aware that a trivial port scan of the network will reveal >the Amanda hosts, so there's not much to be gained by a simple name >obfuscation. An example from our network: Well, yes, except that, until just last month, our DNS was managed by our ISP, and they published the entries for everything we gave them. The only service-like name we gave them was 'mail', everything else was simple host names. Now that we have our own internal DNS, we have fewer machines published. I hope.. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
trouble with samba2-20000418.diff
Hello all,
once more again i have trouble with amanda.
When I dump PC clients (with smb) i always get a mail with the results.
That's OK but in the mail the PC dumps are described as a Strange_dump (
Failure and Strange Dump summary: peter //IDEFIX/nttest lev 0 Strange ).
I searched for patches and found that i should use the samba2-2418.diff
patch. So I installed it, but as result i get an error during the make
prozedure. configure runs well, but when i call make i get the following
error message:
:
:
Making all in client-scr
make[1]: Entering directory '/inst/amanda-2.4.1p1/client-scr'
gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-scr
-D_FILE_OFFSET_BITS=64
-g -c sendbackup-gnutar.c
sendbackup-gnutar.c:114: parse error before '{'
sendbackup-gnutar.c:114: incompatible types in initialization
sendbackup-gnutar.c:114: initializer element for 're_table[35].typ' is not
constant
sendbackup-gnutar.c:115: parse error before '}'
make[1]: *** [sendbackup-gnutar.o] Error 1
make[1]: Leaving directory '/inst/amanda-2.4.1p1/client-scr'
make: *** [all-recursive] Error 1
I looked in sendbackup-gnutar.c
when i change following all is ok again:
@@ start at Row 109:
{ DMP_NORMAL, "^ERRDOS - ERRnoaccess listing", 1},
{ DMP_NORMAL, "^ERRDOS - [0-9][0-9]* opening remote file", 1},
#endif
/* catch-all: DMP-STRANGE is returned for all other lines */
- { DMP_STRANGE, NULL, 0} // I removed this line and make works fine
};
extern char *efile;
int cur_level;
char*cur_disk;
time_t cur_dumptime;
I don't think that this i the best sollution, because this line is given
when the other possibilities before are not working. (So that my
understanding, but I'm not sure if this is correct). What can i do ? Sould
i omit the patch (samba2-2418.diff) and use amanda without the patch or
is there another possibility?
Thank a lot to all who help
With kind regard
Frank
RE: run a DB shutdown before backup
A company called RTDA makes a product called VOV that we use to do job queuing to a farm of PCs. As I understand it, all this does is pass a string from a master queue control to slave daemons running on the PCs and each daemon launches what is passed to it. It's not secure, but with a little work that idea could be expanded on. Ernie > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Joi Ellis > Sent: Wednesday, October 18, 2000 5:02 PM > To: Shakaib Sayyid > Cc: [EMAIL PROTECTED] > Subject: Re: run a DB shutdown before backup > > > On Wed, 18 Oct 2000, Shakaib Sayyid wrote: > > >Date: Wed, 18 Oct 2000 15:52:30 -0400 (EDT) > >From: Shakaib Sayyid <[EMAIL PROTECTED]> > >To: [EMAIL PROTECTED] > >Subject: run a DB shutdown before backup > > > > > >Is there any way I can run a shutdown script before the amanda > >backup start and run a start script once the backup is done. > > > >This is to backup FoxPro Db that we are running on one of our > >Amanda clients. > > Sounds like this is on a windows box. I don't think there's any way > (presently) for amanda to trigger a script on a windows box. (It's > possible on a unix box.) The best thing you can probably do is use > something like NT's "at" thingy to run the shutdown command shortly > before amdump starts, and again to run the startup command X hours > later. > > Does anyone have a better suggestion? > > -- > Joi Ellis > [EMAIL PROTECTED], http://www.visi.com/~gyles19/ > >
wrong tape problem
Hy, I have a problem with amandas tapes. 5 days ago i got the last mail with a successful backup message: --- snip --- These dumps were to tape net-daily4. Tonight's dumps should go onto 1 tape: a new tape. --- snap --- the day after that, the tape was changed to the one one number higher, but the message was: --- snip --- *** A TAPE ERROR OCCURRED: [cannot overwrite active tape net-daily5]. *** PERFORMED ALL DUMPS TO HOLDING DISK. --- snap --- since than i got every day when amanda was supposed to run a similar message. what went wrong here? i do not know _exactly_ if tape changes and everything ran as it should as i do not do that on my own and have no physical access to the machine, so i would need som,e information how i can figure out what went wrong. thanx in advance, henning -- Henning Sprang Netropol Digitale Systeme Lagerstrasse 30a Tel: +49 40 4325 D-20357 Hamburg Fax: +49 40 43189490 [EMAIL PROTECTED]
Re: wrong tape problem
Henning Sprang wrote: > > I have a problem with amandas tapes. > 5 days ago i got the last mail with a successful backup message: > > --- snip --- > These dumps were to tape net-daily4. > Tonight's dumps should go onto 1 tape: a new tape. > --- snap --- > > the day after that, the tape was changed to the one one number higher, > but the message was: > > --- snip --- > *** A TAPE ERROR OCCURRED: [cannot overwrite active tape net-daily5]. > *** PERFORMED ALL DUMPS TO HOLDING DISK. My guess would be that a couple of tapes in the net-daily sequence got skipped. Since Amanda hasn't written to a tapecycle worth of them yet it doesn't want to overwrite a newer tape with data. Check the contents of the tapelist file and you should see what tapes it's used and what got skipped. -- [EMAIL PROTECTED] - HMC UNIX Systems Manager
Re: taper: FATAL syncpipe_get: w: unexpected EOF
On Oct 23, 2000, "S M" <[EMAIL PROTECTED]> wrote:
> Could someone pls help to fix this out?
You're running out of tape.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Backups on CD-RW
On Oct 24, 2000, Patrik Rak <[EMAIL PROTECTED]> wrote:
> Anyone ever attempted to use amanda for creating backups on CD-RW disks?
Yep. You may even be able to find recipes to do that in the FAQ. If
not, you should be able to find them in the archives, in which case
I'm sure you'd be kind enough to contribute a new entry to FAQ-O-Matic
:-) :-)
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Problem with taper?
On Oct 24, 2000, Drew Sanford <[EMAIL PROTECTED]> wrote:
>> taper: FATAL shmget: Cannot allocate memory
ipcs -l
ipcrm
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
trouble with samba2-20000418.diff/second.edition
I described that i have problems with the samba2-2418.diff patch. I copied the changes with hand (means that i deleted/paste the lines manually). Could this be the mistake. I tried to use the patch instruction with no success. Only the following message appears: patching file 'sendbackup-gnutar.c' Hunk #1 FAILED at 63. Hunk #2 FAILED at 90. Hunk #3 FAILED at 298. Hunk #4 FAILED at 305. 4 out of 4 hunks FAILED -- savings rejects to sendbackup-gnutar.c.rej patching file 'sendsize.c' Hunk #1 FAILED at 571. Hunk #2 FAILED at 918. Hunk #3 FAILED at 948. Hunk #4 FAILED at 958. 4 out of 4 hunks FAILED -- savings rejects to sendsize.c.rej patching file 'config.h.in' : : Can anybody tell me the right patch instruction (mean the right options or better the exact syntax). Thanks a lot farnk Rippert
gtar causing kernel hang
Hello everyone. On one machine, and one machine only, the backup process is crashing the server. In particular, it appears to be gtar that is making it hang. This machine is configured similarly to every other machine that I'm backing up, but this is the only one having problems. Here is the error that shows up in /var/log/messages: Oct 24 00:50:08 banjo kernel: Unable to handle kernel paging request at virtual address 0004a2bd Oct 24 00:50:08 banjo kernel: current->tss.cr3 = 133c, %%cr3 = 133c Oct 24 00:50:08 banjo kernel: *pde = Oct 24 00:50:08 banjo kernel: Oops: Oct 24 00:50:08 banjo kernel: CPU:0 Oct 24 00:50:08 banjo kernel: EIP:0010:[dput+295/328] Oct 24 00:50:08 banjo kernel: EFLAGS: 00010296 Oct 24 00:50:08 banjo kernel: eax: 0004a27d ebx: dc027120 ecx: c5616fa0 edx: d6794f80 Oct 24 00:50:08 banjo kernel: esi: edi: cf5a8330 ebp: 0568 esp: dcce3e7c Oct 24 00:50:08 banjo kernel: ds: 0018 es: 0018 ss: 0018 Oct 24 00:50:08 banjo kernel: Process gtar (pid: 7926, process nr: 53, stackpage=dcce3000) Oct 24 00:50:08 banjo kernel: Stack: c56165a0 c012e758 dc027120 dcce3ed0 dcce3ed0 c023715c 1006 dcce3ed0 Oct 24 00:50:08 banjo kernel:0001 1006 c012f6d3 f562 1006 c0268f60 c023715c Oct 24 00:50:08 banjo kernel:c0268f60 cf6598c0 dd26d320 dd26d36c dcce3ed0 dcce3ed0 c012f73a Oct 24 00:50:08 banjo kernel: Call Trace: [prune_dcache+248/300] [try_to_free_inodes+199/264] [grow_inodes+30/384] [get_new_inode+18 5/280] [iget+88/96] [ext2_lookup+84/124] [real_lookup+79/160] Oct 24 00:50:08 banjo kernel:[lookup_dentry+296/488] [__namei+40/88] [sys_newlstat+14/96] [system_call+52/56] [startup_32+43 /286] Oct 24 00:50:08 banjo kernel: Code: 8b 40 40 50 56 68 60 41 1f c0 e8 ee 49 fe ff c7 05 00 00 00 After this, the machine is fully hung, and I have to reboot it. I'm thinking maybe gtar is hosing the stack somehow. Any ideas? Or do I need to send this to the tar bug list? Here's the stats on the server itself: 400MHz PII, 512MB RAM, RAID-5 SCSI with a DPT Decade card. Kernel 2.2.16-3, Amanda 2.4.1p1, gtar 1.12. Thanks for any help! -D
amandaidx/tcp unknown protocol
Hi, The computer, cass150, that was acting as the Amanda server needed to be moved to a new location and given a slightly different configuration ( systemwise, that is ). Amanda seemed to be working fine but, when I recently tried an 'amrecover' from a client, I get: AMRECOVER Version 2.4.1p1. Contacting server on cass150 ... amrecover: amandaidx/tcp unknown protocol: No such file or directory I tried putting "amandaidx 10082/tcp" in /etc/services on the client as read from the server ( attempting to make any guesses from the error messages as to a solution ) which seemed to fix things until I actually got to an 'extract' and then amrecover failed with a similar error. >From the error message, I'm not exactly sure which file or directory "No such file or directory" refers to ( and I've run the 'patch-system' on the client which should suggest that the client has been provided with what it needs ). -- Paul Yeatman(858) 534-9896 [EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
Re: amandaidx/tcp unknown protocol
>I tried putting "amandaidx 10082/tcp" in /etc/services on the >client ... That was the right thing to do. >... as read from the server ... Huh? >... which seemed to fix >things until I actually got to an 'extract' and then amrecover >failed with a similar error. So did adding "amidxtape 10083/tcp" fix this as well? >From the error message, I'm not exactly sure which file or >directory "No such file or directory" refers to ... "No such file or directory" is the text conversion of the Unix error code ENOENT, however that error code is returned by all sorts of functions to indicate "no entry was found". When Amanda called the routine to look up "amandaidx/tcp" it got back ENOENT because you didn't have it listed in /etc/services, then it translated that to text (also via a standard system provided function) to "No such file or directory". >( and I've run the >'patch-system' on the client which should suggest that the client >has been provided with what it needs ). I've never been convinced patch-system has any chance of working given all the various OS's Amanda runs on. Much better to read the installation instructions and do what they tell you (IMHO). >Paul Yeatman John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: trouble with samba2-20000418.diff/second.edition
>I described that i have problems with the samba2-2418.diff patch. I >copied the changes with hand (means that i deleted/paste the lines >manually). ... That was probably a mistake. Why didn't you get it "electronically"? For instance, if you got it from the Amanda web page, why not use "save as" and store it in a file, then transfer that file to where the Amanda sources are? Using things like copy/paste or retyping the text by hand has a close to zero chance of working. Among other things, tabs and strings of spaces are likely to be lost, and those are critical to patch for matching the source against the diff. >Can anybody tell me the right patch instruction (mean the right options or >better the exact syntax). The diffs have to be **exactly** correct for the patch program to be able to work properly. Once you get that corrected, I suspect patch will work for you. >farnk Rippert John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: gtar causing kernel hang
>After this, the machine is fully hung, and I have to reboot it. I'm >thinking maybe gtar is hosing the stack somehow. I'm thinking user programs cannot (in general) cause the kernel to panic, so this isn't an Amanda or tar problem, but should be reported to the kernel folks. >-D John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Level 0 failed
>and when I run the dump i get > >hostname /dev/dsk/c0t0d0s0 lev 0 FAILED [can't switch to incremental dump] Didn't it say anything else? Like dumps too big for tape or words to that effect? How big is your tape (times runtapes)? How much data are you trying to back up? >Matt John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: gtar causing kernel hang
This is a kernel problem, *not* a gtar problem. Gtar is trying to do an lstat() system call, and the kernel has apparently run out of resources -- unless the disk hasn't been fsck'ed, in which case, there may well be a block that is corrupted (and it probably contains inodes). Be assured, if /var/log/messages gives you a "kernel:" message, then the problem is either in the kernel itself, or possibly in the hardware (i.e., you could have an uncorrected memory error (do not *ever* use non-ECC memory on a machine you want to be even remotely reliable!)). Recommendation: fsck the partition that gtar was working on. Run a serious memory checker (wish I had one, but then, I only use ECC memory). Good luck, Marty [EMAIL PROTECTED] wrote: > > Hello everyone. On one machine, and one machine only, the backup process > is crashing the server. In particular, it appears to be gtar that is > making it hang. This machine is configured similarly to every other > machine that I'm backing up, but this is the only one having problems. > > Here is the error that shows up in /var/log/messages: > > Oct 24 00:50:08 banjo kernel: Unable to handle kernel paging request at > virtual address 0004a2bd > Oct 24 00:50:08 banjo kernel: current->tss.cr3 = 133c, %%cr3 = > 133c > Oct 24 00:50:08 banjo kernel: *pde = > Oct 24 00:50:08 banjo kernel: Oops: > Oct 24 00:50:08 banjo kernel: CPU:0 > Oct 24 00:50:08 banjo kernel: EIP:0010:[dput+295/328] > Oct 24 00:50:08 banjo kernel: EFLAGS: 00010296 > Oct 24 00:50:08 banjo kernel: eax: 0004a27d ebx: dc027120 > ecx: c5616fa0 edx: d6794f80 > Oct 24 00:50:08 banjo kernel: esi: edi: cf5a8330 > ebp: 0568 esp: dcce3e7c > Oct 24 00:50:08 banjo kernel: ds: 0018 es: 0018 ss: 0018 > Oct 24 00:50:08 banjo kernel: Process gtar (pid: 7926, process nr: 53, > stackpage=dcce3000) > Oct 24 00:50:08 banjo kernel: Stack: c56165a0 c012e758 dc027120 dcce3ed0 > dcce3ed0 c023715c 1006 dcce3ed0 > Oct 24 00:50:08 banjo kernel:0001 1006 c012f6d3 f562 > 1006 c0268f60 c023715c > Oct 24 00:50:08 banjo kernel:c0268f60 cf6598c0 dd26d320 dd26d36c > dcce3ed0 dcce3ed0 c012f73a > Oct 24 00:50:08 banjo kernel: Call Trace: [prune_dcache+248/300] > [try_to_free_inodes+199/264] [grow_inodes+30/384] [get_new_inode+18 > 5/280] [iget+88/96] [ext2_lookup+84/124] [real_lookup+79/160] > Oct 24 00:50:08 banjo kernel:[lookup_dentry+296/488] > [__namei+40/88] [sys_newlstat+14/96] [system_call+52/56] [startup_32+43 > /286] > Oct 24 00:50:08 banjo kernel: Code: 8b 40 40 50 56 68 60 41 1f c0 e8 ee 49 > fe ff c7 05 00 00 00 > > After this, the machine is fully hung, and I have to reboot it. I'm > thinking maybe gtar is hosing the stack somehow. > > Any ideas? Or do I need to send this to the tar bug list? Here's the > stats on the server itself: > > 400MHz PII, 512MB RAM, RAID-5 SCSI with a DPT Decade card. Kernel > 2.2.16-3, Amanda 2.4.1p1, gtar 1.12. > > Thanks for any help! > > -D -- Marty Shannon, RHCE, Sr. Systems Developer mailto:[EMAIL PROTECTED]
Re: Backups on CD-RW
There is a link from backupcentral.com under freeware. rcb On Tue, 24 Oct 2000, Patrik Rak wrote: > Hi! > > Anyone ever attempted to use amanda for creating backups on CD-RW disks? > > We currently use amanda with DDS tapes and it works great. However, having > a way of backing up to CD-RW disks or dedicated hard disks would be very > interesting. > > Thanks for any info. > > Patrik Rak > -- - Richard Bond ([EMAIL PROTECTED] (206) 605-3561 System Administrator K-351, Health Sciences Center Department of Molecular Biotechnology Box 357730 University of Washington Seattle, WA 98195
Re: trouble with samba2-20000418.diff/second.edition
- Original Message - From: John R. Jackson <[EMAIL PROTECTED]> To: Frank Rippert <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, October 24, 2000 8:05 PM Subject: Re: trouble with samba2-2418.diff/second.edition > >I described that i have problems with the samba2-2418.diff patch. I > >copied the changes with hand (means that i deleted/paste the lines > >manually). ... > > That was probably a mistake. Why didn't you get it "electronically"? > For instance, if you got it from the Amanda web page, why not use "save > as" and store it in a file, then transfer that file to where the > Amanda sources are? > > Using things like copy/paste or retyping the text by hand has a close to > zero chance of working. Among other things, tabs and strings of spaces > are likely to be lost, and those are critical to patch for matching the > source against the diff. > > >Can anybody tell me the right patch instruction (mean the right options or > >better the exact syntax). > > The diffs have to be **exactly** correct for the patch program to be > able to work properly. Once you get that corrected, I suspect patch > will work for you. > > >farnk Rippert > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] >
Re: Problem with taper?
Alexandre Oliva wrote: > > On Oct 24, 2000, Drew Sanford <[EMAIL PROTECTED]> wrote: > > >> taper: FATAL shmget: Cannot allocate memory > > ipcs -l > ipcrm > Thanks. That (and a little studying the man pages :) ) did the trick. Was this a luck geuss, or have you encountered it before? Anyone know exactly what causes this to happen? -- Drew Sanford Systems Administrator Planetwe.com Email: [EMAIL PROTECTED]
error running amrecover on client
amrecover works on my tape server host machine but i am trying to use amrecover to test restore of files on my client machine. *I do not think so but: Do I need to set up the config directory and the amanda.conf file on the client machine as well? Amanda is installed on my client machine. My host machine is backing up my client machine successfully. Here is the indexing defined in the amanda.conf my the host machine. I am not surre if I have to set this up on the client machine. I thought amanda only cared about the host config files. amanda.conf on host machine* # historic reasons, since now it is supposed to be a directory (unless # you have selected some database format other than the `text' default) infofile "/usr/adm/amanda/daily/curinfo"# database DIRECTORY logdir "/usr/adm/amanda/daily"# log directory indexdir "/usr/adm/amanda/daily/index" # index directory tapelist "/usr/adm/amanda/daily/tapelist" # list of used tapes # tapelist is stored, by default, in the directory that contains amanda.conf attempt to use amrecover on client machine [root@admin1 sbin]# /usr/local/pkg/amanda-2.4.1p1/sbin/amrecover daily AMRECOVER Version 2.4.1p1. Contacting server on admin1.corp.walid.com ... amrecover: Unexpected server end of file and [root@admin1 amanda]# /usr/local/pkg/amanda-2.4.1p1/sbin/amrecover daily -s admin1.corp.walid.com AMRECOVER Version 2.4.1p1. Contacting server on admin1.corp.walid.com ... amrecover: Unexpected server end of file [dives@admin1 amanda]# attempt to restore files to client machine using amrecover from host machine** root@sundev1:etc/amanda/daily# amrecover daily -s admin1.corp.walid.com AMRECOVER Version 2.4.1p1. Contacting server on admin1.corp.walid.com ... amrecover: Unexpected server end of file amrecover.debug*** [dives@admin1 amanda]# cat amrecover.debug amrecover: debug 1 pid 6523 ruid 0 euid 0 start time Tue Oct 24 18:47:37 2000 other notes*** amindexd and amidxtaped services have been installed and enabled to inetd on host and client machines. these entries are in both .amandahosts files on the host and client. .amandahosts [EMAIL PROTECTED] amanda sundev1.corp.walid.com root admin1.corp.walid.com amanda admin1.corp.walid.com root Hope this information helps.thank you much. -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: Problem with taper?
On Oct 24, 2000, Drew Sanford <[EMAIL PROTECTED]> wrote:
> Was this a luck geuss, or have you encountered it before?
People have encountered it before. IIRC, in certain failure modes,
taper may fail to release shared memory segments. I seem to recall
this was already fixed in the CVS tree, but I could be wrong.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: groups when using tar
On Mon, 23 Oct 2000, John R. Jackson wrote: > >I'm familiar with the amanda user needing to be in the group > >allowed to read raw devices when using 'dump'. Is this also > >suffient when using 'tar' or do the file and directory permissions > >prevail? > > Amanda runs tar underneath a setuid-root wrapper program, so it doesn't > need any special permission setup. So this means I don't have to add amanda to the group that has write permission on the raw device. right? Peter
Re: groups when using tar
>So this means I don't have to add amanda to the group that has write >permission on the raw device. right? You have a group with write access to the raw device??? Ick. But the answer is yes, you are correct. When using GNU tar, the raw devices (and their permissions) are irrelevant. >Peter John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: groups when using tar
On Tue, 24 Oct 2000, John R. Jackson wrote: > You have a group with write access to the raw device??? Ick. Err, this meant read access :-) Peter
never mind - testing amrecover on client host
I got it working - [dives@admin1 dives]# /usr/local/pkg/amanda-2.4.1p1/sbin/amrecover daily -s sundev1.corp.walid.com AMRECOVER Version 2.4.1p1. Contacting server on sundev1.corp.walid.com ... 220 sundev1 AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2000-10-24) 200 Working date set to 2000-10-24. 200 Config set to daily. 200 Dump host set to admin1.corp.walid.com. $CWD '/home/user/dives' is on disk 'sda10' mounted at '/home'. 200 Disk set to sda10. /home/user/dives WARNING: not on root of selected filesystem, check man-page! amrecover> -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: error running amrecover on client
>Do I need to set up the config directory and the amanda.conf file on the >client machine as well? No. >[root@admin1 sbin]# /usr/local/pkg/amanda-2.4.1p1/sbin/amrecover daily >AMRECOVER Version 2.4.1p1. Contacting server on admin1.corp.walid.com ... >amrecover: Unexpected server end of file What's in /tmp/amanda/amindexd*debug on admin1.corp.walid.com? Can the client resolve both the host name and IP address of the server? Can the server resolve both the host name and IP address of the client? >Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
extract_list - child returned non-zero status: 1
Here is the error message being generated while running amrecover on client machine. ***testing amrecover** amrecover> add installamanda Added /user/dives/installamanda amrecover> extract Extracting files using tape drive /dev/null on host admin1.corp.walid.com. The following tapes are needed: daily555 Restoring files into directory /home/user/dives Continue? [Y/n]: y Load tape daily555 now Continue? [Y/n]: y EOF, check amidxtaped.debug file. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 *amidxtaped.debug* [dives@admin1 amanda]# cat amidxtaped.debug amidxtaped: debug 1 pid 8330 ruid 543 euid 543 start time Tue Oct 24 20:33:41 2000 amidxtaped: version 2.4.1p1 > SECURITY USER root bsd security: remote host admin1.corp.walid.com user root local user amanda amandahosts security check passed > 6 amrestore_nargs=6 > -h > -p > /dev/null > admin1.corp.walid.com > ^sda10$ > 20001023 Ready to execv amrestore with: path = /usr/local/pkg/amanda-2.4.1p1/sbin/amrestore argv[0] = "amrestore" argv[1] = "-h" argv[2] = "-p" argv[3] = "/dev/null" argv[4] = "admin1.corp.walid.com" argv[5] = "^sda10$" argv[6] = "20001023" amrestore: missing file header block amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of tape: date amidxtaped: amrestore terminated normally with status: 1 Rewinding tape: rewinding tape: Inappropriate ioctl for device amidxtaped: pid 8330 finish time Tue Oct 24 20:34:11 2000 [dives@admin1 amanda]# -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: extract_list - child returned non-zero status: 1
>Extracting files using tape drive /dev/null on host admin1.corp.walid.com. Ummm, /dev/null makes for a really bad tape drive :-). Try the -d option on amrecover. >Denise E. Ives John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: extract_list - child returned non-zero status: 1
On Tue, 24 Oct 2000, Denise Ives wrote: > Here is the error message being generated while running amrecover on > client machine. > > ***testing amrecover** > > amrecover> add installamanda > Added /user/dives/installamanda > amrecover> extract > > Extracting files using tape drive /dev/null on host admin1.corp.walid.com. > The following tapes are needed: daily555 > > Restoring files into directory /home/user/dives > Continue? [Y/n]: y > > Load tape daily555 now > Continue? [Y/n]: y I've tried it before, but I failed to insert a tape in my /dev/null device. I asume that your /dev/null is not different than mine is. Try using amrecover -d /path/to/tape -- Tot ziens, Bart-Jan
Re: extract_list - child returned non-zero status: 1
Yes - you are awesome. thankyou - On Tue, 24 Oct 2000, John R. Jackson wrote: > >Extracting files using tape drive /dev/null on host admin1.corp.walid.com. > > Ummm, /dev/null makes for a really bad tape drive :-). > > Try the -d option on amrecover. > > >Denise E. Ives > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] > -- Denise E. Ives [EMAIL PROTECTED] Systems Engineer734.822.2037 Multilingual Internet Domain Name Registrations - http://www.walid.com
Re: extract_list - child returned non-zero status: 1
On Oct 24, 2000, Denise Ives <[EMAIL PROTECTED]> wrote:
> Extracting files using tape drive /dev/null on host admin1.corp.walid.com.
^
When you run amrecover, you'll have to specify the tape drive to be
used on the tape server.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: all tests pass but cannot make backup
Hi John, Thanks for your comments. I noticed the following runtar error in sendsize.debug: "runtar: error [must be invoked by root]". The problem is that for the rest of the machines I compiled amanda with user amanda, while for the last SGI I used the precompiled tardist. The precompiled version seems to be compiled with user root. The amanda server contacts the clients as amanda, while the last SGI expects not amanda but root. I wonder is there a way to change the user for amanda or I have to compile amanda from source? Thanks, Ted P.S. Here is sendsize.debug: bash-2.04# more sendsize.debug sendsize: debug 1 pid 647466 ruid 1136 euid 1136 start time Tue Oct 24 13:11:42 2000 /usr/freeware/libexec/sendsize: version 2.4.1p1 calculating for amname '/usr5/people', dirname '/usr5/people' sendsize: getting size via gnutar for /usr5/people level 0 sendsize: running "/usr/freeware/libexec/runtar --create --directory /usr5/peopl e --listed-incremental /var/amanda/gnutar-lists/craft14_usr5_people_0.new --spar se --one-file-system --ignore-failed-read --totals --file /dev/null --exclude-fr om=/usr/local/etc/amanda/exclude ." runtar: error [must be invoked by root] . (no size line match in above gnutar output) . sendsize: pid 647466 finish time Tue Oct 24 13:11:42 2000 "John R. Jackson" wrote: > > > craft14/usr7/people lev 0 FAILED [disk /usr7/people offline on craft14 > >?] > > You probably need to catch a sendbackup*debug file on that client that > is for this file system. There are three ways to do this: > > * Catch Amanda while it is trying to back up this file system on > this client and before sendbackup.debug gets overwritten with the > next backup (which is difficult). > > * Change your disklist to only contain this client/file system and > do a backup of just it so sendbackup.debug on the client only has > the output from attempting this one file system. You might also > temporarily set "record no" and "tapedev no-such-device" so the > backup does not really do anything. > > * Rebuild Amanda with --with-pid-debug-files so each process on the > client has its own debug file, then you can find the one that matches > this failure. If you do this, you'll have to remember to clean out > /tmp/amanda occasionally. > > >Ted > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
3 Questions on Disks
OK, I'm adding more and more clients to my server. So far so good. I've run into 3 things though. 1) I have a device /dev/md/dsk/d10 which is a disksuite disk. How do I specify it in the config, or do I just use "d10" instead of the c0t0d0s0 device? 2) Is it possible to back up a directory on a filesystem instead of the filesystem? I have the database exporting to /data/exports but the live data is in /data/oradata and /data is one large filesystem. Can I get just /data/exports? 3) What is this from amstatus: nose.mydomain.com:c1t0d0s6 1 [dumps way too big, must skip incremental dumps] When will it pick up and dump this filesystem? Robert :wq! --- Robert L. Harris| Micros~1 : Unix System Administrator |For when quality, reliability at Agency.com | and security just aren't \_ that important! DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. FYI: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
Re: all tests pass but cannot make backup
>... I wonder is there a way to change the user for amanda or I have to compile >amanda from source? It's built into the binary, so you must rebuild from source. This is the reason the Amanda group usually recommends against pre-built packages. >Ted John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: 3 Questions on Disks
>1) I have a device /dev/md/dsk/d10 which is a disksuite disk. How do I >specify > it in the config, or do I just use "d10" instead of the c0t0d0s0 >device? I would list it by mount point rather than device name, i.e. /usr/local. However, if you want to enter the device name, it would be: /dev/md/rdsk/d10 Note the rdsk instead of dsk. >2) Is it possible to back up a directory on a filesystem instead of the >filesystem? It depends on which dump program you use. If you use GNU tar you can list individual subdirectories of mount points. If you use something like ufsdump, you usually cannot do subdirectories. >3) What is this from amstatus: > >nose.mydomain.com:c1t0d0s6 1 [dumps way too big, must skip >incremental dumps] > >When will it pick up and dump this filesystem? When the other file systems being dumped can do incrementals and there is enough tape space left to do this file system. My guess is you added a bunch of new disks which have to have a full dump done first and that squeezed out the possibility of doing this one in any form. Once the first full dump is done, things should settle back down, assuming you have enough tape capacity. >Robert John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover gives strange error message
"Fredrik Persson P (QRA)" wrote: > > Hi folks! > > AMRECOVER Version 2.4.1. Contacting server on backupserver ... > 501 Couldn't cd into /opt/amanda/etc/amanda/#added. Misconfiguration? > It looks for an amanda.conf file for a configuration called "#added". This is probably because "#added" is the compiled-in default of the configuration name. Try using your configuration: amrecover DailySet1 instead of just typing "amrecover" and expect everything to work fine. (you didn't RTFM, did you?) -- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: Level 0 failed
"Kavluk, Matt" wrote: > > Hi, > > Im running amanda 2.4.1p1 on Solaris 7. > > I am trying to force amanda to do level 0 dumps every time > > In my disklists file I have > > hostname /dev/dsk/c0t0d0s0 always-full > > and when I run the dump i get > > hostname /dev/dsk/c0t0d0s0 lev 0 FAILED [can't switch to incremental dump] > Try dumpcycle 0, instead of strategy always-full. -- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: Not sure why chunker failed
"Brian J. Murrell" wrote: > > find diskspace: want 169472 K > find diskspace: size 169472 hf 501408 df 501376 da 169472 ha 169504 > find diskspace: selected /hd1 free 501408 reserved 169504 dumpers 0 > merging holding disk /hd1 to disk localhost:/data/mp3, add 169504 for reserved >3558816, left 0 > driver: send-cmd time 13987.981 to chunker1: CONTINUE Look at the "reserved 3558816" above, check the "reserve" parameter in amanda.conf and figure if it is right. I suspect you are trying to do a full backup of /data/mp3, but the reserve parameter is 100. Try a smaller value, say, reserve 30. -- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: Fw: BackUpGrp AMANDA MAIL REPORT FOR October 22, 2000
(I don't know if this message did it to the list, so I try again...) Rolf Olsen wrote: > > FAILURE AND STRANGE DUMP SUMMARY: > > hal2.mored /home4 lev 0 FAILED [missing result for /home4 in > hal2.mored.net response] Increase etimeout in amanda.conf. -- Regards Chris Karakas Don´t waste your cpu time - crack rc5: http://www.distributed.net
Re: Changing a tape's density
Quoting Joi Ellis ([EMAIL PROTECTED]): > On Tue, 24 Oct 2000, Bernhard R. Erdmann wrote: > >Paul Tomblin wrote: > [snip] > >> reformat? I don't have a bulk eraser. I tried using "mt setdensity > >> DDS-2", but it didn't take. > >mt weof 5 > >or > >mt erase > >or > >dd if=/dev/zero bs=32k of=$TAPE > > In my own experience, using only a dd won't change the tape's format. My > drives all see and use the original drive blocksize and compressions > setting and use it until I overwrite it with a weof. I don't know if > the erase will do it or not. I know when my drive is shoeshining on a > tape header, an erase won't do it. I'm certain the dd won't... > > (4mm DAT of various vintanges, EXB-8500, EXB-8505). > > (Did you mean for the dd to overwrite the whole tape? Usually just > whacking the header is sufficient. If not, add a count=NN to it.) So far nothing has worked. I've tried "mt weof 10", "mt erase" and "mt setdensity 0x24", and nothing has worked. -- Paul Tomblin <[EMAIL PROTECTED]>, not speaking for anybody Real computer scientists despise the idea of actual hardware. Hardware has limitations, software doesn't. It's a real shame that Turing machines are so poor at I/O.
Compile error?
I've built amanda so far on about 6 clients. On # 7 I'm getting this: gcc -g -o .libs/amrecover amrecover.o display_commands.o extract_list.o help.o set_commands.o uparse.o uscan.o -ll -R/usr/local/lib ../client-src/.libs/libamclient.so -lgen -lm -ltermcap -lsocket -lnsl -lintl -R/usr/local/lib ../tape-src/.libs/libamtape.so -lgen -lm -ltermcap -lsocket -lnsl -lintl -R/usr/local/lib ../common-src/.libs/libamanda.so -lgen -lm -ltermcap -lsocket -lnsl -lintl -lgen -lm -ltermcap -lsocket -lnsl -lintl Undefined first referenced symbol in file yy_scan_string uscan.o ld: fatal: Symbol referencing errors. No output written to .libs/amrecover *** Error code 1 make: Fatal error: Command failed for target `amrecover' Current working directory /home/roharris/Amanda/amanda-2.4.1p1/recover-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Anyone seen this? Robert -- :wq! --- Robert L. Harris| Micros~1 : Unix System Administrator |For when quality, reliability at Agency.com | and security just aren't \_ that important! DISCLAIMER: These are MY OPINIONS ALONE. I speak for no-one else. FYI: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
strangely slow amrecover
Hi, I've recently been doing more-than-my-usual backups after making some changes in the Sun cluster here. As I like to do, I want to test the backups by attempting a restore of one of the directories on one of the disks that has just been backed up. The backups seem to be running normally but, as I'm trying to restore a directory just under 100 megs from one such backup, it runs strangely slowly. After starting the restore (using 'amrecover'), I check that files and directories are indeed being created. Good. I think, "hmmm, a 100 megs, should take well less than an hour". Yet after running quite awhile, I decided to leave it to finish while at lunch. Returning an hour or so later, I returned to find the program still running. The read light on the tape drive continued to flash yet the size of data on the client disk was apparently not changing. Thinking something must be wrong, I aborted 'amrecover' and restarted things. Afterall, I was playing around with the /etc/services file during the restore. This following time, not having erased the files and directories that were restored the first time to the client disk, I can't see that anything is being restored. 'df's of the partition and 'du's of the directory show no change in size though, as with the first time, the tape drive read light is slowly flashing away. The only proof that anything has happened at all was the appearance of a finite number of: restore: : File exists which appeared awhile after beginning the extraction though no activity has been seen since. Is there anyway to monitor amrecover's activity? I checked the man page for a verbose flag but apparently this doesn't exist. I could stop things again and try the restore with 'amrestore' directly using the verbose mode with 'ufsrestore' but only part of this test is to ensure that I can really restore things. The other is to prove I can use 'amrecover' to do so. If I can't get amrecover to work, I might as well turn indexing off. -- Paul Yeatman(858) 534-9896 [EMAIL PROTECTED] == ==Proudly brought to you by Mutt== ==
I think I have an mtx problem.... advice?
I am getting these error messages. I am working around the problem by manually loading the tape into the drive (an ADIC FastStor 22). I think the problem is actually an MTX problem because of the following: kite!backup 232# mtx -f /dev/tape-changer unload Unloading Data Transfer Element into Storage Element 8...mtx: Request Sense: Long Report=yes mtx: Request Sense: Valid Residual=no mtx: Request Sense: Error Code=70 (Current) mtx: Request Sense: Sense Key=Illegal Request mtx: Request Sense: FileMark=no mtx: Request Sense: EOM=no mtx: Request Sense: ILI=no mtx: Request Sense: Additional Sense Code = 3B mtx: Request Sense: Additional Sense Qualifier = 90 mtx: Request Sense: BPV=no mtx: Request Sense: Error in CDB=no mtx: Request Sense: SKSV=no mtx: MOVE MEDIUM from Element Address 82 to 8 Failed kite!backup 233# However, I can use mtx to load the tape into the drive. Anybody have any advice? -- Jeff Silverman, sysadmin for the Research Computing Systems (RCS) University of Washington, School of Engineering, Electrical Engineering Dept. Box 352500, Seattle, WA, 98125-2500 FAX: (206) 221-5264 Phone (206) 543-9378 [EMAIL PROTECTED] http://rcs.ee.washington.edu/~jeffs Amanda Tape Server Host Check - WARNING: /bkup: only 19389024 KB free (31457280 KB requested). amcheck-server: slot 8: date 20001021 label ssli-007 (active tape) amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online amcheck-server: slot expr:: no tape online ERROR: label ssli-008 or new tape not found in rack. (expecting tape ssli-008 or a new tape) NOTE: skipping tape-writable test. Server check took 23.712 seconds. Amanda Backup Client Hosts Check ERROR: canard: [access as backup not allowed from [EMAIL PROTECTED]] ERROR: kite: [PC SHARE //peacock/WEBTALK access error: host down or invalid password?] ERROR: kite: [PC SHARE //peacock/C access error: host down or invalid password?] WARNING: parrot: selfcheck request timed out. Host down? Client check: 26 hosts checked in 30.802 seconds, 4 problems found. (brought to you by Amanda 2.4.1p1) Tue Oct 24 16:26:31 PDT 2000
Re: Changing a tape's density
Paul Tomblin <[EMAIL PROTECTED]> wrote: > > So far nothing has worked. I've tried "mt weof 10", "mt erase" and "mt > setdensity 0x24", and nothing has worked. I had the same problem, where I accidentally used DDS-2 media in a DDS-1 drive, and the tapes wouldn't be recognized as DDS-2 anymore, even after bulk-erasure. In my case, I discovered that my DDS-2 drive had the Media Recognition System (MRS) switched OFF. I turned it on, and most of the tapes became useable again. I recommend never disabling MRS on a DDS drive. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Changing a tape's density
On Tue, 24 Oct 2000, Paul Tomblin wrote: >Date: Tue, 24 Oct 2000 18:33:11 -0400 >From: Paul Tomblin <[EMAIL PROTECTED]> >To: Amanda <[EMAIL PROTECTED]> >Subject: Re: Changing a tape's density > >So far nothing has worked. I've tried "mt weof 10", "mt erase" and "mt >setdensity 0x24", and nothing has worked. Perhaps we're missing something... DAT cartridges com in various flavors, right? DDS1 vs DDS2, etc. Perhaps your media knows it isn't tested for compressed drives and doesn't have the proper notches. IE I know there are notces in some types of cartridges to indicate length and/or maximum write density. And there are special notches on cleaning tapes. Perhaps your drive isn't cooperating because it doesn't like the media. Find a new cartridge you know is compatible with all your drive's features and see if your mt commands work better with the new cartridge. -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: trouble with samba2-20000418.diff/second.edition
On Tue, 24 Oct 2000, Frank Rippert wrote: >Date: Tue, 24 Oct 2000 19:25:12 +0200 >From: Frank Rippert <[EMAIL PROTECTED]> >To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, > "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> >Subject: trouble with samba2-2418.diff/second.edition > >I described that i have problems with the samba2-2418.diff patch. I >copied the changes with hand (means that i deleted/paste the lines >manually). Could this be the mistake. Patch is extremely sensitive to changes in the content of a patch file, including whitespace, blank lines, etc. Even downloading a patch with a browser improperly is enough to mangle the patch file. It looks like you used the correct patch command syntax. I suspect your patch file was corrupt. Patch could also be confused if you have a patch file for, say, Version 1.1 of a source file, but you're applying it against Version 1.3. Sometimes Patch gets it right, sometimes it just can't. If you can't get it to work, tell me where you found your patch file, and send my your two input files (sendbackup-gnutar.c, sendsize.c) and I'll try it. >I tried to use the patch instruction >with no success. Only the following message appears: > >patching file 'sendbackup-gnutar.c' >Hunk #1 FAILED at 63. >Hunk #2 FAILED at 90. >Hunk #3 FAILED at 298. >Hunk #4 FAILED at 305. >4 out of 4 hunks FAILED -- savings rejects to sendbackup-gnutar.c.rej >patching file 'sendsize.c' >Hunk #1 FAILED at 571. >Hunk #2 FAILED at 918. >Hunk #3 FAILED at 948. >Hunk #4 FAILED at 958. >4 out of 4 hunks FAILED -- savings rejects to sendsize.c.rej >patching file 'config.h.in' > : > : > > >Can anybody tell me the right patch instruction (mean the right options or >better the exact syntax). >Thanks a lot >farnk Rippert > > -- Joi Ellis [EMAIL PROTECTED], http://www.visi.com/~gyles19/
Re: all tests pass but cannot make backup
On Oct 24, 2000, Ted Sariyski <[EMAIL PROTECTED]> wrote:
> runtar: error [must be invoked by root]
Make sure it is setuid-root, and that it is not mounted with nosuid.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Changing a tape's density
Quoting Joi Ellis ([EMAIL PROTECTED]): > On Tue, 24 Oct 2000, Paul Tomblin wrote: > >So far nothing has worked. I've tried "mt weof 10", "mt erase" and "mt > >setdensity 0x24", and nothing has worked. > > Perhaps we're missing something... DAT cartridges com in various > flavors, right? DDS1 vs DDS2, etc. Perhaps your media knows it isn't > tested for compressed drives and doesn't have the proper notches. Nope, the tapes say DDS2, and one that I fortuitously hadn't done a amlabel on works as a DDS2. I stuck it in, did a tapetype on it, and it showed it as being 3.5 Gb and mt status showed it as DDS2. [amanda@stratus tape-src]$ mt status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 512 bytes. Density code 0x24 (DDS-2). Soft error count since last status=0 General status bits on (4101): BOT ONLINE IM_REP_EN -- Paul Tomblin <[EMAIL PROTECTED]>, not speaking for anybody "I find your lack of clue...disturbing" - SithAdmin Vader.
Re: Changing a tape's density
> Perhaps we're missing something... DAT cartridges com in various > flavors, right? DDS1 vs DDS2, etc. Perhaps your media knows it isn't > tested for compressed drives and doesn't have the proper notches. Well he said it's a 120 m tape. That's DDS2. DDS1 are 60 and 90 m. -Mitch
