lkml.org 
[lkml]   [2003]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] EXT3 extents against 2.6.0-test7
On Fri, 17 Oct 2003 16:13:51 -0400
Ed Sweetman <ed.sweetman@wmich.edu> wrote:

> How am i supposed to know which directory in the fs this corruption
> takes place in? I can tell you the size of the partitions that have
> extents enabled, From that error message i dont even know which
> partition it was. And judging by the dmesg last modified time, this
> happened 2 days ago

OK. the question wasn't clear.

1) could you _estimate_ max directory size or number of entries in single
directory on your filesystems, please? had you large directories?
100, 300, 500 or more entries?

2) did you use 2.6.0-test7+extents or some another patches?

3) could you describe workload. knowing it I'd try to reproduce this


> Isn't it possible though that this happened in one of the non-extents
> enabled partitions though? Since they still have the ability to read
> extents in files, they have to try and look them up every time for
> everything dont they? Anyways, the two partitions above are the only
> ones i actually enable extents on.
>

extents take place only if flag in inode->i_flags is set. that flag can
be set only during inode creation on extents-enabled filesystem.

with best wishes, Alex
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

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