lkml.org 
[lkml]   [1997]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: ext2 errors with 2.0.31
From
Date
toreo-mlist  <toreo-mlist@tihlde.hist.no> writes:

> Running dmesg tells me:
> EXT2-fs warning (device 03:04): ext2_free_blocks: bit already cleared for block 508248
> EXT2-fs warning (device 03:04): ext2_free_blocks: bit already cleared for block 508260
> EXT2-fs warning (device 03:04): empty_dir: bad directory (dir #42990) - no `.' or `..'

> I never had problems with 2.0.31 (or any other kernel) until
> recently[1]. What could this be? Hardware failure?

That looks similar to the problem I have had from at least 2.0.29. It's
happened to me only with IDE (/dev/hda and /dev/hdc) and manifested on
my system as blocks of 4 inodes getting completely zeroed.

Aug 20 14:20:11 altair kernel: EXT2-fs warning (device 03:02): ext2_free_inode: bit already cleared for inode 181586
Aug 20 14:20:12 altair kernel: EXT2-fs warning (device 03:02): ext2_free_inode: bit already cleared for inode 181587
Aug 20 14:24:38 altair kernel: EXT2-fs warning (device 03:02): ext2_free_inode: bit already cleared for inode 181586
Aug 20 14:24:38 altair kernel: EXT2-fs warning (device 03:02): ext2_free_inode: bit already cleared for inode 181587

\
 
 \ /
  Last update: 2005-03-22 13:40    [from the cache]
©2003-2011 Jasper Spaans