[lkml]   [2003]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Corruption problem with ext3 and htree
Hmm... can you help construct a test case that doesn't rely on the
presence of the Gentoo distribution? Is there some way we can
instrument the python code so we can see the exact filesystem
operations (renames, deletions, moves, etc.) that is going on? The
good news is that you say that you're able to reproduce it every
single time, which implies it's not a timing related problem.

> And for some reason its only with the Hash::Util* files that it have
> this problem. Am assuming it might not be related to the filename
> itself ?

It could possibly be a hash value dependent problem, which case it
could be related to the filename. That's not very likely, but it is
possible. If you could send us the result of "dumpe2fs -h /dev/XXXX",
that would be useful. In particular the last two lines:

Default directory hash: tea
Directory Hash Seed: 407dbbca-8326-4bed-bc7c-bb0453f79049

The most important thing though is to be able to reduce the test case
to something which is slightly easier for us ext2/3 developers to run.

- 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 13:33    [W:0.054 / U:1.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site