On Sat, Dec 10, 2005 at 03:10:05PM -0700, Michael Loftis wrote:
> >Thanks for the detailled explanation!
> I try not to say something without actual experience and technical details
> to back it up. :)
Hmm, you seem to be doing a pretty good job of that here...
> >Yes, I would *love* to use a totally new file system with a new,
> >dynamic, good design, but - just as many others - had my experiences
> >with ReiserFS and it will take a *lot* of time for ReiserFS to restore
> >confidence. So for now, I'll probably stay with ext3, with which I had
> >no problems so far.
> >JFS/XFS should also both be capable of growing, XFS of online-growth,
> XFS has terrible unpredictable performance in production. Also it has very
What on earth does that mean? Whatever it means, it doesn't
sound right - can you back that up with some data please?
> bad behavior when recovering from crashes,
Details? Are you talking about this post of yours:
There have been several fixes in this area since that post.
> often times it's tools totally fail to clean the filesystem.
In what way? Did you open a bug report?
> It also needs larger kernel stacks because
> of some of the really deep call trees,
Those have been long since fixed as far as we are aware. Do you
have an actual example where things can fail?
> so when you use it with LVM or MD it
> can oops unless you use the larger kernel stacks.
Anything can oops in combination with enough stacked device drivers
(although there has been block layer work to resolve this recently,
so you should try again with a current kernel...). If you have an
actual example of this still happening, please open a bug or at least
let the XFS developers know of your test case. Thanks.
> We also have had
> problems with the quota system but the details on that have faded.
Seems like details of all the problems you described have faded.
Your mail seems to me like a bit of a troll ... I guess you had a
problem or two a couple of years ago (from searching the lists)
and are still sore. Can you point me to mailing list reports of
the problems you're refering to here or bug reports you've opened
for these issues? I'll let you know if any of them are still