[1007] in linux-scsi channel archive
more scsi errors :(
daemon@ATHENA.MIT.EDU (Jon Lewis)
Sun Nov 24 00:17:38 1996
Date: Sun, 24 Nov 1996 00:14:57 -0500 (EST)
From: Jon Lewis <jlewis@inorganic5.fdt.net>
Reply-To: Jon Lewis <jlewis@inorganic5.fdt.net>
To: Gerard Roudier <groudier@club-internet.fr>
cc: ncr53c810@colorado.edu,
Linux SCSI Mailing List <linux-scsi@vger.rutgers.edu>
In-Reply-To: <Pine.LNX.3.91.961123220749.111A-100000@localhost>
In my news server running 2.0.25 with a pair of NCR 810's using the BSD
ported driver, I just noticed these in the kernel message buffer.
EXT2-fs error (device 08:31): ext2_find_entry: bad entry in directory
#757318: rec_len % 4 != 0 - offset=1552, inode=3941569338, rec_len=43694,
name_len=16580
EXT2-fs error (device 08:31): ext2_add_entry: bad entry in directory
#757318: rec_len % 4 != 0 - offset=1552, inode=3941569338, rec_len=43694,
name_len=16580
EXT2-fs error (device 08:31): ext2_add_entry: bad entry in directory
#757318: rec_len % 4 != 0 - offset=1552, inode=3941569338, rec_len=43694,
name_len=16580
EXT2-fs error (device 08:31): ext2_find_entry: bad entry in directory
#757318: rec_len % 4 != 0 - offset=1552, inode=3941569338, rec_len=43694,
name_len=16580
The device in question is:
/dev/sdd1 2399101 1788717 590384 75% /var/spool/news/alt
It's the majority of a Micropolis 3243-19MZ Q4D Rev: HT02. I used to get
errors in the news server fairly frequently, so I talked the boss into
blowing a fortune on Granite Digital SCSI cables which are supposed to be
the best (probably just most expensive) cables money can buy. After
installing them, I saw no problems that I can recall...until this.
At this point, the problem is almost definitely not cable related.
Termination is passive on the 810 but active on the other end via a DEC
DSP5300S at the end of this channel. I suppose I could improve things by
removing the card's terminators and put an active terminator on the card's
external connector. Anyone know what kind of terminators Buslogic uses?
I'm getting close to wanting to start over and build a new news server on
wide or ultra SCSI with more spool anyway...if only we had the $$.
I'm a bit confused by the messages...especially inode=3941569338. I have
a lot of inodes...but not that many.
Filesystem Inodes IUsed IFree %IUsed Mounted on
/dev/sdd1 1748808 186064 1562744 11% /var/spool/news/alt
The syslogd timestamps for the first 3 messages was 09:23:21, and the last
one was 09:25:29. This particular SCSI bus has just the 3243 and the DSP
5300 on it. Other disks are on the other 810. The 3243's have been
historically troublesome for us and have done strange things in the
past (in a different server, one once vanished during or causing a
system hang and would not show up after several warm boots. I had to
power cycle the system for it to be found again)...so I always somewhat
suspect the 3243's when things go wrong. We keep them very well
ventilated...so heat should not be an issue.
Another possiblilty could be interference. The news server shares a
monster 2 motherboard 16 drive capacity case with another system and there
are 2 P90 systems, 3 NCR 810 boards, and 6 scsi disks...but the super
expensive shielded cables are supposed to minimize interference.
I'm open to interpretations of the messages, suggestions, etc. Innd
hasn't complained about the disk yet...but often it will eventually quit
(throttle itself) sometime after one of the spool disks logs errors. At
some point, I'll probably kill innd, umount sdd1, run e2fsck -fy on it,
remount, and restart innd.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______
