Re-sent due to "5.7.1 Content-Policy reject msg: The capital Triple-X in subject is way too often associated with junk email, please rephrase. ":
>>> "Ulrich Windl" <ulrich.wi...@rz.uni-regensburg.de> schrieb am 16.08.2013 um
10:29 in Nachricht <520e15ef.ed38.00a...@rz.uni-regensburg.de>:
> Hi,
>
> recently I found out that we his the "NFS: directory in/mdoc contains a
> readdir loop.Please contact your server vendor." frequently on an NFS-Client
> running SLES11 SP2 (3.0.80-0.7-default). The NFS server is also SLES11 SP2,
> and
> the exported filesystem is ext3 with "dir_index" on.
>
> SLES support suggested to turn off "dir_index" in ext3, which "should be
> safe".
>
> I googled the problem, and I found some (to me) vague description by Ted Tso
> ("If not readdir() then what?") back in 2011 referring to ext3.
>
> Now I wonder: Is this problem restricted to just ext3, or to any filesystem?
>
> We have (and I cannot change it) directories with many files, even if just
> temporary.
>
> The statistics say: "122431/524288 files (3.4% non-contiguous),
> 1230006/2097152 blocks"
>
> The biggest directory has almost 1MB in size, but just about 16513 directory
> entries.
>
> I'm wondering whether "directory compaction" (compact slots of removed
> entries) would help with the problem. In HP-UX VxFS you could do directory
> compation online...
>
> If you can explain the relationship of ext3 and other filesystems with this
> bug, please reply keeping the CC:
>
> Thank you,
> Ulrich
Header
Description: Binary data
