I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying
to load the oss driver, which is not too shocking. What was shocking
was the damage done to my filesystem. The automatic fsck failed,
with an UNEXPECTED SOFT UPDATES INCONSISTNCY. PARTIALLY ALLOCATED
INODE I=39684.
Running fsck
On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote:
> I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying
> to load the oss driver, which is not too shocking. What was shocking
> was the damage done to my filesystem. The automatic fsck failed,
> with an UNEXPECTED SOFT U
On Sun, 13 Jun 1999, Bernd Walter wrote:
> On Sat, Jun 12, 1999 at 12:13:43AM -0500, David Scheidt wrote:
> > I had a 3.2 stable (from 30 May 1999)machine panic tonight, trying
> > to load the oss driver, which is not too shocking. What was shocking
> > was the damage done to my filesystem. The
em
:damage as bad as this.
:
:David Scheidt
This smells like a memory corruption problem rather then a softupdates
problem. i.e. that something in the kernel overwrote random kernel
memory which happened to correspond to a filesystem buffer.
There was a buffer corruption bug found
4 matches
Mail list logo