Re: great new thread idea
Originally posted by eirik
I'm a bit skeptical about the utility/importance to server administrators of a journalling file system. Nonetheless, ktlx raises a good point to me. I'd like to see a thread digging into what features OS X lacks for various server markets/needs. There we could discuss, for examlpe, the utility/need for a journalling file system in a server world.
I'd start it myself but I don't have that priviledge in Macrumors.
Eirik
The first time you have a hard crash of a 500MB file system on a live system you will see the importance of a journaling file system.

Without a journaling file system, the file system will either come up possibly corrupt or you will need to do a fsck on it. If it is corrupt and you try to write, the file system is toast and it is time to get out your backup tapes (RAID does not help if the file system is corrupt). If you run fsck, your server is unavailable until it is complete. Large file systems can take a
long time to run fsck on. I have seen file servers without journaling file systems take hours to come up waiting on their fscks to complete.
With a journaling file system, this does not happen (except in rare cases that would have trashed a non-journaling file system anyway). The file system is either kept in a non-corrupt state or a recoverable state by backing out incomplete updates. For an enterprise-class database server or large file server, this is critical. Web and print servers can get away without a journaling file system just fine. Most e-mail systems could probably get away without it, although if it is a large one, having the mail spool and storage file systems journaled is nice.
These features are so critical to enterprise class servers that Veritas built a very successfuly business solely around providing journaling file systems and software RAID for UNIX systems. When Linux first started going after the server market, one of the knocks against it was that it had no (and no one provided) a journaling file system for it. Since then several companies stepped in to fill in the gaps. Linux still has some limitations, but it is much farther along than Mac OS X.
Please don't get me wrong, the Xserve is a nice server and Mac OS X is a nice operating system. It is a wonderful system for a small operation or for most Web, file and print services. But to me, a high end server is an enterprise-class server that is going to run a database (i.e. Oracle or DB/2), application server (i.e. BEA, PeopleSoft or SAP) or large e-mail or file server. Apple has no experience here and Mac OS X is woefully inadequate compared to Solaris, HP-UX, AIX and Linux. And Linux is only on that list, in my opinion, thanks to the huge investment by IBM.
It will very difficult for Apple to get much traction in the large server market as Sun, Hewlett-Packard and IBM own 90% of the UNIX server market. All of them have far more experience than Apple at building large servers. My guess is that as Linux matures and Intel improves their server CPU designs, Dell will capture the remaining market share leaving only crumbs for Apple or any other company.