> > In my opinion the non-inclosure in the mainline kernel is the most
> > important reason not to use XFS (or any other FS). Which in turn
> > massively reduces the tester base. It is a shame, because for some type
> > of applications it performs great, or better than anything else.
>
> On the other hand, filesystem corruption bugs are one of the worst type
> to suffer from. We absolutely don't want to include filesystems without
> at least a reasonable proven track record in the mainline kernel, and
> therefore encourage the various distributions to use them, incase any
> bugs do show up. Look how long a buffer overflow existed in Zlib
> unnoticed.
Given that the IDE code in 2.5 wrote random bad data not only in the
mounted filesystems but on other partitions and even drives, if we are
dropping things which have an unreasonable track record, we should drop
IDE for sure ;-)
This is a development kernel, the rules for what goes in should be far
more open than the stable series. IMHO both JFS (AIX) and XFS (IRIX)
should be in, because they will not be solid until users actually use
them, and better that be in a development kernel.
>
> EXT2 is a very capable filesystem, and has *years* of proven
> reliability. That's why I'm not going to switch away from it for
> critical work any time soon.
One might note that both JFS and XFS have been around since xiafs was the
Linux f/s of choice. It's all relative. If you want old and grotty, go
back to minix f/s.
-- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.- 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/