[208] in linux-scsi channel archive
Re: SCSI ext2 problems
daemon@ATHENA.MIT.EDU (Lutz Pressler)
Wed May 24 16:13:54 1995
Date: Wed, 24 May 1995 20:42:40 +0200 (MEZ)
From: Lutz Pressler <Lutz.Pressler@Unix.AMS.Medizin.Uni-Goettingen.DE>
To: Michael Weller <eowmob@exp-math.uni-essen.de>
cc: Peter K <pko@paradigm.co.za>, linux-kernel@vger.rutgers.edu,
linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.3.89.9505241736.I63928-0100000@werner.exp-math.uni-essen.de>
Hello,
On Wed, 24 May 1995, Michael Weller wrote:
> > From: Peter K <pko@paradigm.co.za>
> > To: linux-kernel <linux-kernel@vger.rutgers.edu>
> > Subject: SCSI ext2 problems
> >
> > Hi guys.
> >
> > Seem this box is out to get me. No hassles until 1.2.8 and then repeated
> > crashes reporting (inter alia)
> > Kernel panic: EXT2-fs panic (device 8/2): ext2_read_inode:
> > unable to read i-node block - inode=6127, block=73743
>
> [...]
>
> I didn't understand exactly what you mean.. Ok you have this problems
> with 1.2.8. and had none b4. However, when you now switch back to an older
> do you still get problems (did you try) or does it work.
>
We are experiences similar problems here (same type of ext2 errors) on a
PCI system with NCR53c810 SCSI controller (Digital and Maxtor disks)
which is an NFS server.
About 5 lock ups since installing 1.2.8 (hmm, 3 weeks now?). Never had any
hangs since the very early version of the NCR dricver (problems in
combination with graphics card in those days).
So I _suspect_ some change in 1.2.8 triggers this - don't know what.
There is the remote possibility of a hardware fault, of cause. But if
others report this, too...
Have a nice day,
Lutz
--
Lutz Pre"sler <URL:http://www.AMS.Medizin.Uni-Goettingen.DE/~lpressl1/>
Systemverwaltung -- Abt. Medizinische Statistik, Universit"at G"ottingen
Humboldtallee 32, D-37073 G"ottingen, Tel.: +49(0551) 39-4956 FAX: -4995
<Lutz.Pressler@AMS.Medizin.Uni-Goettingen.DE> [PGP-key:WWW&keys.] IRC:lp
