lkml.org 
[lkml]   [1997]   [Mar]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Inode Corruption
Timothy Peters writes:

I know this is a little late.

> I am getting inode corruption on an md partition when accessing over NFS
>
> I have applied the fs-22-jan-1997 patch but I am still getting
> corruption
>
> Jan 29 16:05:20 babbage kernel: EXT2-fs warning (device 09:00):
> ext2_free_inode: bit already cleared for inode 275578
> Jan 29 16:05:20 babbage kernel: EXT2-fs warning (device 09:00):
> ext2_free_blocks: bit already cleared for block 1098501
> Jan 29 16:05:20 babbage last message repeated 3 times
> Jan 29 16:05:20 babbage kernel: EXT2-fs warning (device 09:00):
> ext2_free_inode: bit already cleared for inode 275580
>
> Jan 29 16:05:20 babbage kernel: EXT2-fs warning (device 09:00): ext2_free_inode: bit already cleared for inode 275578
> Jan 29 16:05:20 babbage kernel: EXT2-fs warning (device 09:00): ext2_free_blocks: bit already cleared for block 1098501
> Jan 29 16:05:20 babbage last message repeated 3 times
> Jan 29 16:05:20 babbage kernel: EXT2-fs warning (device 09:00): ext2_free_inode: bit already cleared for inode 275580

This seems like the same problem that we had with an unsupported UMC IDE
controller doing lots and lots of "open, write, close" functions.

I didn't believe that it would work, but changing the IDE controller fixed
the problem. Try one of the supported IDE chipsets and see what happens.

Oskar

\
 
 \ /
  Last update: 2005-03-22 13:39    [W:0.043 / U:0.372 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site