Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Sep 1995 09:45:24 -0500 (CDT)
From:      Bob Willcox <bob@luke.pmr.com>
To:        gary@palmer.demon.co.uk (Gary Palmer)
Cc:        asami@cs.berkeley.edu, freebsd-ports@freefall.freebsd.org
Subject:   Re: Using amanda from ports
Message-ID:  <199509201445.JAA26315@luke.pmr.com>
In-Reply-To: <520.811603967@palmer.demon.co.uk> from "Gary Palmer" at Sep 20, 95 02:32:47 pm

next in thread | previous in thread | raw e-mail | index | archive | help
Gary Palmer wrote:
> 
> In message <199509201001.DAA04750@silvia.HIP.Berkeley.EDU>, Satoshi Asami write
> s:
> > * Well, Think I'll have to give up my attempts to use amanda for now.
> > * I did finally get it to run but it caused my system to spontaneously
> > * reboot while it was running.  I have used up more time than I can
> > * afford on it right now, perhaps next time I get to trying it I will
> > * have better luck.  Too bad, it looks quite useful...    :-(
> 
> >Sorry to hear that. :<
> 
> There was a problem in the SCSI tape code (probably in 2.0.5R also, as
> the bug was noticed (by me at least) after the disk was pressed). For
> the life of me I can't remember what it was tho. I think it was a
> timeout problem, not a crash'n'burn problem tho.
> 
> ``spontaneously reboot'' == kernel stack overflow (if there wasn't a
> panic message). Details of your problem should be addressed to the
> relevant list (freebsd-current or freebsd-stable depending on your
> version - ports certainly isn't it). A dmesg showing hardware involved
> would certainly be helpful in debugging this problem.

Well, here is the (I believe) relavent hardware config:

P100 CPU, Triton chipset, 256kb L2 cache (write-back), 32mb RAM
    2 NCR 53C810 based SCSI adapters,
    1 Adaptec AHA-3940 SCSI adapter,
    1 Digital DC21040 Ethernet adapter.

I am running 2.1-stable as of 9/15 with the -current level of the
Adaptec device driver (per the recommendation of Justin Gibbs).

Here are some highlights of the SCSI probe output:

    (ncr0:0:0): "MICROP 2217-15MZ1001901 HZ30" type 0 fixed SCSI 2
    sd0(ncr0:0:0): Direct-Access 
    sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
    (ncr0:3:0): "TOSHIBA CD-ROM XM-3401TA 2873" type 5 removable SCSI 2
    cd0(ncr0:3:0): CD-ROM 
    cd0(ncr0:3:0): 250ns (4 Mb/sec) offset 8.
    cd0(ncr0:3:0): NOT READY asc:3a,0 Medium not present
    (ncr0:4:0): "TOSHIBA CD-ROM XM-3401TA 0283" type 5 removable SCSI 2
    cd1(ncr0:4:0): CD-ROM 
    cd1(ncr0:4:0): 250ns (4 Mb/sec) offset 8.
    cd1(ncr0:4:0): NOT READY asc:3a,0 Medium not present
    (ncr0:5:0): "WANGTEK 5525ES SCSI REV7 3R2" type 1 removable SCSI 1
    st0(ncr0:5:0): Sequential-Access st0: Wangtek 5525ES is a known rogue
    density code 0x0,  drive empty
    (ncr0:6:0): "EXABYTE EXB-8200 2687" type 1 removable SCSI 1
    st1(ncr0:6:0): Sequential-Access density code 0x0,  drive empty
    ncr1 <ncr 53c810 scsi> rev 2 int a irq 12 on pci0:18
    ncr1: restart (scsi reset).
    ncr1 scanning for targets 0..6 (V2 pl22 95/07/07)
    ncr1 waiting for scsi devices to settle
    (ncr1:0:0): "SEAGATE ST12550N 0013" type 0 fixed SCSI 2
    sd1(ncr1:0:0): Direct-Access 
    sd1(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
    (ncr1:1:0): "HP C2247-300 0BE4" type 0 fixed SCSI 2
    sd2(ncr1:1:0): Direct-Access 
    sd2(ncr1:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
    (ncr1:2:0): "DEC DSP3105S 386C" type 0 fixed SCSI 2
    sd3(ncr1:2:0): Direct-Access 
    sd3(ncr1:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
    (ncr1:3:0): "DEC DSP3107LS 441C" type 0 fixed SCSI 2
    sd4(ncr1:3:0): Direct-Access 
    sd4(ncr1:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
    (ncr1:4:0): "DEC DSP3210S 441C" type 0 fixed SCSI 2
    sd5(ncr1:4:0): Direct-Access 
    sd5(ncr1:4:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8.
    ahc0 <Adaptec 3940 SCSI host adapter> rev 0 int a irq 14 on pci1:4
    ahc0: 3940 Channel A, SCSI Id=7, aic7870, 16 SCBs
    ahc0 waiting for scsi devices to settle
    ahc0: target 0 Tagged Queuing Device
    (ahc0:0:0): "DEC DSP3210S 441C" type 0 fixed SCSI 2
    sd6(ahc0:0:0): Direct-Access 2049MB (4197520 512 byte sectors)
    ahc0: target 1 Tagged Queuing Device
    (ahc0:1:0): "DEC DSP3105S 386C" type 0 fixed SCSI 2
    sd7(ahc0:1:0): Direct-Access 1001MB (2050860 512 byte sectors)
    ahc0: target 2 Tagged Queuing Device
    (ahc0:2:0): "DEC DSP3105S 386C" type 0 fixed SCSI 2
    sd8(ahc0:2:0): Direct-Access 1001MB (2050860 512 byte sectors)
    ahc0: target 3 Tagged Queuing Device
    (ahc0:3:0): "DEC DSP3107LS 441C" type 0 fixed SCSI 2
    sd9(ahc0:3:0): Direct-Access 1021MB (2091144 512 byte sectors)
    ahc1 <Adaptec 3940 SCSI host adapter> rev 0 int a irq 15 on pci1:5
    ahc1: 3940 Channel B, SCSI Id=7, aic7870, 16 SCBs
    ahc1 waiting for scsi devices to settle
    ahc1: target 0 Tagged Queuing Device
    (ahc1:0:0): "DEC DSP3210S 435E" type 0 fixed SCSI 2
    sd10(ahc1:0:0): Direct-Access 2049MB (4197520 512 byte sectors)
    ahc1: target 2 Tagged Queuing Device
    (ahc1:2:0): "DEC DSP3105S 386C" type 0 fixed SCSI 2
    sd11(ahc1:2:0): Direct-Access 1001MB (2050860 512 byte sectors)
    ahc1: target 3 Tagged Queuing Device
    (ahc1:3:0): "DEC DSP3210S 441C" type 0 fixed SCSI 2
    sd12(ahc1:3:0): Direct-Access 2049MB (4197520 512 byte sectors)
    ahc1: target 4 Tagged Queuing Device
    (ahc1:4:0): "SEAGATE ST12550N 0014" type 0 fixed SCSI 2
    sd13(ahc1:4:0): Direct-Access 2040MB (4178874 512 byte sectors)

At the time of the reboot a filesystem on sd2 was being dumped to
the holding disk on sd5.  There was no tape activity at the time
(though a previous filesystem had recently been copied from the
holding disk to the tape.  The tape drive being used is an Exabyte
8200 (st1).  The system is our news and file server so there was
other activity going on at the same time.

Note that this was an attempt to dump the local filesystems only.
There were no other systems involved.

> 
> > * I'd certainly like to hear from folks that are successfully using
> > * it...
> 
> About 6 machines are dumped to a 9Gb Exabyte tape drive every night at
> Walnut Creek (aka cdrom.com). This includes freefall.FreeBSD.ORG, so I
> sincerely hope it works! (I have to say, I do know that it works - I
> am on the alias that gets the dump reports every night).
> 
> >I'm sure there is somebody using it successfully, maybe you can ask in 
> >the newsgroup or "hackers"?  The "ports" list is for porters, so
> >amanda users may not be listening here....
> 
> This isn't a generic Amanda problem I think. I can't think of HOW
> amanda can force a spontaneous reboot, as it doesn't do anything low
> level enough to worry me (all the low level stuff is done through
> `dump(8)' and then piped over TCP/IP to a listener which dumps it to
> the tape).

I believe that as-well, however I can (and do) backup this entire
system to the same tape drive simply using dump(8) without this
problem.  (I have experienced ``Queue Full'' error messages from
the adaptec device driver - this is why Justin suggested I update
it to current - I have not seen that problem since then, though I
haven't been running the new driver for very long yet.)

> 
> Gary
> 
> P.S. Sorry if I'm hopping on the end of this discussion, I don't
> remember seeing previous mails about this (I could have done, I've had
> a lot on my mind the last few days).
> 


-- 
Bob Willcox
bob@luke.pmr.com (or obiwan%bob@uunet.uu.net)
Austin, TX



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199509201445.JAA26315>