Disable Journaling in DiskUtility

Tried to diable journaling on external drive from disk utility.
Normal way did not work. Had to use Terminal.
Can anybody confirm?
OS X 10.5.2

You can't disable journaling on an active Time Machine backup volume.

Similar Messages

Disable journaling on external drive?

Hello!
I have a MacBook Pro running Mac OS X 10.8.2 Mountain Lion and an external WesternDigital 320GB drive formatted with HFS+ Journaled for Time Machine backups.
I wanted to use the external HD with Linux, but Journaling isn't supported. When i tried to disable it in Disk Utility (option-click File --> disable journaling) , it failed. I tried "Repair Drive" and when it finished, the option to disable journaling has been grayed out.
Finally, i used the terminal. I typed:
sudo diskutil disablejournal /Volumes/WD320
but it throws the following error:
"An error occurred journaling the file system: The underlying task reported failure on exit (-69860)"
I also tried to use /dev/disk2s2 instead of /Volumes/WD320, but it gives the same result.
System log gives:
kernel[0] <Debug>: hfs: cannot disable journaling on volumes with directory hardlinks
Any help would be greatly appreciated
penguin01210

You can't disable journaling on an active Time Machine backup volume.

Disable journaling

Hi.
I purchased a WDTV Live with a WD external Hard drive.
The external when connected to the home network is read only.
Threads have suggested I disable journaling.
I am running 10.9.2 and disk utility no longer has MacOs Extended as an option.
Any thoughts?

OK, so most people say it's a Good Thing! A Gift From Apple!
So you don't think I'm not going to gain anything in iMovie '09 speed for rendering/encoding/multiplexing/burning. Like I said, I've been having issues & am in the middle of a Large Project. So I might keep it off for this Third Part of the Project & see if anything improves. If it does not help, I will in fact enable it again.
Here is something I read which inspired me to create this Post in the first Place:
READ BELOW:
"The problem is that journaling takes time. Enough time that it is worth considering turning journaling off on all your media drives. The benefit is that you get faster performance. The disadvantage is that in the event of a crash, you don't have the protection journaling provides. On the third hand, hard drives with journaling turned off are in no worse shape than hard drives running under OS 10.2.
In my experience with a wide variety of media clients, disk directory problems almost never arise with secondary drives, they are almost exclusively the domain of the boot disk.
As Apple writes: "If your [computer] contains high-bandwidth usage data files, such as large video, graphics, or audio files, you may want to weigh the benefits of using journaling against the performance needed to access your data. In most cases, the impact of journaling upon data access performance are unnoticeable to users, but its implementation may not be practical for [computers] where data access demands outweigh its benefits.
My recommendation? Leave journaling turned on for your boot disk and turn it off for all secondary drives (both internal and external) that are used to store media files. For external drives that store data, not media, turn journaling on." Written By Larry Jordan
I'm curious to know why baltwo disables it. baltwo? Did you read this same article?

Error Enabling Journaling with diskutil enableJournal diskXsX

I have few large backup volumes built specifically as HFS+ with Journaling disabled but now I notice problems where we have to wait very long time for hfs_fsck to complete its checkup and have decided to go back and enable journaling but keep getting errors. Here is more detail:
After I ran:
sudo fsck_hfs /dev/disk14s3
And it completed without problem then I ran:
sudo diskutil enableJournal disk14s3
Which gives me following error:
An error occured journaling the filesystem
Checking volume info it shows:
File System: HFS+
Owners: Enabled
Partition Type: Apple_HFS
Bootable: Is bootable
Media Type: Generic
Total Size: 9.2 TB
Free Space: 548.3 GB
Read Only: No
Ejectable: Yes
I have unmounted and mounted this volume without problem and have tried different variations of "diskutil enableJournal xxx" but everytime I get same error. I've also "Disk Utility" Enable Journaling option with no success and have tried diskutil with "sudo -s" option and tried "diskutil disableJournal xxx" and it shows:
Journaling was already disabled on the volume
I have another similar volume that has 2 TB available space and am getting same error not enabling journaling. First volume has around 85,000 files and second one close to 800,000.
Appreciate any input?

I'm able to enable journaling on all other volumes under 2TB beside those large ones (9TB). I've tried "mount_hfs -j -c /dev/disk13s3 /Volumes/BadJournal" and when I ran "diskutil info disk13s3" it shows File System is "HFS+ Journaled" which shouldn't be the case and after I ran "disktool -r disk13s3" it reverted back and showed HFS+ only. I've also ran multiple hfs_fsck, diskutil repairDisk, and reboot which don't show any problem and still not able to enable journaling.
Could this be a limitation of diskutil not able to enableJournal for 9TB volumes or volumes with large number of files?
Appreciate any help

How to fully disable Journals in BPC

Once Journals are enabled in an app, how can they be disabled fully so new dimensions can be added? I already changed the flag in the tblApp table, but more is needed.

Sorin,
I did another test and I think you are right that only tblapp needs to be changed, but with a re-logon of the administration console. After changing the tblapp table I did not re-logon and I got the error that the journals where enabled. But after closing the admin console and a new logon it is also working without removing the jrn tables :). So it seems to cache the journal setting of tblapp on the client or something...
Regards,
Joost

How to disable journaling?

Was rummaging through DiskUtility while my 40G external f/w connected and accidentally clicked on enable journaling. Can't seem to find a way to reverse this action in DU. Not sure if I really need journaling on this volume do I, what does it do? It's just a storage space.
Second question is DU also tells me that my f/w drive has "partition: 4" and my internal drive has "partition: 2". What does that mean? I have never partitioned either drive.

don't worry about journaling.
if you wont turn off you must re-format the volume and select "Mac os extended"
for the question number 2:
all drive must be partitioned otherwise you can't use it.
p.s.
http://discussions.apple.com/help.jspa#whyreward
Message was edited by: Federico_82

How do I disable journaling on an external drive that won't mount?

I'm trying to fix a hard drive that gives me the "Invalid content in journal" error. I've run the latest TechTool and Drive Genius and they say the drive is fine, except for its crippling inability to actually mount. Onyx and Cocktail won't touch it until its mounted. Ideas?

It's possible to recover files using recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive.
Also visit The XLab FAQs and read the FAQ on Data Recovery.

Disable Journaling on Software RAID

Hello.
I am running OS 10.7.3 and have four internal drives I would like to create a raid set with using disk utility. I can seem to create a software raid without journalising, is this possible. Creating the raid and option clicking file wont allow journalising to be turned off.
Could anyone advise?
Many thanks, Jim.

RAID is not a replacement for Journaling. If anything a RAID storage system wants Journaling even more.
Journaling is used to make sure file system metadata changes are always complete.
If the system crashes, there is a power failure, the cable between the Mac and the RAID deivces gets kicked out (unplugged), then Journaling means that the file system can just process the journal to make sure that the file system on disk metadata is correct. RAID does not protect you from any of these events.
Without the journal, the file system must run /sbin/fsck_hfs and read every file system metadata structure to make sure that there are no double storage allocations, no lost files, no half written metadata updates, etc... This takes a long time, based on the total number of files and directories stored in the file system.

HOW DO I: disable journaling? make an alias of my user folder? Where is AHT

...on the retail discs?
1. UNCHECKED during install, yet like the last three X's, the install disc installs Journaling anyway.
Xupport could do this, but is now "incompatable" with 10.5
2. Tells me I dont have permission
3 Be darned if I can find it-used to restart and hold down "D"

Apple Hardware Test is on a disc that came with the computer, not on the Leopard (or any other OSX) retail disc. The hardware test does not depend on the operating system on the hard drive, so does not need to be updated for newer operating systems.

Fix - Journaled partition fails to mount (journal magic error)

Before trying to repair or recover a 'Mac OS Extended (Journaled)' disk or partition that fails to mount in the Finder, check whether it is just the journal file that is corrupted. If the partition appears in Disk Utility, the fix is to turn off Journaling. If the partition can now be mounted and your files are present, the problem is solved and journaling can be reenabled.
To confirm a problem with the journal search for console error messages with "journal magic" that occur when tring to mount the partition.
In Disk Utility select the partition that will not mount, hold the Option key and select 'Disable Journaling' in the File menu drop down. It will take a few seconds to complete. Now mount the partition using the Mount button or the File menu. To turn journaling back on (recreating a clean journal file), select Enable Journaling from the File menu or the green toolbar button. (This can also be done through Terminal with the diskutil command. See https://discussions.apple.com/message/12838806#12838806 and search on "journal magic" for details.)
I spent two days trying to recover my data from an external drive. Neither Disk Utility or Disk Warrior 4.4 was able to repair this problem. DU said the partition could not be repaired and DW failed with an "insufficient memory error (2154)". Of course your problem could be a more sever corruption, or the disk does not appear at all in DU, but this is easy to try first.
Hope this is helpful.

Let me be more specific
W2000 SP4 server, MacBook client, trying to mount shared volume thru SMB
-on the same subnet (i.e. lappy next to the server on the same switch) both mount_smbfs and smbclient work OK
-from home smbclient is working, mount_smbfs does not (Err -36)
-from home my wife can mount the shared volume thru Network Neighbours on her XP notebook
-it does not seem to be TCP/IP related - all comp can make FTP or VNC to the server verywhere
-err log of mount_smbfs is "negotiate phase failed: syserr Operation timed out in the console", no idea is there a way to verbose mount_smbfs
-smb.conf looks basic...secure passwords=enable, no nsmb.conf
-W2000 SP4 sever is all default secure policies, running FTP server w/o any issues.
So is there a key on server...or the client which I have to tweak?
Thank you.
MB 2.0 Mac OS X (10.4.9)
MB 2.0 Mac OS X (10.4.9)

To Journal or not to Journal

So I use 10.3.9 as my primary OS. I have 10.4.11 installed on a second ATA drive when I need to use Tiger. That second ATA drive was originally just used for storage of files in addition to an external drive, but now that I have an OS installed on the second ATA drive, are there any concerns I need to take into consideration in regards to moving files back and forth between the two ATA drives?
The main reason I ask is that when I have run DiskUtility it seems that the Disks' Journaling options have changed on their own. I set up both ATA drives to "enable journaling" but it seems like they've been disabled after restarts.
Should I just disable journaling on both drives in both OSs?
Thanks in advance.

Journaling is mostly useful on the startup volume. It isn't usable on a data storage volume. Read the following:
Mac OS X- About file system journaling
File Journaling in OSX Panther Explained
How To Journal a Volume or Repair a Journaled Volume

Journal or not to Journal?

That is my ? I have a new external HDD.
Do I format Journaled or not?
Thanks for your replies.
wtk

Turning on journaling uses slightly more disk space, but increases your chances of recovering data if you run into trouble with the drive later. You can enable and disable journaling on a disk later without reformatting it if you change your mind about journaling in the future.
(8860)

Migration Assistant Error Some files from ".journal" could not be transferred?

Hello, world.
A few days ago I replaced my the 97% full 100GB hard drive in my Dad's Core Duo 2.0GHz Macbook Pro with a 500GB but I received an ominous error at the end of the Migration Assistant transfer. Here are the steps I took:
1. Replaced physical drive.
2. Booted up from OS X Snow Leopard disc.
3. Formatted new drive as OS X Journaled using Disk Utility.
4. Installed OS X Snow Leopard on the new drive.
5. When prompted by OS X Installation, I selected transfer data from another volume.
6. Placed the old drive in an enclosure and connected via USB.
7. At this point I let Migration Assistant take over.
It took an hour and a half or more to transfer the data and everything SEEMS fine. However, at the end I received the following error message from Migration Assistant:
Errors and Warnings:
- 2013-11-02 16:15:49 -0400 Some files from ".journal" could not be transferred
- 2013-11-02 16:15:49 -0400 Some files from ".journal_info_block" could not be transferred
I have searched around but I've been unable to find any information on this. In other instances of these warnings, people seemed to be pointing the finger at moving from PowerPC macs to Intel Macs but this was Intel-->Intel.
I did find someone suggest one other thing in another thread:
"My reading of those error messages indicates that there's something wrong with the journaling files on the PB. I suggest that you disable and reenable it on the PB"
However, I do not know how to enable or disable journaling without reformatting the drive from scratch as journaled or non-journaled.
(post found here: https://discussions.apple.com/message/8675337#8675337)
Question: Should I be worried and does anyone know specifically what this error indicates? Is it possible that my dad's old hard drive was NOT formatted for journaling and MA was looking for these journal related files and unable to find them?
Thank you all in advance for your help,
Nick

What options did you select for Migration Assistant to transfer? For instance, did you select network & computer settings?
"Opt" sounds like the name of a folder, not a file type. On your 13" MacBook, do you have any folder by that name, especially in your home folder?
Also, have you run Disk Utility's *verify disk* check on the MacBook's drive?

Journaling on a PowerBook?

According to Apple, "Journaling is best suited for servers requiring high availability, servers containing volumes with many files..."
That being said, on a PowerBook wouldn't I gain a little bit of speed from my hard drive if I were to disable journaling?

Hi, Joe.
You wrote: "wouldn't I gain a little bit of speed from my hard drive if I were to disable journaling?"IMO, nothing perceptible as measured by human senses.
You're quoting from "Mac OS X: About File System Journaling." That document begins:"Journaling is a feature that helps protect the file system against power outages or hardware component failures, reducing the need for repairs."The repairs in question there are primarily of the Disk Utility > Repair Disk kind.
With Mac OS X 10.3 Panther, journaling was enabled by default on both the Client and Server versions of Mac OS X. It remains so in Tiger. This is because of its benefits. The article in question should be updated so that it also reflects the benefits of journaling for the Client version of Mac OS X — what you and I run on our Macs — in addition to those for the Server version.
Journaling is "a good thing." I recommend keeping Journaling enabled on your startup disk.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

Journaling and Disk Speed

How much speed penalty do you take for having Journaling turned on for your main hard disk?

Not a great deal but there is some reduction in speed. If you work with large files and data access speed is critical to your needs, then you may see a slight benefit from disabling journaling. The trade-off is crash recovery. Journaling helps improve recovery from crashes caused by power outages or sudden shutdowns.
Here are two (slightly old) articles that explain about journaling:
http://www.lafcpug.org/featuresfilejournaling.html
http://docs.info.apple.com/article.html?artnum=107249

Disable Journaling in DiskUtility

Similar Messages

Maybe you are looking for