Date: Tue, 13 Jun 1995 23:21:08 +0200 (MET DST) From: wjw@IAEhv.nl (Willem Jan Withagen) To: dufault@hda.com (Peter Dufault) Cc: wjw@IAEhv.nl, questions@freebsd.org Subject: Re: Medium error Message-ID: <199506132121.XAA08095@iaehv.IAEhv.nl> In-Reply-To: <199506132108.RAA13083@hda.com> from "Peter Dufault" at Jun 13, 95 05:08:29 pm
next in thread | previous in thread | raw e-mail | index | archive | help
You ( Peter Dufault ) write: => => Willem Jan Withagen writes: => => (Re-directed to -questions) => => > We're running an ISP site and our newsdisk is giving us a hard time, but => > it's real hard to replace the damn thing at the moment. => > => > What do we have: => > A P90-asus with NCR controller with a quantum 2.1 Empire as sd2. => => Be sure you provide all the information about your installation. In => this case, I need to know which release you are running. Eh, dumb, dumb, dumb. I keep telling this to our users over and over. Boy do I feel stuppid: Running 2.0R with a few minor patches ./i386/conf/files.i386.orig ./i386/pci/ncr.c.orig ./i386/pci/ncrreg.h.orig ./kern/kern_sysctl.c.orig ./kern/vfs_syscalls.c.orig ./netinet/ip_input.c.orig ./netinet/ip_output.c.orig ./netinet/ip_fw.c.orig ./netinet/ip_fw.h.orig ./netinet/raw_ip.c.orig ./netinet/in.h.orig ./sys/malloc.h.orig These we're added by our local FreeBSD guru, the ncr patches even after consults with the NCR author. => > And this baby is generating a medium error on just one location. => > Jun 13 22:19:50 iaehv kernel: sd2(ncr0:2:0): medium error, info = 2817606 (decimal) => => Is this always the same "info" code? Yes, this is the only error spot it reports always this 2817606 => > The funny (??) thing is that this cause I/O errors in INN in serveral spool => > directories. Even after I created a real large file to try and cover the bad => > spot with just-another-file. => > => > So I'm starting to wonder: can the bad spot contain more than just one => > directory which is getting trouble? => => It is probably a single spot. That's what I hoped. But it still doesn't give me any hint as to why I now can not create new files in 6 different directories? And doing a 'touch a' in such a directory immediatly triggers the kernel message. => > But the real serious question: Is there any way of getting this ONE error => > out of the way by just any reasonable method? => => I'll make some suggestions after I see what you're running. You have => more options if you are running 2.05. That's what Guido told me, but we'd want to test-run 2.05 before letting it take a whack at our users. :-) --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506132121.XAA08095>