Messages in this thread | | | Date | Tue, 11 Mar 1997 02:09:38 +0200 | From | (Oskar Pearson) | Subject | Re: 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
| |