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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
