[Fwd: TAKE 820267 - enable xfsrestore to run on non-xfs filesystem]

2001-10-18 Thread Bernhard R. Erdmann



 Original Message 
Subject: TAKE 820267 - enable xfsrestore to run on non-xfs filesystem
Date: Thu, 18 Oct 2001 13:59:49 +1000 (EST)
From: Ivan Rayner [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

This removes the restriction that xfsrestore -t must be run on an xfs
filesystem (which seemed to adversely affect amanda users).

It also removes the (harmless) space pre-allocation warnings if restore
is writing to a non-xfs filesystem.

Ivan


Date:  Wed Oct 17 20:54:34 PDT 2001
Workarea: 
omen.melbourne.sgi.com:/hosts/snort/diskb/build6/ivanr/isms/2.4.x-xfs

The following file(s) were checked into:
  bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs


Modid:  2.4.x-xfs:slinx:104985a
cmd/xfsdump/restore/namreg.c - 1.2
cmd/xfsdump/restore/dirattr.c - 1.3
- dont issue a warning if space pre-allocation failed for mmap
  file if the operation is not supported

cmd/xfsdump/restore/content.c - 1.16
- dont check whether housekeeping directory is on xfs filesystem



Problems with amrecover

2001-10-18 Thread Jens Rohde

Hi

I'm stuck! - I've tried to get amrecover to work. There's no problem in
selecting host, disk and files to recover, but when I try to do the actual
recover I get the following error:

amrecover extract

Extracting files using tape drive /dev/nst1 on host devel.
The following tapes are needed: EOS-011
EOS-012

Restoring files into directory /tmp
Continue? [Y/n]: y

Load tape EOS-011 now
Continue? [Y/n]: y
EOF, check amidxtaped.debug file on devel.
amrecover: short block 0 bytes
UNKNOWN file
amrecover: Can't read file header
extract_list - child returned non-zero status: 1
Continue? [Y/n]:

The debug file contains:

amidxtaped: debug 1 pid 3112 ruid 1028 euid 1028 start time Thu Oct 18
11:17:09 2001
amidxtaped: version 2.4.2
 SECURITY USER root
bsd security: remote host afs1.eos user root local user amanda
amandahosts security check passed
 6
amrestore_nargs=6
 -h
 -p
 /dev/nst1
 svabonius.eos.dk
 ^/etc$
 20011017
Ready to execv amrestore with:
path = /afs/eos.dk/sw/pack/amanda-2.4.2/sbin/amrestore
argv[0] = amrestore
argv[1] = -h
argv[2] = -p
argv[3] = /dev/nst1
argv[4] = svabonius.eos.dk
argv[5] = ^/etc$
argv[6] = 20011017
amrestore: could not open tape /dev/nst1: Permission denied
amidxtaped: amrestore terminated normally with status: 2
Rewinding tape: no tape online
amidxtaped: pid 3112 finish time Thu Oct 18 11:17:09 2001

I've searched the mail-list archives but didn't find anything that applied
to my problem (or at least I don't think so :) ).

I have no problems with restoring files using mt and dd on the same
tape/tape drive, so it is functioning.

The server is running RedHat Linux 7.0, and I've tried both amanda 2.4.2
and 2.4.2p2. Same result.

So what do I do wrong here?

-- 
Jens Rohde, System Administrator
---
Eastfork Object Space (EOS), Margrethepladsen 3, 8000  Aarhus C, Denmark
Tel: +45 8732 8787 / Fax: +45 8732 8788




Re: Problems with amrecover

2001-10-18 Thread Bernhard R. Erdmann

On Thu, Oct 18, 2001 at 12:05:46PM +0200, Jens Rohde wrote:
 Hi
 
 I'm stuck! - I've tried to get amrecover to work. There's no problem in
 selecting host, disk and files to recover, but when I try to do the actual
 recover I get the following error:
 
 amrecover extract
 
 Extracting files using tape drive /dev/nst1 on host devel.
 The following tapes are needed: EOS-011
 EOS-012
 
 Restoring files into directory /tmp
 Continue? [Y/n]: y
 
 Load tape EOS-011 now
 Continue? [Y/n]: y
 EOF, check amidxtaped.debug file on devel.
 amrecover: short block 0 bytes
 UNKNOWN file
 amrecover: Can't read file header
 extract_list - child returned non-zero status: 1
 Continue? [Y/n]:
 
 The debug file contains:
 
 amidxtaped: debug 1 pid 3112 ruid 1028 euid 1028 start time Thu Oct 18
 11:17:09 2001
 amidxtaped: version 2.4.2
  SECURITY USER root
 bsd security: remote host afs1.eos user root local user amanda
 amandahosts security check passed
  6
 amrestore_nargs=6
  -h
  -p
  /dev/nst1
  svabonius.eos.dk
  ^/etc$
  20011017
 Ready to execv amrestore with:
 path = /afs/eos.dk/sw/pack/amanda-2.4.2/sbin/amrestore
 argv[0] = amrestore
 argv[1] = -h
 argv[2] = -p
 argv[3] = /dev/nst1
 argv[4] = svabonius.eos.dk
 argv[5] = ^/etc$
 argv[6] = 20011017
 amrestore: could not open tape /dev/nst1: Permission denied

^ 

Here's the error. Please look at remote host afs1.eos user root local
user amanda.

Maybe you start amidxtaped as user amanda instead of root. Check
/etc/inetd.conf or /etc/xinetd*


 amidxtaped: amrestore terminated normally with status: 2
 Rewinding tape: no tape online
 amidxtaped: pid 3112 finish time Thu Oct 18 11:17:09 2001
 
 I've searched the mail-list archives but didn't find anything that applied
 to my problem (or at least I don't think so :) ).
 
 I have no problems with restoring files using mt and dd on the same
 tape/tape drive, so it is functioning.
 
 The server is running RedHat Linux 7.0, and I've tried both amanda 2.4.2
 and 2.4.2p2. Same result.
 
 So what do I do wrong here?
 
 -- 
 Jens Rohde, System Administrator
 ---
 Eastfork Object Space (EOS), Margrethepladsen 3, 8000  Aarhus C, Denmark
 Tel: +45 8732 8787 / Fax: +45 8732 8788
 
 



Quantum SuperDLT1 tapetype

2001-10-18 Thread Fernyhough Mark

Hi

I have just run tapetype on Quantum SuperDLT1 tape (SPARC Solaris8)

tapetype -e 110g -f /dev/rmt/0bn -t SuperDLT1 yeilds

define tapetype SuperDLT1 {
comment blar blar
length  96868   mbytes
filemark0   kbytes
speed   9142kps
}

Do these figures look right especially the filemark entry ?

Cheers

Mark

-
Dr Mark Fernyhough, IT Systems Engineer, Enterprise  Legacy Systems.
Thales Underwater Systems UK, Ocean House, Templecombe, Somerset, BA8 0DH.
 
Email: [EMAIL PROTECTED]   
Tel: 01963 372696
Fax:01963 373008

-


This email and any attachments are confidential to the intended recipient
and may also be privileged. If you are not the intended recipient please
delete it from your system and notify Thales Underwater Systems on +44 1963
370 551. You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.



Problem with stopped backup

2001-10-18 Thread Bill Delphenich

I seem to have a backup that is stopped, but I don't know how to read 
the status report on it. I have included it below.

This backup started last night after midnight and seems to be still 
going. However, the 40.96% dumped number has stayed the same for over an 
hour now. Can someone help me decipher this status report. Also, if it 
is indeed stopped, why did it stop and how do I kill it?

Thanks for any assistance.




Using /usr/adm/amanda/DailySet1/amdump from Thu Oct 18 00:45:00 EDT 2001

coltrane.krjda.com:/home 1 7380096k finished (1:29:28)
travis.krjda.com:/home   010647688k dumping to tape 
(1:29:28)

SUMMARY  part real estimated
  size  size
partition   :   2
estimated   :   2   18017165k
failed  :   0  0k   (  0.00%)
wait for dumping:   0  0k   (  0.00%)
dumping to tape :   1   10647688k   ( 59.10%)
dumping :   00k0k (  0.00%) (  0.00%)
dumped  :   1  7380096k  7369477k (100.14%) ( 40.96%)
wait for writing:   00k0k (  0.00%) (  0.00%)
writing to tape :   00k0k (  0.00%) (  0.00%)
failed to tape  :   00k0k (  0.00%) (  0.00%)
taped   :   1  7380096k  7369477k (100.14%) ( 40.96%)
3 dumpers idle  : not-idle
taper writing, tapeq: 0
network free kps:  970
holding space   :   719800k (100.00%)
 dumper0 busy   :  0:41:30  (100.00%)
   taper busy   :  0:41:30  (100.00%)
 0 dumpers busy :  0:00:00  (  0.00%)
 1 dumper busy  :  0:41:30  (100.00%)not-idle:  0:41:30  
(100.00%)





Re: changer problem

2001-10-18 Thread John Rowan Littell

I was having problems similar to this (though I can't remember the
specific error messages).  I'm using chg-zd-mtx on Solaris 8 with
an Overland LoaderXpress (DLT).  What solved the problem for me
was making sure that the changer config file has _all_ of the
variables specified, even if they seemed to be default values.
The chg-zd-mtx script doesn't seem to set default values, and gives
weird errors if they're not there.

  --rowan

Lo, Donnie Emeson and the coffee pot sang in unison:
 I'm having trouble with amanda 2.4.2p2 and a new changer, a Sun L20 with
 20 slots and one DLT8000.
 
 This changer has a barcode reader, but I'm not using it.  (I don't have
 a label maker and don't really want to bother.)  Perhaps this is what's
 causing my problems...
 
 I have chg-zd-mtx working, though I had to make some minor changes.
 
 The problem is amlabel and amcheck.  Both get similar errors.  Amlabel
 goes ahead and loads the first tape and then gives me:
 amlabel: could not load slot current: badly formed result from changer: 
MT=/usr/bin/mt
 
 Amcheck is fine except for this error:
 amcheck-server: could not get changer info: badly formed result from changer: 
MT=/usr/bin/mt
[snip]

-- 
John Rowan Littell
Systems Administrator
Earlham College Computing Services

 PGP signature


Re: Problem with stopped backup

2001-10-18 Thread Joshua Baker-LePain

On Thu, 18 Oct 2001 at 8:03am, Bill Delphenich wrote

 This backup started last night after midnight and seems to be still
 going. However, the 40.96% dumped number has stayed the same for over an
 hour now. Can someone help me decipher this status report. Also, if it
 is indeed stopped, why did it stop and how do I kill it?

 Using /usr/adm/amanda/DailySet1/amdump from Thu Oct 18 00:45:00 EDT 2001

 coltrane.krjda.com:/home 1 7380096k finished (1:29:28)
 travis.krjda.com:/home   010647688k dumping to tape
 (1:29:28)

 SUMMARY  part real estimated
   size  size
 partition   :   2
 estimated   :   2   18017165k
 failed  :   0  0k   (  0.00%)
 wait for dumping:   0  0k   (  0.00%)
 dumping to tape :   1   10647688k   ( 59.10%)
 dumping :   00k0k (  0.00%) (  0.00%)
 dumped  :   1  7380096k  7369477k (100.14%) ( 40.96%)
 wait for writing:   00k0k (  0.00%) (  0.00%)
 writing to tape :   00k0k (  0.00%) (  0.00%)
 failed to tape  :   00k0k (  0.00%) (  0.00%)
 taped   :   1  7380096k  7369477k (100.14%) ( 40.96%)
 3 dumpers idle  : not-idle
 taper writing, tapeq: 0
 network free kps:  970
 holding space   :   719800k (100.00%)
  dumper0 busy   :  0:41:30  (100.00%)
taper busy   :  0:41:30  (100.00%)
  0 dumpers busy :  0:00:00  (  0.00%)
  1 dumper busy  :  0:41:30  (100.00%)not-idle:  0:41:30
 (100.00%)

/home on coltrane has been taped -- it finished at 1:30.  So it's number
shouldn't be changing.  /home on travis is currently being dumped to tape.
You should see it's number changing (along with tape activity).

You don't have enough holding space for either of these partitions, so all
dumps are going straight to tape.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University




Re: changer problem

2001-10-18 Thread Chamby

Hello Donnie !!!

I have the same hardware (StorEdge L20)

I was not able to set amanda with this L20

May i see your configs files (amanda and chg-zd-mtx)

thank's in advance !!!

P.S. I can try it and see if a have the same problem than you !!!

- Original Message -
From: Donnie Emeson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 18, 2001 12:16 AM
Subject: changer problem


 I'm having trouble with amanda 2.4.2p2 and a new changer, a Sun L20 with
 20 slots and one DLT8000.

 This changer has a barcode reader, but I'm not using it.  (I don't have
 a label maker and don't really want to bother.)  Perhaps this is what's
 causing my problems...

 I have chg-zd-mtx working, though I had to make some minor changes.

 The problem is amlabel and amcheck.  Both get similar errors.  Amlabel
 goes ahead and loads the first tape and then gives me:
 amlabel: could not load slot current: badly formed result from changer:
MT=/usr/bin/mt

 Amcheck is fine except for this error:
 amcheck-server: could not get changer info: badly formed result from
changer: MT=/usr/bin/mt


 # cat /tmp/amanda/amlabel.20011017213837.debug
 amlabel: debug 1 pid 27110 ruid 43382 euid 43382 start time Wed Oct 17
21:38:37 2001
 changer: got exit: 0 str: MT=/usr/bin/mt
 could not load slot current: badly formed result from changer:
MT=/usr/bin/mt
 amlabel: pid 27110 finish time Wed Oct 17 21:40:07 2001


 # cat /tmp/amanda/amcheck.20011017213225.debug
 amcheck: debug 1 pid 27006 ruid 43382 euid 0 start time Wed Oct 17
21:32:25 2001
 amcheck: dgram_bind: socket bound to 0.0.0.0.711
 changer: got exit: 0 str: MT=/usr/bin/mt
 changer_query: changer return was
 could not get changer info: badly formed result from changer:
MT=/usr/bin/mt
 amcheck-server: pid 27007 finish time Wed Oct 17 21:32:25 2001
 amcheck: pid 27006 finish time Wed Oct 17 21:32:25 2001

 --donnie





Amanda 2.4.2p2, Solaris 8, amandad hangup

2001-10-18 Thread Brian Cuttler


Hello,

I am trying to run amanda 2.4.2p2 on Solaris 8 and am receiving
the following in /var/adm/messages

Oct 18 09:22:28 c110 inetd[186]: [ID 858011 daemon.warning] 
/usr/local/libexec/amandad: Hangup

Unlike the messages from May (30029 and related) I am not seeing
a secondary message amanda/udp server failing (looping), service terminated

and I have checked with our security manager, we are not running
BSM security modules on this system.

I should also tell you that we are runing the amanda server on Solaris 7
as bin and installing the amanda client on Solaris 8 built for user
amanda.

We seem to be finding/triggering amanda services from inetd correctly
or we'd have different messages in /var/adm/messages...

There is no output, no creation of /tmp/amanda/
Using the run-amanda wrapper as suggested by Dan Lorenzini to run
amanda as root in inetd.conf but as local user via the wrapper's
su command produces the same result, .../amandad: Hangup

Come to think of it I should also state that the amanda server 
is 2.4.1p1. Its is compattible with the 2.4.2p2 client ?

thanks,

Brian

---
   Brian R Cuttler [EMAIL PROTECTED]
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773




Still trying to get gzip/gpg

2001-10-18 Thread ahall

Hello,

I am still trying to get gzip/gpg working.  I did not receive any replies
from my last two mails, so let me try again not so broad.

If someone might be able to answer this, that would be awesome:

As I understand the process the data should be written to tape with gzip,
not dump.  But what is weird is that it appears that amanda is attempting
to backup the data with dump, but restore it with gzip.

sendbackup: start [localhost:sda1 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/var/backups/bin/gzip -dc |/sbin/restore
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end


Why is the BACKUP command /sbin/dump, and the RECOVER_CMD gzip?  How can I
change this?


BTW, When I get this all figured out I will write a doc covering exactly
how to do this.


TIA.

Andrew




Re: New to Amanda

2001-10-18 Thread Joshua Baker-LePain

On Thu, 18 Oct 2001 at 3:45pm, XiScO wrote

 I'd like to know if Amanda can do backup to HD in spite of Tape. Is
 there any user manual??

Look around for info on the tapeio branch of amanda.  You'll need to pull
it out of CVS, and it's still beta, but people are using it.

 [root@marjal02 amanda-2.4.2p2]# ./configure
.
 configure: error: *** --with-user=USER is missing

 Any idea??, thanks.

RTFM.  You need to create a user for amanda, and tell configure the
username and group of that user.

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University




Re: tapecycle off by 1?

2001-10-18 Thread Bernhard R. Erdmann

 I've been waiting to reach the 135th tape.  For weeks and weeks now, I see
 The next 6 tapes Amanda expects to used are: a new tape, a new tape, a new
 tape, a new tape, a new tape, a new tape.  I've been waiting for it to say
 it expects tape #1 again.
 
 Today was suppose to be the big day.
 
 But here's what the report said: These dumps were to tapes love129,
 love130, love131.  The next 6 tapes Amanda expects to used are: a new tape,
 love132, love133, love134, love1, love2.
 
 My question is how come it's not expecting love135, after all that's what I
 have specified in amanda.conf.  Kinda looks like a x-1 error.  But I'm
 sure I'm just missing something, and hoping the list can help me...


Probably you missed (skipped) a tape someday. Check your tapelist if
every tape love1-love131 was used.



Re: Quantum SuperDLT1 tapetype

2001-10-18 Thread Anthony A. D. Talltree

Remember that storage vendors usually redefine meg/gig to be
1000/100 instead of the traditional multiples of 1024.  Taking that
into account, 96868 real-world meg would be 101573 storage-vendor meg.



Re: multiple emails from list

2001-10-18 Thread Dan Wilder

On Thu, Oct 18, 2001 at 07:23:07PM -0400, Chris Dahn wrote:
   I keep getting emails from the list that I've already received. I probably 
 receive them twice or three times. Is this happening to anyone else?
 
 -Chris
 

Not me.

Keep the multiple copies and compare closely the Received headers.
You're looking for small differences between them.  These will
indicate at what machine the duplicates are originating.

The Received headers are in reverse chronological order,
newest first.  The oldest headers will be identical, and
above some point in the headers, all headers will differ
between the seemingly duplicate emails.  The lowest header
with differences will give a clue to where the duplication
is happening.

-- 
-
 Dan Wilder [EMAIL PROTECTED]   Technical Manager  Editor
 SSC, Inc. P.O. Box 55549   Phone:  206-782-8808
 Seattle, WA  98155-0549URL http://embedded.linuxjournal.com/
-