I've had this same error occur several times, on kernels ranging from 2.0.2x
to 2.0.35. In my case it's an IDE drive, and the affected directory is usually
(perhaps always) /var/log, and it usually happens about the same time this
cron job runs:
1 * * * * accttrim -n 1000 /var/log/acct 2>/dev/null || accton /var/log/acct
I haven't ever lost any files from /var/log. I just make a new directory,
move /var/log/* into it (during the glob, ext2_readdir complains about the
holes again), rmdir /var/log, and mv the new directory in its place, and
everything stays happy for a while. (I did run e2fsck the first time I saw
the error. It's been so long I don't remember what the results of that were.)
Is there anything I can do to try to catch these directory "holes" as they
are being created? Any further investigation I can perform that would be
helpful?
-- Alan Curry- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/