Well, duh, yeah, it is (cripes I hate getting old).
It does have some advantages and disadvantages, though, discussed at http://en.wikipedia.org/wiki/Ext3
Seems like, if you're getting that many inodes all over the place that you might be doing a whole lot of file creation, updates and the like? Might also be worth a look at how applications are doing things; for example, do applications stay open for a long, long time and do lots and lots of reads and writes to files? Be worth a look at flushing after a or a few writes in the application itself (like a call to fflush()
) if you can. I'm talking about stuff users start up and leave running for hours (or sometimes days) -- I've seen more than a few instances of files open in editors for three or four days. Even something as simple as a scheduled reboot at, oh, 0330 on Sunday can alleviate a lot of that nonsense. It doesn't hurt, either, to "bounce" a DBMS server in the middle of the night sometimes -- just stop and restart the DBMS server makes it flush and clean up after itself (things like pending updates to tables, logs, locks, all that stuff).
And, syncing every hour or so can't hurt either.
You can see if sync
will help by just logging in as root on a given server, enter sync
and hit the return -- it is takes a while (more than a second or two), that tells you you've got a lot of stuff hanging out there. I generally run that in threes (sync;sync;sync); first one goes slow, second and third usually go really, really fast.
Anyway, sorry about being old and dumb and hope some of the above helps a little.