Date: Fri, 26 Feb 1999 12:50:18 +0100 From: User Girgen <girgen@partitur.se> To: Warner Losh <imp@harmony.village.org> Cc: freebsd-stable@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: panic: aha0 Invalid CCB or SG list Message-ID: <36D68A7A.CC8FEF98@partitur.se> References: <36D4B092.8B076D55@partitur.se> <199902252308.QAA04402@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote: > > In message <36D4B092.8B076D55@partitur.se> Palle Girgensohn writes: > : I've seen three crashes in the last couple of weeks, with a server > : box that's been running stable as a rock for two years, at least. It > : has an adaptec 2940UW with six disks, and an adaptec 1542CP that's > : connected to a seagate travan tape driver. > > OK. This card is known to be good. At least I've not had any > problems with it. > > : It's running STABLE-3.1 from Feb 19 1999, and since the last > : upgrade, I've seen three crashes, all related to dumping to > : tape. Since I got no info on what happened, I decided to sit down > : with the machine, run a backup sequence to tape, and wait for it to > : possibly crash. After 90 minutes, I was about to give up when > : suddenly, poof: > : panic: aha0 Invalid CCB or SG list. > : > : So, it's probably the 1540 driver (or hardware)? > > Ah. OK. I'm not doing tape stuff on my machine. How fast is that > seagate tr-4 that you are doing? It claims it can do 600 Kbytes/s, but most often it's around 550 when writing large "prepared" dump files. > > : Can anybody shed some light on what to do? Is it software? That's my > : guess, since the machine never ONCE has crashed until the upgrade to > : 3.x. I had one crash when running current form beginning of January > : (soon after moving to 3.x), and now theese three in a week. The 1540 > : has been in the machine for about six months. > > Chances are really good that this is software. The invalid ccb or sg > list is due to either a race condition or something taht corrupts > these things. > > : If there's anything I can do to help debug I'll do it, but device > : drivers are a little above my level of expertise. > > If you can wait a day or three, I might be able to find something that > will help. However, I don't have a tape drive right now to test it > with. I'll see what I can beg, borrow or steal. > > Warner I can wait, no problem. I don't think I have a choice, anyway ;-) It seems to be working better when not utilizing the CPU 100% when writing to tape. As I mentioned, I'm using amanda to dump both server and a bunch of workstations. Amanda does gzip on the the dumps before writing them to a scratch disk on the tape host, from where they are written to tape. Since the backup client performs the gzip, I don't see crashes every night, but only when a lot of the dumps scheduled are from the tape host itself (that is, when the tape host is gzipping away att 100% CPU, while at the same writing to tape). Thanks for helping! /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36D68A7A.CC8FEF98>