Journalling under MacOS X 10.2.8 Jaguar
|
|
Thread rating:  |
Bob Blaylock - 30 Oct 2005 04:53 GMT I know that Journalling was implemented under Jaguar, but supposedly improved to a great degree under Panther, as well as being enabled by default at that point.
I am running MacOS X 10.2.8, Jaguar, on my beige G3.
On some previous instance where I enabled journalling, I was met with several Kernel Panics, which persuaded me to turn it off.
Many reformat/reinstall cycles, and a few years later, I tried it again, and got no Kernel panics, but thought it caused a significant loss of performance, so I turned it off again.
Last night, after yet another reformat/reinstall cycle, I again enabled journalling, and so far, it seems to be working fine, without any noticeable performance issues.
I was wondering what experiences, advice, wisdom, and knowledge anyone else might have to share regarding journalling under Jaguar.
My most recent event of turning it on came about because my latest reformat/reinstall cycle was brought about by a sudden power loss at an inopportune time that caused sufficient corruption of my operating system that less drastic means failed to get it working again. I'm assuming that journalling will protect me from this.
 Signature "Today, we celebrate the first glorious anniversary of the Information Purification Directives. ... Our Unification of Thoughts is more powerful a weapon than any fleet or army on earth. ... Our enemies shall talk themselves to death and we will bury them with their own confusion."
G.T. - 30 Oct 2005 09:05 GMT > I was wondering what experiences, advice, wisdom, and knowledge anyone > else might have to share regarding journalling under Jaguar. Never had any problems with it whatsoever on any of our Macs at work or mine at home. With Jaguar or Panther. So don't have any advice other than it was a no-brainer.
Greg
Mark Conrad - 30 Oct 2005 10:40 GMT > I was wondering what experiences, advice, wisdom, and knowledge anyone > else might have to share regarding journalling under Jaguar. Well, I could tell you the advice I get from the people here who are too inconsiderate to offer direct advice, but who feel compelled to beat down guys like us. They would say this question has been answered innumerable times, and that you should waste hours of your time searching Google for answers, instead of bothering them.
...but I could not do a dirty trick like that to you.<g>
Apple (and others) - in their infinite wisdom, try to make everything possible automatic.
Er, _except_ the things that _I_ prefer that they make automatic.
But it is their OS, so they can do anything they darn well please, and don't have to listen to their customers if they don't want to.
This is going to be a long explanation, so sit down and get comfortable.
I am going to give you the long version, so you fully understand it.
> My most recent event of turning it on came about because my latest > reformat/reinstall cycle was brought about by a sudden power loss at an > inopportune time that caused sufficient corruption of my operating > system that less drastic means failed to get it working again. I'm > assuming that journalling will protect me from this. That is the prime reason for journaling, to enable you to protect the _file_ system against being corrupted, when you have a power interruption. Notice I said protects the file system, not the file being written to disk at the time of the power interruption.
This indeed would make it easier to get running again after a power interruption. (on a desktop Mac)
Being powerbooks run off battery power, it is very unlikely that a power failure would affect them, even if they were plugged into the AC outlet, because their battery would prevent them from losing power.
Background Info', Necessary to Fully Understand Journaling - ******************************************** A file system of some sort can be considered to be a necessary _part_ of the operating system, but just a tiny small part, generally just a few megabytes in size.
BEFORE you install the OS, you install an approved default file system, usually a HFS+ file system. This is normally done by you before OS X is even installed - - - when you "prepare" your hard drive by erasing it, partitioning it, or whatever you do to get the drive icon to appear on the screen of your computer.
If you _don't_ install an "approved" file system of some kind on your hard drive, the drive's icon might not even appear on your screen. You will get an error message something like this:
"An unrecognizable drive is attached to this computer, do you want me to initialize it?"
Sometimes that message will appear if a hard drive was used on a Window's computer. There _is_ a file system, a Window's file system, which the Mac simply might not "recognize".
...or, some dirty guy like me might have erased all traces of any sort of file system whatever, from the drive. (its a lot of work, but it _can_ be done)
Whatever the reason, your Jaguar CD will refuse to install OS X until you let it install an "approved" file system first.
It will give you your choice of HFS+ (extended) - - - or UFS.
UFS is only used by Unix geeks, so the Jaguar install CD will probably gently nudge you to use the regular HFS+ "extended" default variety of file system.
Okay, the Jaguar CD installs a default file system, then it proceeds to install the Jaguar OS itself.
The invisible file system files get updated to reflect where each file was placed on the disk, what kind of file it was, what kind of app' will be used to open the file, when each file was written to disk, and a lot of other details about the files. ********************************************* End of Background Info' -
Okay, back to Journaling.
Let's look at one other reason for journaling.
Files in OS X are constantly changing in size, some file segments are automatically deleted, some files grow in size, some files may be automatically compressed, other files may be automatically defragged, which means the segments of those defragged files get moved to other locations on the disk.
Time is consumed as all of these many changes are written to the file system area of the disk, in order to keep track of where files are located on the disk.
That "file system housekeeping" time is taken away from any disk chores that _you_ want to do, like downloading a file from the Internet.
A journaling system allows you to postpone some of this disk writing to the file system area, keeping track of all the file system changes in fast RAM instead, then later, writing all the changes to disk at once.
This saves the time that would ordinarily be lost by many slow disk constantly interrupting its "legitimate" work in order to update the file system area of the disk.
All that said, journaling itself slows down some operations about 5% according to some reports. I have read that some users prefer to shut off journaling when their Macs are doing CPU intensive tasks, like displaying full screen movies, for example.
Keep in mind that the MAIN reason for journaling is to prevent _some_ of the damage that would be done in case of a power interruption, or the rare crash of the OS itself.
FWIW, here I have operated both ways, sometimes leaving journaling on for months at a time, sometimes leaving it off for months at a time.
Generally, when I think of it, I guess I prefer to leave it off.
However, if I were doing a lot of disk intensive tasks, my preference then would shift to keeping it on, to possibly speed up those disk tasks a tiny bit.
My rule of thumb, leave it on for disk intensive tasks, leave it off for CPU intensive tasks.
Confusing, isn't it.<g>
I don't really worry about power interruptions here, even though they occur often due to my rural location and unreliable power.
I run powerbooks exclusively, and I also have them running from un-interruptible power supplies - - - so over the years no power interruption has zapped my Macs.
If I ran desktop Macs, I _might_ engage journaling.
Then again, perhaps not.
Everyone has to make up their own mind. Most Mac users just leave journaling on. Journaling with Tiger is turned on by default.
Mark-
Marc Heusser - 30 Oct 2005 11:09 GMT > Being powerbooks run off battery power, it is very unlikely that a > power failure would affect them, even if they were plugged into the AC > outlet, because their battery would prevent them from losing power. I found it very easy to fail a Powerbook (17"): Just close the lid, turn it over, get the battery out to exchange it for a full one - if you do that fast enough, it will not have gone to sleep yet and will restart only if you press the button.
Marc
 Signature Switzerland/Europe <http://www.heusser.com> remove CHEERS and from MERCIAL to get valid e-mail
Mark Conrad - 30 Oct 2005 18:43 GMT > > Being powerbooks run off battery power, it is very unlikely that a > > power failure would affect them, even if they were plugged into the AC [quoted text clipped - 4 lines] > a full one - if you do that fast enough, it will not have gone to sleep > yet and will restart only if you press the button. Heh, bet you were not expecting that.
Moral of that story, make darn certain that the powerbook has actually had time to go to sleep before one changes the battery.<g>
Mark-
G.T. - 30 Oct 2005 20:29 GMT > > I was wondering what experiences, advice, wisdom, and knowledge anyone > > else might have to share regarding journalling under Jaguar. [quoted text clipped - 4 lines] > innumerable times, and that you should waste hours of your time > searching Google for answers, instead of bothering them. Wow, Mark provides a full set of encyclopedias when a simple one liner answer is sufficient.
> That "file system housekeeping" time is taken away from any disk chores > that _you_ want to do, like downloading a file from the Internet. Really, REALLY poor example.
> A journaling system allows you to postpone some of this disk writing to > the file system area, keeping track of all the file system changes in [quoted text clipped - 6 lines] > All that said, journaling itself slows down some operations about 5% > according to some reports. Citation please, showing which operations.
> I have read that some users prefer to shut > off journaling when their Macs are doing CPU intensive tasks, like > displaying full screen movies, for example. Citation please.
> Keep in mind that the MAIN reason for journaling is to prevent > _some_ of the damage that would be done in case of a power [quoted text clipped - 11 lines] > My rule of thumb, leave it on for disk intensive tasks, leave it off > for CPU intensive tasks. You make no sense at all.
Greg
Mark Conrad - 31 Oct 2005 01:47 GMT G.T. say fit to offer these snide remarks -
Bob Blaylock posed this question to all -
> > > I was wondering what experiences, advice, wisdom, and knowledge anyone > > > else might have to share regarding journalling under Jaguar. Mark Conrad responded -
> > Well, I could tell you the advice I get from the people here who are > > too inconsiderate to offer direct advice, but who feel compelled to > > beat down guys like us. They would say this question has been answered > > innumerable times, and that you should waste hours of your time > > searching Google for answers, instead of bothering them. > > ...but I could not do a dirty trick like that to you.<g> Long remainder of post about journaling clipped.
G.T. posted these sour grapes -
> Wow, Mark provides a full set of encyclopedias when a simple one liner > answer is sufficient. Not really, G.T. - - - a subject like journaling can not be explained in a one liner. An expert here on journaling, Bob Harris, used a post over twice as long as mine in the same thread that you referenced, in order to explain journaling.
Mark noted -
> > That "file system housekeeping" time is taken away from any disk chores > > that _you_ want to do, like downloading a file from the Internet. More sour grapes from G.T.
> Really, REALLY poor example. You are dead wrong again as usual.
OS X is a multitasking system, which means that it can do several tasks at essentially the same time.
For example, I could start one task of the computer playing a chess game against itself, white against black.
I could then start a second task, of downloading a file from the Internet.
Both these tasks will run at essentially the same time, while I get a cup of coffee or whatever.
Each of these tasks will slow the other task down. for example, the chess task will slow down the file download task, an appreciable amount.
The chess task creates extensive files to keep track of chess moves. Those files grow, shrink, get deleted, get created, all depending on how the chess game is progressing.
Exotic file handling occurs, "Alpha-Beta pruning of game trees" for example.
The chess files _have_ to be updated in the file system, otherwise the chess game will not know where to access the files when it needs them to plan next moves, etc.
So any time wasted by waiting for the slow hard drive to update the file system _has_ to be taken away from the two running tasks.
By contrast, if journaling is enabled, no time is wasted waiting for the hard drive to update the disk's file system. Instead, fast RAM is updated, and the chess game program "knows" to go to the journal area in RAM to get any _recent_ updates of the file system.
The long Bob Harris post will explain this in detail. (see his section explaining about saving repeated unnecessary reads and writes to disk, by using journal RAM instead)
> > All that said, journaling itself slows down some operations about 5% > > according to some reports. > > Citation please, showing which operations. Get your own. In your case, due to your accusations, I have no desire to help you. You _do_ know how to use Google, don't you?
> > I have read that some users prefer to shut > > off journaling when their Macs are doing CPU intensive tasks, like > > displaying full screen movies, for example. > > Citation please. Same response as above.
> You make no sense at all. More sour grapes? I notice you refused to cite any specific example when you made the above all encompassing accusation.
Mark-
Mark Conrad - 31 Oct 2005 04:12 GMT For those interested in a more in-depth description of journaling -
Date: 7/24/05 5:13am Thread Title: Where is the journaling log file? Originating Poster: Mark Conrad Poster Responding: Bob Miller Website: <http://devplug.com/topic57501.htm>
A very comprehensive post by Bob Miller, if you scroll down a bit to view his entire (long) post, the post at 5:13am - - - _not_ the very first post on the webpage.
Mark-
G.T. - 31 Oct 2005 04:33 GMT > G.T. say fit to offer these snide remarks - > [quoted text clipped - 19 lines] > over twice as long as mine in the same thread that you referenced, in > order to explain journaling. You mean the incredibly informative post he made with this conclusion:
"So in conclusion. You do want the journal file. Mostly because it has not been giving anyone any problems that I have heard about, and I have been following the Mac newsgroups and MacFixIt.com for a long time, and it has not shown up as an issue."
And his post was worth the several paragraphs of reading because it didn't include a bunch of non-sensical off-topic whining like yours does.
> Mark noted - > > > That "file system housekeeping" time is taken away from any disk chores [quoted text clipped - 20 lines] > chess task will slow down the file download task, an appreciable > amount. You meant an unnoticeable amount, right?
> The chess task creates extensive files to keep track of chess moves. > Those files grow, shrink, get deleted, get created, all depending on [quoted text clipped - 14 lines] > updated, and the chess game program "knows" to go to the journal area > in RAM to get any _recent_ updates of the file system. You need to reread his Bob Harris' post. Your intrepretation borders on the bizarre.
> The long Bob Harris post will explain this in detail. > (see his section explaining about saving repeated unnecessary reads and [quoted text clipped - 7 lines] > Get your own. In your case, due to your accusations, I have no desire > to help you. You _do_ know how to use Google, don't you? Yes, and I still haven't found a %5 hit. Please provide a citation since you're the one who came up with that figure.
> > > I have read that some users prefer to shut > > > off journaling when their Macs are doing CPU intensive tasks, like [quoted text clipped - 3 lines] > > Same response as above. They don't turn it off for CPU intensive tasks. They turn it off for tasks such as writing uncompressed realtime video, if necessary, as both Tom Stiller and Ilgaz Olcal, respectively, pointed out to you in July:
"Flicker is a playback artifact and journaling does not come into play during read operations. I believe "Ilgaz Ocal" was referring to _writing_ video files, when the extra disk activity associated with journaling might impact the ability to capture realtime uncompressed video."
"As reply to this message, journaling will effect real time video recording (uncompressed) etc but remember, they are such speeds needing fiber SCSI etc (even SATA not enough) so I say to keep journaling on."
Do you see mention of CPU intensive tasks?
Greg
Mark Conrad - 30 Oct 2005 18:26 GMT > I am running MacOS X 10.2.8, Jaguar, on my beige G3. A few more things about journaling I saved for this follow-up post.
Bob Harris is our resident expert on journaling, wish he would pop in to supplement this thread with his expertise.
Apparently, some of the journal information is also kept on disk if I understood Bob Harris correctly. This is important in some situations.
For example, if you are running a big honking Mac server, with a hundred times more files than we run in our hobby Macs - - -
Imagine such a server has a power outage. Well, ordinarily, when you fire it back up again, fsck runs automatically to try to repair the file system that was messed up by the power outage.
WITHOUT journaling, fsck has to check _each_ _one_ of potentially millions of files, which _could_ take as long as 30 minutes.
WITH journaling, a lot of this info is on disk, so fsck would only take perhaps one minute to run its file system repairs, because fsck could "play back" a lot of the journal info' and therefore fsck would be saved from needing to check _all_ the files on disk.
This saving of time is important if you are trying to get a huge critical server back on the air.
Not so important on our hobby Macs.
Mark-
Bob Blaylock - 31 Oct 2005 01:05 GMT > WITHOUT journaling, fsck has to check _each_ _one_ of potentially > millions of files, which _could_ take as long as 30 minutes. [quoted text clipped - 3 lines] > could "play back" a lot of the journal info' and therefore fsck would > be saved from needing to check _all_ the files on disk. I know from past experience that if journalling is enabled, fsck will not run (at least not from single-user mode) on a journalled volume unless you use the -f switch. I'm given to understand that doing so is a bad idea, that letting fsck "repair" the journalled volume will mess with the attempt that will later occur in the boot process to repair it using the journalled data.
I suppose this makes sense. On a journalled volume that has been shut down incorrectly, the volume is inconsistent in a manner that fsck would want to fix, but the journalling data is present to tell the journalling system how to fix it. If fsck is used to fix a volume in this condition, then it will no longer match what the journalling system thinks is wrong with it, and the journalling system might well just screw it up worse.
On the other hand, if a volume has been shut down correctly, of has has no journalling-related inconsistencies that haven't been resolved already by the journalling system, then I expect it probably is perfectly find to run fsck in order to find and repair any other inconsistencies which journalling might have missed.
Any thoughts on this?
 Signature "Today, we celebrate the first glorious anniversary of the Information Purification Directives. ... Our Unification of Thoughts is more powerful a weapon than any fleet or army on earth. ... Our enemies shall talk themselves to death and we will bury them with their own confusion."
Tom Stiller - 31 Oct 2005 01:31 GMT > > WITHOUT journaling, fsck has to check _each_ _one_ of potentially > > millions of files, which _could_ take as long as 30 minutes. [quoted text clipped - 26 lines] > > Any thoughts on this? On those occasions when I've restarted in single user mode after a power failure, I see a message that says the journal has been rolled forward before I get the first prompt. Unless the machine was known to be in a quiescent state when the power failed, I always run 'applejack' which has fsck as its first option. Occasionally, fsck will find and repair some orphaned nodes, but I've never had it cause a problem.
 Signature Tom Stiller
PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
Jerry Kindall - 31 Oct 2005 02:46 GMT > > > WITHOUT journaling, fsck has to check _each_ _one_ of potentially > > > millions of files, which _could_ take as long as 30 minutes. [quoted text clipped - 33 lines] > has fsck as its first option. Occasionally, fsck will find and repair > some orphaned nodes, but I've never had it cause a problem. Yeah, the journal roll-forward happens as the disk is mounted. You can safely fsck a journaled boot volume in single-user mode.
 Signature Jerry Kindall, Seattle, WA <http://www.jerrykindall.com/>
Send only plain text messages under 32K to the Reply-To address. This mailbox is filtered aggressively to thwart spam and viruses.
Bob Blaylock - 31 Oct 2005 03:16 GMT > > On those occasions when I've restarted in single user mode after a power > > failure, I see a message that says the journal has been rolled forward [quoted text clipped - 5 lines] > Yeah, the journal roll-forward happens as the disk is mounted. You can > safely fsck a journaled boot volume in single-user mode. It's clear enough you'd want the journal roll-forward to happen before you fscked a journalled volume. Apparently, it does. So why does fsck require the -f switch to run on a journalled volume? That'd make sense if fscking a journalled volume was potentially dangerous, and it wanted to be sure you knew what you were doing, which is what I was previously (and apparently, incorrectly) assuming
 Signature "Today, we celebrate the first glorious anniversary of the Information Purification Directives. ... Our Unification of Thoughts is more powerful a weapon than any fleet or army on earth. ... Our enemies shall talk themselves to death and we will bury them with their own confusion."
Jerry Kindall - 31 Oct 2005 03:56 GMT > > > On those occasions when I've restarted in single user mode after a power > > > failure, I see a message that says the journal has been rolled forward [quoted text clipped - 12 lines] > to be sure you knew what you were doing, which is what I was previously > (and apparently, incorrectly) assuming Primarily because you shouldn't _need_ to fsck a volume with a journal; that's the whole point of the journal, after all. The OS _will_ automatically fsck volumes that weren't unmounted properly, so some way to prevent this happening on journaled volumes is necessary. Apple chose to put that check into fsck, so when called at mount time it doesn't check file systems that shouldn't need checking. (Another way to look at it is: fsck _is_ checking the filesystem -- to see whether it needs checked at all.)
 Signature Jerry Kindall, Seattle, WA <http://www.jerrykindall.com/>
Send only plain text messages under 32K to the Reply-To address. This mailbox is filtered aggressively to thwart spam and viruses.
Mark Conrad - 31 Oct 2005 04:26 GMT > > WITHOUT journaling, fsck has to check _each_ _one_ of potentially > > millions of files, which _could_ take as long as 30 minutes. [quoted text clipped - 6 lines] > I know from past experience that if journalling is enabled, fsck will > not run ...<snip>... Thanks for clarifying that point, apparently I was wrong about fsck running automatically when lournaling is enabled.
Mark-
|
|
|