mouse@mcgill-vision.UUCP (der Mouse) (08/15/85)
Help! I'm going nuts! We have a VAX-11/750 running 4.2bsd and we
recently got a DR11W card as an interface to a small machine with a
DR11W emulator (looks like a DR11W to another DR11W). I cheerfully
started in on the driver for it (has to be a custom driver because some
ad hoc protocol has to be done at the driver level to get speed).
Trouble showed up shortly after I got it appearing to work. After about
30 seconds of exerciser transfers, someone (presumably the driver)
corrupts something and we get messages like (usually inode 2):
bad dir entry ino 2 offset 0: mangled entry
bad dir entry ino 2 offset 512: mangled entry
bad dir entry ino 2 offset 1024: mangled entry
bad dir entry ino 2 offset 1536: mangled entry
bad dir entry ino 2 offset 2048: mangled entry
Shortly thereafter, the system panics (not consistently the same
panic) and we crash. Once it managed to write the damaged directory
back to disk first and we had to pull the partition off backups.
Is there a working DR11W driver out there I could look at for
ideas? Or does anyone have any other suggestions?
Pretty please??
--
der Mouse
System hacker and general troublemaker
CVaRL, McGill University
Hacker: One responsible for destroying /
Wizard: One responsible for recovering it afterwardchris@umcp-cs.UUCP (Chris Torek) (08/18/85)
>... After about 30 seconds of exerciser transfers, someone >(presumably the driver) corrupts something and we get messages >like (usually inode 2): > >bad dir entry ino 2 offset 0: mangled entry The most common (?) cause of those symptoms is something tromping on the buffer cache. (I managed to do this once in the course of writing the mass driver, by using geteblk(10240); nothing in the kernel checked the size of the request. I fixed *that* too....) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 4251) UUCP: seismo!umcp-cs!chris CSNet: chris@umcp-cs ARPA: chris@maryland