Date: Mon, 23 Aug 1999 09:18:33 -0500 (CDT) From: David Scheidt <dscheidt@enteract.com> To: Stephen McKay <syssgm@detir.qld.gov.au> Cc: freebsd-current@freebsd.org Subject: Re: Softupdates reliability? Message-ID: <Pine.NEB.3.96.990823090919.6729A-100000@shell-1.enteract.com> In-Reply-To: <199908230659.QAA08609@nymph.detir.qld.gov.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Aug 1999, Stephen McKay wrote: > I was extracting from the Exabyte to the DDRS disk while applying a CTM > update from that disk against one of the DCAS disks when it crashed. The > Exabyte went wonky (took about 6 goes to get the tape ejected) and the > rest of the disk system locked up. The SCSI adapter was so confused I > had to power down. > > When it recovered, there was an "UNEXPECTED SOFT UPDATE INCONSISTENCY" > which turned out to be a referenced but unallocated inode, and two zero size > directories. In all, a couple dozen files ended up in lost+found. I had this happen a couple times in 3.-2 stable. I tried to load a buggy kernel module, and hosed a cylinder group. As near as I could tell, the kernel module was writing to memory at random, and corrupted the buffer chain. I couldn't quite reproduce this enough to get a good handle on exactly what was going on, though. > If many other people have survived sudden power loss or similar no-sync type > crashes, I'll be happy to believe option 1 caused my problem. If not, then > perhaps softupdates still has incomplete handling of dependencies. Of course, > if it is option 1, I'm keen to know what's wrong with the current driver! I have survived a number of power loss crashes, with no problems. I tend to suspect the SCSI driver did something bad. David Scheidt 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?Pine.NEB.3.96.990823090919.6729A-100000>