Mac OS X to Get Journaling FS
overunderunderdone writes "According to eWeek, Apple Computer is planning to introduce a new journaling file system code-named 'Elvis' with the 10.2.2 release. Supposedly it will run on top of HFS+ and will be turned off by default. Though it will cost you 10% to 15% performance penalty the article says it is more extensive than NTFS and is on par with BeOS's 64-bit journaling file system. Not surprising since it is being developed by the same person - Dominic Giampaolo." I've been super impressed by OS X having used it as my primary laptop for the last couple weeks. It really is a great unix box- and this is one of the important missing puzzle pieces.
...when you pry HFS+ from my cold, dead hands.
No, wait. Give me that.
But what do I know. I'm just looking for anonymous gay sex.
Is this an entirely new journaling system or one based on an existing (BeOS) journaling system? Won't there be performance and stability impacts from basing it on HFS+ instead of a more modern framework? Is is possible to compile one of the existing *BSD journaling systems on OSX/Darwin (I haven't heard of anyone with success in this matter)?
what other important features has OSX that Linux has not. I am thinking about getting a Laptop with OSX so I was wondering how OXS compares to Linux.
Ok, so being I'm not the highest on there terminology totem pole, can somebody expain to me why journaling matters to me, and why its worth 10-15% of my system resources?
Mod point free since 2001
...to Switch! This was about the last major gripe I had with Mac OS X. We already have an encrypted file system. However, no matter how I have abused my Macs in the past, I have never had filesystem corruption with HFS+. I constantly forget to unmount my iPod and yank it off the firewire cable. Mac OS X grips about the possibility of filesystem corruption but so far, so good. Others mileage may vary and I wouldn't do it during a write.
Strange women lying in ponds distributing swords is no basis for a system of government.
i wish it would have been explained that way...
the writer of the eWeek article is Nick De Plumme (or something) - he's the guy from ThinkSecret....
hardly a "journalistic" website.
guns kill people like spoons make Rosie O'Donnell fat.
Though it will cost you 10% to 15% performance penalty
This refers to hard disk access time penalties, not an overall 10-15% reduction in the performance of your computer. You wouldn't notice the difference.
Pish. I have a Pismo (500MHz G3 PowerBook) and a 933 G4. While the G4 is a lot faster, the Pismo is a delight to use and leaves me with no complaints.
There should be a moratorium on the use of the apostrophe.
Max V.
NeXTMail/MIME Mail welcome
I wonder if that stated 10-15% performance hit
is with or without journal on a separate disk.
I'm surprised no one has brought this up yet.
Ben "You have your mind on computers, it seems."
At least this shows Apple's serious with courting the tech-savvy audience. Before, the reason to go with Apple was out of preference for the UI... and that was it. OS9 was ungainly and unstable. With OSX there're now true geeky reasons to want a Mac. No more being ashamed of coveting the rainbow apple! I want protected memory/journalling fs/unix multiuser/process stability/gnu tools/etc ... and an interface that looks like i can eat it for dessert!
I predict that it will become faster with time.
Just looking at how OS X itself has progressed in speed from Public Beta (slug with brick tied to it), to 10.0 (slug), to 10.1 (average lazy human), to 10.2 (average lazy human drinking strong coffee), I expect that by 10.3 this technology will not give nearly such a performance hit.
And heck. Don't like the speed hit? Turn it off.
But what do I know. I'm just looking for anonymous gay sex.
One of the main reasons I haven't switched from the despotic Linux family with it's Nazi-esque SysV init scripts is the presence of awesome journaling capability, knowing that I can pull out the power cords on my SCSI disks and reconstruct data on the fly gives me a lot of peace of mind.
But, having cut my eye teeth on SunOS 4.1.3, I still have a hankering for the old rc files, and the general Berkeleyness of the BSDs. Will Apple be good enough to help roll a decent journaling file system back into the BDSs, so I can return to my blissfil Berkely rc days, and not worry about the cleaning lady pulling out my RAID power outlet to use the vacuum cleaner?
OS X doesn't really need a fast G4, any G4 is good as long as you have a shedload of RAM. That's the real OS X bottleneck, which is easily solved by a quick trip to Crucial.com.
do you get an "Elvis has left the building" message?
A new and cool feature would be a file system that maintained a Weblog...
Today I stored my user's tax return...what a piece of crap...he actually expects the IRS to believe that he donated 40,000 to the MDA?...I think I'll just switch a few numbers around and drop a hint to the audit hotline
Yeah, that could be good...where's the SourceForge project for this?
I use FAT32.
The diskspace used by the journal file in NTFS and this new filesystem can be put to much better use.
Ya, like all of the fucking backups you need to keep your data safe. On that 80Gig disk, no less.
Fuck
All
There
is what we used to call the FAT filesystem, and for good reason. No security, no recovery. You work for Peter Norton, any chance?
Get a clue, bud - journaling file systems were integrated with _all_ modern OSes for a reason. Namely, big gain, near zero cost.
Soko
"Depression is merely anger without enthusiasm." - Anonymous
Rob, what kind of laptop is it?
And will you be writing a review of OSX and Apple laptops in the near future?
"The diskspace used by the journal file in NTFS and this new filesystem can be put to much better use."
You mean like empty cluster tips?
NTFS might use a good amount of space, but you make up for allot of that just based on the smaller cluster sizes. Take a large directory (20,000+ files, 10GB+), put it on a Win2k machine with NTFS, then another with FAT32. Right click -> properties. Size on Disk says it all.
-- "Government is the great fiction through which everybody endeavors to live at the expense of everybody else."
If it takes a 10-15% performace hit that is significant on older hardware. 10.2 is faster than 10.1 but on a G3 333 it's still dog slow. It works out my G4 733 too.
That being said I'll try it but hopefully there will be a way to disable it as well.
Disk Read Failure: The King is dead.
-----
jonathan barket
As a few people have pointed out, that's drive performance. I don't think alot of people will suffer from this. I am kind of paranoid however with my older TiBook because of the slower drive. As is, my external firewire drive rapes the internal one speed wise. Be interesting to see though.
-----
jonathan barket
The critical differences for me are that Apple stuff Just Works, Really Really Well, OS X is a Unix, and Apple seems to be philosophically opposed to Digital Rights Restrictions.
Whether or not they'd be like this if they were in a monopoly position is up to debate, but Apple is currently a far less evil company than Microsoft. Instead of putting roadblocks up for me, the Mac makes most things I want to do far easier.
Blockquoth the poster:
When Apple has retaken 95% of the market and starts using its 100 MWatt master Airport transmitters to force-download 3 GB trailers for 'Toy Story 5' onto my desktop, then I'll worry...
The only place Apple currently lags is in the CPU, we all hope the Power4 will fix that....
I'm sorry to nitpick, but you're talking about the PowerPC 970. (AKA GPUL) The newly announced chip is not the same as the POWER4. They share some architectural aspects, like the instruction set, but they're not the same.
Again, sorry for nitpicking. It's just that this is a really confusing matter, what with the POWER4 chip and the POWER architecture and the Amazon architecture and the PowerPC architecture and the PowerPC chips and... so on.
I write in my journal
Oops, they have!
Well, we all know Apple's just "embracing and extending", they don't ever submit any of their extensions to the IETF and release that code, right?
wrong, and wrong again!
If you are so attached to your computer that the software it runs *really* dictates how "free" or "enslaved" you are, then I think you have much bigger problems.
Computers, and the information they hold and route, that we are all so addicted to, are just toys. Computers are the ultimate distraction by which we, as a culture, impress ourselves with how clever we are. All the while, the quality of our lives becomes increasingly dominated by ones and zeros that don't really exist.
Think about it and tell me, how many hours of your life are spent in front of a computer that runs Free Software or not (it does not matter), *really* making the world a better place? How much of your self-worth is invested in the software you use or write, the games you play, the mp3 collection you build?
If your computer blew up today, how much of a life would you have?
Now tell me who is enslaved and who is free.
Tyler's words coming out of my mouth.
Gimmie a break. There's another kind of freedom: the freedom to get shit done without having to wrestle with the operating system. Remember that when you think about OSX. No slaves here, just someone getting the job done.
I live ze unknown. I love ze unknown. I am ze unknown.
America can, should, must, and will install Linux to protect our freedom. We must destroy the terrorism that is Mac OS X.
Onward, GNU soldiers! We cry freedom from coherent, mature GUIs! Freedom from packaging systems that work! Freedom from mature, accountable developers!
And if you consider for one moment "switching" to one of those evil, repugnant, proprietary systems, just Think of the Children, and pray that Stallman will give you strength in your time of weakness. Now we crush the infidels!
(-1, Raw and Uncut is the only way to read)
I'd rather have a plain old UFS filesystem that IS case sensitive than HFS+journaling+whatever.
Then... use one. You can create and mount UFS filesystems with OS X. You can even install the OS on a UFS filesystem, but legacy software often depends on features of HFS/HFS+. So if you don't have any legacy apps, you can run an entire OS X system on UFS.
I write in my journal
I'm sure some people out there realize this, but I wanted to point it out: having a journaling file system isn't meant for the typical user who has their laptop to check email & surf the web. Duh! No one using a graphical interface would want to sacrifice 15% of eye-candy processing power just to have a more reliable file system.
This change is meant for people who are using OS X on *servers*... possibly even (gasp!) headless servers! I'm currently running a webserver & IMAP mail server off of an OS X box, and I never actually pull up the GUI on it (why would I need to?). But I'd love to have the added assurance of JFS on it. This is the market that Elvis is meant for.
Apple is trying to edge their way into the low-end server market, which is already over-crowded. Putting this feature into their OS, even though it's turned off by default, is a big feature difference for the XServe-purchasing crowd.
So, unless you're really nervous about losing your porn, your desktop machine doesn't need this.
--Mid
A huge fraction of technical (and high-spending) PC users who might switch know exactly what Slashdot is.
It would be awesome: "... I'm Rob Malda, and I run Slashdot.org"
Do I see an Apple "switcher" ad featuring CmdrTaco in the near future?
There are 01 kinds of cars in the world. The General Lee, and everything else.
Unless Apple is caching its graphics to disc before displaying them, it wouldn't make a different in your "eye-candy processing power".
Thats a 15% hit in disk performance, not system performance.
OS X isn't like Linux in that respect. The swap file resides on the main partition.
The high-end TiBook is well over $5K. $6,059.00 to be exact, and that's without any extra options.
The high-end TiBook is $3,799.00 without any extras. The middle-of-the-road one is $3,199.00.
If you had mentioned the fact that you were quoting prices in Canadian dollars, you could have avoided this correction. Of course, if your purpose was to artificially inflate prices, you should have looked at the Australian store, where a top-end PowerBook goes for a whopping $8,745.00.
I write in my journal
A week with a Mac laptop, running OS X?
We are all doomed! Once you go Mac, you never go back!
Next he'll be dressing up in black, sporting a goatee, and drinking pretentious coffee drinks...
Like him!
GPL Deconstructed
What I want is a filesystem that supports 1)Long File Names 2)Large Files (over 4GB) 3)Journaling and 4) can be used between Linux, Mac OS X and whatever else. Unfortuantely there are currently no filesystems that mett all of these criteria. The closest one unfortunately is FAT32, only even it falls way short. Until then it is very difficult for me to share my firewire drive between multiple platforms. -peel
just my carrot for the button soup.
A journaling filesystem does not "provide corporate Mac sites with a new, historical view of their data"; all it does is increase reliability.
On servers, despite its popularity, journaling makes much less sense: there are better ways to recover from failures, and the performance hit really does matter.
I found this howto through google. It shows you step by step how to set up OSX to use a different partition for swaping. I've never used it myself so I can't comment either way.
I know I'm going to hell, I'm just trying to get good seats.
Furthermore, yes, software does rely on it. Even just untarring a UNIX archive on OS X can break it, like if it contains "Makefile" and "makefile".
Funny. You scath another poster for not pointing out that he was using Canadian dollars, but you never once said you were quoting USD.
Not everything is US-centric you know. And yes, I *am* an American.
"Ignorance more frequently begets confidence than does knowledge"
- Charles Darwin
Imagine that you have a library, and a librarian is filing away new books. When she is done filing them, she puts entries into the card catalog downstairs for the new books. The card catalog represents a filesystem's metadata.
Now imagine that the librarian falls out of a 2nd story window into a dumpster and is carted away before she finishes filing the books and updating the catalog. You have no idea what books were filed; you have to perform an exhaustive search of the library to ensure that the card catalog is correct, which takes a long time. This was fsck before journaling.
Servers with large amounts of disk space cannot afford extensive fsck times after a crash. It can take hours.
Now imagine that the librarian keeps a small notepad of the books that she is filing, and when she meets her sticky end, the new librarian can read the notepad, check and verify the new entries, then update the card catalog to a consistent state. We assume that the notepad is updated before the book is filed, so if we have an incomplete notepad entry, the librarian died and the entry can be disregarded. The notepad corresponds to the journal in a journaling file system.
It takes time to write a journal, so journaling filesystems will always be at least a little slower than non-journaling equivalents, design improvements aside.
Most journaling filesystems will only guard the card catalog (metadata). Some, such as VxFS and ext3, can also be made to journal the books (data), but performance goes down because so much more goes through the log.
Another feature to look for in journaling filesystems is dynamic inode creation. ext3 does not have this feature - you can only have so many card catalog entries, and when you exceed them, you can't add any more new books. XFS, for example, can create new inodes on the fly as long as you have disk space.
For Sun people, it is always a surprise to find that Sun's UFS does journaling (you don't have to buy Veritas VxFS), but you have to turn it on with an option in /etc/vfstab.
I assume that this rumor means that the new FS will be "more extensive" in its journaling capabilities, not features.
NTFS supports DACLs (Discretionary Access Control Lists. Grant rights specifically on files, folders, or both for any specific combination of rights. Yes, even includes things like execute, though most users don't get THAT granular.) It also supports Auditing via an ACL-like mechanism. Wanna see if user sally01 read file X? Add her with READ to the audit list. Who is renaming files in c:\docs? add Everyone with rename/modify to the Audit list.
NTFS does quotas, junction points (links), and reparse points. Reparse points allow things like EFS to work without the app being aware of it. If I wanted to replace the word "microsoft" with BORK BORK BORK on the disk, I could write a parsing driver and install it. Then, any file with my driver's signature in its reparse point list would be handed off to my driver for processing before being saved to disk or read from disk to an application.
There are plenty of other features as well, but the point is that to be a better filesystem than NTFS would take a huge amount of work on the filesystem itself, plus getting the OS to support it. However it is relatively easy to attack a specific point of NTFS (its journaling) and make your filesystem do that specific thing better.
Natural != (nontoxic || beneficial)
When the word Elvis is used, the words bloat, dead, and clusters (like peanut clusters) come to mind. I think marketing could have picked a better name for the FS.
Unless of course you someday decide that you don't want to use the Mac anymore, in which case you'll find you're just as badly locked in to it as 95% of the world is with Windows. I know you might think it crazy that you would ever wish to stop using the Mac, but Apple is a company, and we all know that they are hardly the most consistant things when it comes to doing what you want. What would happen if you wanted to switch to something else?
Well, you'd find that none of your apps would work on the platform of your choice, because the Mac APIs are proprietary, and there is only one implementation of them - the Apple implementation. Notice how easy it is to make open sourced Linux stuff work on the Mac? Yet that it's impossible to do the reverse? What about the Mac file formats? Even the iPod, a frickin MP3 player had to have some format reverse engineered (the index? don't remember). It's not like Apple deliberately throw up these roadblocks (though they have a history of abusing the legal system), it's just a natural consequence of lockin, which is what characterizes these kind of platforms.
[sigh]. I'm tired. Don't get me wrong, this isn't me criticizing OS X or even Apple specifically, not this time. I think it's great you're getting a journaled FS, more power to Apple and as a consequence you
But comments like the above just show that you haven't really experienced the pain of vendor lockin yet. Right now things are peachy. But in the future? What if the upgrade to 10.3 also costs $120? What will you do? Pay up I guess. Well, it's your choice, but at least understand that there are plenty of roadblocks in Mac land, it's just that they're one way only.
http://developer.apple.com/technotes/tn/tn1150.htm l
>80 column hard wrapped e-mail is not a sign of intelligent
>life
Actually, I'd guess that the memory bus is the bottleneck of modern PC's, but regardless of whether or not I'm right there, journaled filesystems tend to slow down writes more than reads (since reads don't require as many, if any, journal entries). So as far as performance goes, it probably won't slow down the performance of just reads (ie, applications loading) by 10%. The majority of the time, you are doing reads and not writes to the disk.
Go Badgers! -- #include "std/disclaimer.h"
That's what the reaction will be. Because they'll be waiting for Mac OS X to finish booting. OSX fsck's the file systems itself while it boots up. first it fscks the main drive/partition and then after the boot process starts up (and you see the pretty OSX start up screen with the progress bar) it checks other drives/partitions.
So, thankfully, AOL Grandmas running OSX all over the world would not ever have to see the command line.
Gabriel Ricard
It turns out that what people really want is a non-MS desktop that actually works. Most people over the age of 14 don't give a rat's ass about the ideological aspects at all.
Boobies never hurt anyone. - Sherry Glaser.
This is quite misguided, and is symptomatic of somebody who is obsessed with numbers.
First of all, it's crucial to note that the article is quite vague: "enabling the journaled file system will slow current system performance by 10 percent to 15 percent." What is a "system performance"? Editing a 100 KB document in Word is going to generate a very different load on the file system than streaming a 6 GB video.
Secondly, disk caches anticipate common usage patterns, so that most accesses (especially CPU instruction fetches) are satisfied from the cache in RAM. This means that the access that brought the data in from the disk counts for a much smaller percentage. Compression can also reduce the need for raw bandwidth.
Thirdly, journalling typically does not affect read performance, only write performance. Many applications don't require a great deal of write bandwidth, and those that do typically require a constant minimum bandwidth (capturing video) rather than a high peak bandwidth.
Fourthly, 10% or 15% is quite difficult to detect. Try to see if a friend can tell the difference between 10 seconds or 11 seconds. Try other durations if you wish. Then try to do it without counting ticks.
Finally, users can be distracted by appropriate eye candy. This is not a joke - it's a serious (and cheap) engineering solution.
In conclusion, no, the hard disk is not necessarily a bottleneck, and no, the computer may or may not slow down noticeably. The benefits of journalling, on the other hand, are well known.
Yup, and if OS 9.2.2 ever gets too fast for you, just remember to hold down the mouse button and it will stop and let you catch up.
All editorial writers ever do is come down from the hill after the battle is over and shoot the wounded.
With a journaling filesystem, it may become more of an issue. It would still be a performance vs. disk space trade off though.
I know of one AOL Grandma who has only one troubleshooting strategy: she power cycles her iMac whenever she has a computer problem.
Doug Moen
I have written a truly remarkable program which this sig is too small to contain.
gsfprez,
It might be worth your time to give a closer look to some of Think Secret's exclusive Mac insider news from this past year. As you indicated, circa 2000 we did indeed transition from an opinion/speculation site to a publication resembling what we are today. Not only have we broken some of the biggest Apple stories out there, but I'm proud of our accuracy.
I think our record for the past two years speaks for itself, and I invite others to examine our archives to reach their own conclusion.
If you truly believe that every news article drawing on facts not officially released from Apple is "rumor," then I suppose we have a fundamental difference of opinion.
Thanks for reading,
Nick dePlume
Publisher and Editor in Chief, Think Secret
http://www.thinksecret.com
I welcome the Journaled File System to OSX and certainly hope they are able to improve performance on machines. I'll gladly give up HFS+ for a good file system that has all the benefits of XFS. I'd like to see it make improvements over the much touted BFS and I hope it will be a 64-bit Journaled File System that allows attributes to be searched quickly much like BeOS and if possible clustering like SGI does with their XFS disks in CXFS.
X _2 000/
Here is a great article by Wilfredo Sánchez on Mac OS and Unix. In it is an extensive explanation on HFS, HFS+ and UFS.
http://www.mit.edu/people/wsanchez/papers/USENI
-Diganta
Oh yeah. And BeOS still rocks, even though it is LONG DEAD! LONG LIVE THE DEAD!
What I mean by "modern" is "modern design, e.g. designed with modern features (such as journaling)", not necessarily "modern implementation". It seems that HFS+ was just an extension of HFS, not a complete rewrite for OSX, and so you're just hacking on top of a hack. It seems that integrity, reliability, and speed of the filesystem would be better if they started from scratch and designed a completely new, OSX-centered filesystem rather than extending HFS+ which is really MacOS9-legacy.