[lkml]   [2004]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: ext3 on raid5 failure
On Wed, Feb 04, 2004 at 10:24:55AM +0100, Bas Mevissen wrote:
> I've seen this kind of problems on my notebook too. Among others, over
> 600MB of a huge cache directory (from a news reader) was having "funny"
> permissions. Maybe more files were affected. I used fsck.ext3 and
> changed the attributes with chmod.

Was it just the permissions screwy? Was the contents of these files
with the "funny" permission sane, or did they contain garbage? What
about the modtime of the files?

In the original bug report random garbage had gotten written into the
inode table. That sort of failure is generally caused at a level
below that of the filesystem (i.e., device driver or hardware).

The question is whether the problems you are seeing seem to be caused
by wholesale corruption of an entire block of the inode table, or is
some other kind of problem. For example, if only the permissions are
getting screwed up, when the rest of the inode data is correct, then
yes, it would most likely be a filesystem bug. I haven't noticed any
such problem myself, but it's possible that something like that might
be going on. On the other hand, if it is an entire block in the inode
table getting corrupted then I'd be less likely to presume it to be a
filesystem flaw.

- Ted
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:00    [W:0.077 / U:3.920 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site