Kworker, jbd2 constantly writing to disk

I have read earlier posts on jbd2 journal writing to disk constantly.
These posts are several months old, but since about 4 kernel updates back, I have similar issues, which I cannot resolve.
I have a few systems on Arch Linux and I observe it on two systems with an ext3 partition.
Have tried "noatime, commit=60" in "/etc/fstab".
Tried "Storage=volatile", "RuntimeMaxUse=25M" in "/etc/systemd/journald.conf"
I ran my system with only a bash shell, systemd (212-1) and the kernel (3.13.7-1).
Iotop shows [kworker/*:*] with 0.05% I/O access every other second,
with jbd2 every 10 seconds actually writing to disk (despite commit=60).
I hear my laptop harddrive often clicking so it is kind of annoying.
related discussion on Ubuntu Launchpad
related discussion on Ubuntu forum
related discussion on Arch Linux forum
related discussion on Arch Linux forum
related discussion on Arch Linux forum
A minute or so of kernel debug output, only running systemd and bash shell:
[ 3625.942255] kworker/u16:3(1274): WRITE block 699941776 on sda3 (8 sectors)
[ 3625.942260] kworker/u16:3(1274): WRITE block 700448896 on sda3 (8 sectors)
[ 3625.942265] kworker/u16:3(1274): WRITE block 700710920 on sda3 (8 sectors)
[ 3625.942270] kworker/u16:3(1274): WRITE block 700711032 on sda3 (8 sectors)
[ 3625.942275] kworker/u16:3(1274): WRITE block 700711120 on sda3 (8 sectors)
[ 3625.942280] kworker/u16:3(1274): WRITE block 700724344 on sda3 (8 sectors)
[ 3625.942290] kworker/u16:3(1274): WRITE block 704643080 on sda3 (8 sectors)
[ 3625.942295] kworker/u16:3(1274): WRITE block 704643416 on sda3 (8 sectors)
[ 3625.942300] kworker/u16:3(1274): WRITE block 704643464 on sda3 (8 sectors)
[ 3625.942305] kworker/u16:3(1274): WRITE block 704656376 on sda3 (8 sectors)
[ 3625.942310] kworker/u16:3(1274): WRITE block 705167424 on sda3 (8 sectors)
[ 3625.942319] kworker/u16:3(1274): WRITE block 705691656 on sda3 (8 sectors)
[ 3625.942324] kworker/u16:3(1274): WRITE block 705691992 on sda3 (8 sectors)
[ 3625.942329] kworker/u16:3(1274): WRITE block 705692584 on sda3 (8 sectors)
[ 3625.942334] kworker/u16:3(1274): WRITE block 705715184 on sda3 (8 sectors)
[ 3625.942339] kworker/u16:3(1274): WRITE block 743443568 on sda3 (8 sectors)
[ 3625.942391] kworker/u16:3(1274): WRITE block 743443600 on sda3 (8 sectors)
[ 3625.942397] kworker/u16:3(1274): WRITE block 768345896 on sda3 (8 sectors)
[ 3625.942412] kworker/u16:3(1274): WRITE block 128 on sda3 (8 sectors)
[ 3625.942418] kworker/u16:3(1274): WRITE block 176 on sda3 (8 sectors)
[ 3625.942423] kworker/u16:3(1274): WRITE block 516423696 on sda3 (8 sectors)
[ 3625.942428] kworker/u16:3(1274): WRITE block 516423832 on sda3 (8 sectors)
[ 3625.942432] kworker/u16:3(1274): WRITE block 516952488 on sda3 (8 sectors)
[ 3625.942437] kworker/u16:3(1274): WRITE block 520617984 on sda3 (8 sectors)
[ 3625.942441] kworker/u16:3(1274): WRITE block 520880128 on sda3 (8 sectors)
[ 3625.942446] kworker/u16:3(1274): WRITE block 520884264 on sda3 (8 sectors)
[ 3625.942451] kworker/u16:3(1274): WRITE block 698875920 on sda3 (8 sectors)
[ 3625.942460] kworker/u16:3(1274): WRITE block 699138080 on sda3 (8 sectors)
[ 3625.942465] kworker/u16:3(1274): WRITE block 699138128 on sda3 (8 sectors)
[ 3625.942472] kworker/u16:3(1274): WRITE block 699138784 on sda3 (8 sectors)
[ 3625.942477] kworker/u16:3(1274): WRITE block 699138792 on sda3 (8 sectors)
[ 3625.942481] kworker/u16:3(1274): WRITE block 699139120 on sda3 (8 sectors)
[ 3625.942485] kworker/u16:3(1274): WRITE block 699139128 on sda3 (8 sectors)
[ 3630.956821] kworker/u16:3(1274): WRITE block 520897816 on sda3 (64 sectors)
[ 3640.986172] kworker/u16:0(1137): WRITE block 703786032 on sda3 (128 sectors)
[ 3640.986195] kworker/u16:0(1137): WRITE block 81030272 on sda3 (32 sectors)
[ 3670.367351] jbd2/sda3-8(115): WRITE block 401139384 on sda3 (8 sectors)
[ 3670.367450] jbd2/sda3-8(115): WRITE block 401139392 on sda3 (8 sectors)
[ 3670.367457] jbd2/sda3-8(115): WRITE block 401139400 on sda3 (8 sectors)
[ 3670.367462] jbd2/sda3-8(115): WRITE block 401139408 on sda3 (8 sectors)
[ 3670.367465] jbd2/sda3-8(115): WRITE block 401139416 on sda3 (8 sectors)
[ 3670.367470] jbd2/sda3-8(115): WRITE block 401139424 on sda3 (8 sectors)
[ 3670.367473] jbd2/sda3-8(115): WRITE block 401139432 on sda3 (8 sectors)
[ 3670.367476] jbd2/sda3-8(115): WRITE block 401139440 on sda3 (8 sectors)
[ 3670.367480] jbd2/sda3-8(115): WRITE block 401139448 on sda3 (8 sectors)
[ 3670.367483] jbd2/sda3-8(115): WRITE block 401139456 on sda3 (8 sectors)
[ 3670.367486] jbd2/sda3-8(115): WRITE block 401139464 on sda3 (8 sectors)
[ 3670.367489] jbd2/sda3-8(115): WRITE block 401139472 on sda3 (8 sectors)
[ 3670.367492] jbd2/sda3-8(115): WRITE block 401139480 on sda3 (8 sectors)
[ 3670.367496] jbd2/sda3-8(115): WRITE block 401139488 on sda3 (8 sectors)
[ 3670.367499] jbd2/sda3-8(115): WRITE block 401139496 on sda3 (8 sectors)
[ 3670.367502] jbd2/sda3-8(115): WRITE block 401139504 on sda3 (8 sectors)
[ 3670.367506] jbd2/sda3-8(115): WRITE block 401139512 on sda3 (8 sectors)
[ 3670.367509] jbd2/sda3-8(115): WRITE block 401139520 on sda3 (8 sectors)
[ 3670.367512] jbd2/sda3-8(115): WRITE block 401139528 on sda3 (8 sectors)
[ 3670.658084] jbd2/sda3-8(115): WRITE block 401139536 on sda3 (8 sectors)
Last edited by MDykstra (2014-05-02 09:04:51)

Hi, I'm bumping this since I'm having the same issue. I've been reading the last entire week a lot of threads about that, but they're pretty old and they didn't solved anything. I read this whole thread, tried everything, but nothing of that worked...
https://bbs.archlinux.org/viewtopic.php?id=113516&p=1
https://bugzilla.kernel.org/show_bug.cgi?id=39072
Using commit=60 does nothing. I've disabled tlp too, and used hdparm alone, but neither worked. I'm completely lost.
I'd really appreciate any help, because I'm afraid of breaking my HDD and, unfortunately, I can't afford a new one...

Similar Messages

System process constantly writing to disk

While dealing with another hard drive Problem, ive noticed in Ressource Monitor, that the process 'System' is constantly writing to my main drive.
Sometimes its about 100-200 KiB/sec, today ive watched it for a while, and its writing action was 1.5 MiB/sec for quite a while! Later on it was about 300-400 KiB/sec.
Why does this process write so much data to my disk? Considering Windows running times, this adds up to multiple times the size of my hard drive.
Anyone knows whats going on here?

I have a similar, though less severe issue that hopefully someone can help me with. The System process (pid 4) on my dual core Vaio laptop is writing to disk appx. once every 500ms. This is not performance impacting and I considered it just a
minor annoyance until I recently installed a SSD. Since SSD lifetimes are limited by write/erase cycles, I'm concerned these writes are deteriorating my SSD; not good since they're expensive and I LOVE the performance; boots in appx. 15s, instant IE,
etc.
As with the original poster here, the same activity persists in safe mode. Per SSD optimization guidelines I've read elsewhere, I've disabled all fetching (super, pre, etc.), indexing and all logging except Application, Security & System but the
writes persist.
Im using the latest (very recent) driver from Intel (Intel 5 Series 4 Port SATA AHCI Controller 10.8.0.1003 10/17/2011). I've tried other drivers and while the write pattern seems to change (drive activity light no longer blinks), Resource Monitor
shows they're still there. They also cause an additional issue of consuming CPU (?) which doesn't occur with the "recommended" driver I just mentioned.
Anyone know what these writes may be and if/how I can/should stop them? Thanks.
(BTW, love the caffiene->code quote :-)

Spotlight mds bringing down system, constantly leaking RAM & disk access

Spotlight is going rampant here.
The mds (metadata server, aka Spotlight) process is constantly accessing the disk and writing some data to it, filling it until there is no space left on the device. I cannot find out what file it is writing to. I've tried with fsevener which sadly didn't help.
mds is also eating up all the CPU cycles it can get leaving my system fully loaded at all times.
The mds process is also taking up inceasingly huge amounts of memory, causing permanent swapping of memory and bringing the system to a grinding halt. (Cache Hits go down below 1%, About 250.000 pageins happen per minute.) Memory Footprint is going up to several hundred MB or real RAM.
$ vm_stat
Mach Virtual Memory Statistics: (page size of 4096 bytes)
Pages free: 53166.
Pages active: 275736.
Pages inactive: 135633.
Pages wired down: 59698.
"Translation faults": 10217862.
Pages copy-on-write: 136166.
Pages zero filled: 5983710.
Pages reactivated: 96772.
Pageins: 1236330.
Pageouts: 77113.
Object cache: 24391 hits of 1183451 lookups (2% hit rate)
(This is 95 minutes after reboot. Only running: Finder, Terminal, LaunchBar, Safari, Mail)
This bahaviour goes until the disk is full and I get a "low disk space" warning. Then mds crashes, the system frees up the (temporary?) files written by the process and also frees the RAM taken up by it. Resulting in even more swapping, as the system tries to page-in other processes now. Subseqently the system launches a new mds process and the game starts over.
Things I've tried to remedy:
Rebuilt spotlight index several times. Including totally deleting the .Spotlight-V100 folder on local volumes. Doesn't help, takes about 16 to 20 hours to rebuild on my machine, so is not a thing one wants to just-try.
Reinstalled 10.5.5 Combo Update, doesn't help. Privileges are repaired.
Turn off spotlight completely: Does indeed stop the madness, but now I cannot find anything on my system. So this is not a solution at all.
I've tried to keep the index small by excluding more and more stuff in the privacy settings of the Spotlight PreferencePane. This doesn't solve the problem either.
My System:
PowerBook G4 1.5GHz
2GB RAM (Maximum) (Tested with ASD ok, Rember ok. Different RAM modules, also ok.)
160GB HD (5GB free) (SMART ok, Blockscan ok, Filesystem ok, File privileges ok)
Mac OS X 10.5.5 (9F33) including Security Update 2008/007 (no further updates available)
Any help or suggestions are welcome. I'm happy to provide any further details you may need.
Best regards
Pepi

J D McIninch wrote:
This probably isn't Spotlight so much as one of the index plugins (mdimporters). Spotlight itself is very robust, however, all it takes is a single bad indexing plugin. MDS, basically, identifies a file type and loads in a list of plugins that are registered for that file type and executes a routine in the plugin to grab the metadata. If the plugin is improperly written, it can go haywire.
Thanks for the suggestion, I already had checked that.
I don't have any custom (read non-apple provided) Spotlight or QuickLook Plug-Ins on my system. So it is unlikely that it is related to a custom .mdimporter Plug-In. (Might be a buggy Apple one going rampant though.)
I've personally found Spotlight to be quite a solid technology as well. Just the user interface provided by Apple is terrible and especially useless in the Finder (Taking away functionality, or making it horrific to use since Tiger… but that is another story.)
What was the last application that you installed prior to it going crazy? Perhaps one of the last 2-3...
Failing that, you can wipeout the metadata database for a Volume like so (from Terminal.app):
*sudo mdutil -E /Volumes/yourvolumehere*
... or '/' in place of '/Volumes/...' for the local disk. You can turn off metadata indexing for a volume entirely like so:
As I already said, rebuilding the index from scratch doesn't help. Completely deleting it, and rebuilding doesn't remedy as well.
*sudo lsof | grep mdimporter*
... which might help you understand what's being used to index, and this:
/System/Library/Spotlight/Chat.mdimporter/Contents/MacOS/Chat
/System/Library/Spotlight/iCal.mdimporter/Contents/MacOS/iCal /System/Library/Spotlight/Mail.mdimporter/Contents/MacOS/Mail
Nothing fancy here.
I ran a diff on my daily installation report and it gives me these app, that have been modified (Installed or updated in the last 31 days.)
/Applications/Address Book.app
/Applications/Adium.app
/Applications/AppleScript/Script Editor.app
/Applications/Automator.app
/Applications/Carbon Copy Cloner.app
/Applications/Dashboard.app
/Applications/Dictionary.app
/Applications/DVD Player.app
/Applications/Expose.app
/Applications/Flip4Mac/WMV Player.app
/Applications/iCal.app
/Applications/iChat.app
/Applications/iPhoto.app
/Applications/iSync.app
/Applications/iTunes.app
/Applications/JollysFastVNC.app
/Applications/Mail.app
/Applications/OmniFocus.app
/Applications/Photo Booth.app
/Applications/Preview.app
/Applications/Safari.app
/Applications/Skitch.app
/Applications/Spaces.app
/Applications/StuffIt/StuffIt Expander.app
/Applications/StuffIt 12/StuffIt Expander.app
/Applications/Time Machine.app
/Applications/Utilities/Activity Monitor.app
/Applications/Utilities/Bluetooth File Exchange.app
/Applications/Utilities/ColorSync Utility.app
/Applications/Utilities/Directory Utility.app
/Applications/Utilities/Directory.app
/Applications/Utilities/Disk Utility.app
/Applications/Utilities/Keychain Access.app
/Applications/Utilities/Migration Assistant.app
/Applications/Utilities/Network Utility.app
/Applications/Utilities/Podcast Capture.app
/Applications/Utilities/RAID Utility.app
/Applications/Utilities/Remote Install Mac OS X.app
/Applications/Utilities/Terminal.app
/Applications/Utilities/VoiceOver Utility.app
/Applications/Utilities/X11.app
/System/Library/CoreServices/Apple80211Agent.app
/System/Library/CoreServices/AppleFileServer.app
/System/Library/CoreServices/Automator Launcher.app
/System/Library/CoreServices/Automator Runner.app
/System/Library/CoreServices/AVRCPAgent.app
/System/Library/CoreServices/Bluetooth Setup Assistant.app
/System/Library/CoreServices/BluetoothAudioAgent.app
/System/Library/CoreServices/BluetoothUIServer.app
/System/Library/CoreServices/CCacheServer.app
/System/Library/CoreServices/CoreServicesUIAgent.app
/System/Library/CoreServices/DiskImageMounter.app
/System/Library/CoreServices/Dock.app
/System/Library/CoreServices/File Sync.app
/System/Library/CoreServices/FileSyncAgent.app
/System/Library/CoreServices/Finder.app
/System/Library/CoreServices/Help Viewer.app
/System/Library/CoreServices/Installer.app
/System/Library/CoreServices/Kerberos.app
/System/Library/CoreServices/KerberosAgent.app
/System/Library/CoreServices/loginwindow.app
/System/Library/CoreServices/ManagedClient.app
/System/Library/CoreServices/NetAuthAgent.app
/System/Library/CoreServices/Network Diagnostics.app
/System/Library/CoreServices/Network Setup Assistant.app
/System/Library/CoreServices/OBEXAgent.app
/System/Library/CoreServices/ODSAgent.app
/System/Library/CoreServices/PreferenceSyncClient.app
/System/Library/CoreServices/Problem Reporter.app
/System/Library/CoreServices/RemoteManagement/ARDAgent.app
/System/Library/CoreServices/Screen Sharing.app
/System/Library/CoreServices/Spotlight.app
/System/Library/CoreServices/SystemUIServer.app
/System/Library/CoreServices/VerifiedDownloadAgent.app
As you can see, there is nothing special in there as well. Just Apple Apps, and a few non-suspicious ones from my point of view.
Tom in London wrote:
rather than mess around with all of this and maybe fix it until the next Spotlight problem manifests itself, why not just disable Spotlight with Spotless, and use EasyFind instead? Easyfind finds everything, has more options, is reliable, and doesn't cause problems .... and doesn't eat up any space on your hard drive.
...and doesn't find what I need. Thanks for the suggestions though. As I said, totally disabling Spotlight is not an option. I'll stay far away from mysterious tools, as I know what I am doing in a Terminal.
Best regards
Pepi

Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY . Looking for solution.

Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY . Looking for solution.

Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash, if possible.
Triple-click anywhere in the line below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
find ~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $ 2>&- | wc -l | pbcopy
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
The output of the command will be a number. It's automatically copied to the Clipboard. Please paste it into a reply.
The Terminal window doesn't show the output. Please don't copy anything from there.

Why is Premiere 6 giving a "Error writing file (disk full?)" message?

Hello helpful experts,
I'm using Premiere 6 on a Windows 7 machine.
I have a file imported in to the timeline and it is set to play in reverse via the speed setting being set to -100 and it plays back in the preview window correctly, in reverse, when I click the play button.
But when I do a "File>Export Timeline>Movie" command I get an error message saying "An error occurred while making the movie. Error writing file (disk full?)"... but my hard drive is not nearly full, with over 30 gigs left open on it... and my RAM usage gadget shows over half of my RAM capacity is unused.
Now previously, weeks ago on a different project, I was getting this same error message for a while when I would hit enter to preview my movie on the timeline (but that worked itself out somehow and eventually stopped giving me that error message). But when I went to save and export, then I would not get the error message... now, it is just the opposite... I'm now getting the error message when trying to do an export and save the movie.
And also now when I hit enter to preview, as opposed to just clicking the play button on the preview window, Premiere is going through the process of saving the movie since it is saving a temporary preview file... hopefully, since I'm getting this error message, I can find the temporary preview file and save it as my exported AVI file.
But I still shouldn't be getting this error message when trying to save, or when trying to preview, as I did for a while a couple of weeks ago.
Does anyone know about the erroneous error message that says, "An error occurred while making the movie. Error writing file (disk full?)"
Thanks,
numetro

Depending on your hard drive size, P6 may be confused... since drives were not as large when it was written
For Win7 64bit Pro or Ultimate (or Enterprise?) this is ONE example of using Virtual XP http://forums.adobe.com/thread/702693?tstart=0
This is saved from an OLD message that may help
File size limits by disk format type
Fat = 2 Gig maximum file size
Fat32 = 4 Gig
NTFS = ?Terrabytes?
Message saved from Premiere forum
John Acocks - 07:52am Apr 17, 2003 Pacific
I am unable to complete captures because I get a message
that says "capture stopped because disk was full." What
does this mean?
Daniel Conklin - 08:02am Apr 17, 2003 Pacific (#1 of 2)
If you are using a Pinnacle card, a possible solution to
this is to right click on the recycle bin, and set the
percentage on your media drive to less than 2%.
There a several other possible causes as well, but you
need to supply some info about your system. How are you
capturing and what format is your video? How big is
your hard drive?
Jeff Schell - 09:57am Apr 17, 2003 Pacific (#2 of 2)
this is one of my favorite error messages. Basically,
you've chosen an incorrect setting in your DV settings.
(Odds are you have DV settings). If so, read on:
1. The DV format is very rigid. Meaning that if you
   make changes to the format, it cannot export as
   requested, because your movie file must match every
   single spec exactly.
2. When Premiere goes to export a project, the DV codec
   says "Whoa. I can't do anything, because the settings
   don't match."
3. Then Premiere comes back to you and has to report an
   error. (Don't shoot the messenger). Unfortunately,
   Premiere doesn't know why it wasn't able to export a
   movie. So it says to you, "Um... I can't make the movie.
   Um... maybe your hard drives are full?"
It's a complete guess. And has nothing to do with your harddrives.
Check your project settings and/or your export settings. Make
sure you have chosen one of the "presets" that will specify
every correct setting for you. Make sure it is one of the DV
presets, if you are using DV video, or make sure it is one of
the presets supplied by your capture card manufacturer (in this
case I'm going to guess Pinnacle or Matrox.)
To choose a preset, go to Project > Settings Viewer, and then
click on the project settings column, and then click 'load' to
load a correct preset. Do the same with export settings.

Why does iPhoto say "Error writing to disk"?

When I go on iPhoto I click on the "import all" button and try imorting my pictures from my iPhone to my mac and after a while of importing it completely stops and a window pops out saying "Error writing to disk" and I really don't know what to do to this solution.

Hello JJ,
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)

Insufficient disk space / Error writing to Disk: when using photo library manager

First I couldn't open my iphoto library (again!) so I am rebuilding my library (again- 4th time). NOW I'm told I donot have sufficient disk space to import photos.
Using OSX 10-9-5 Memory 4GB
And just as I'm writing this I get Error Writing to disk memo
iPhoto cannot import your photos because there was a problem writing to the volume containing your iPhoto library.

Freeing Up Space on The Hard Drive
1. See Lion/Mountain Lion/Mavericks' Storage Display.
2. You can remove data from your Home folder except for the /Home/Library/ folder.
3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
4. Also see Freeing space on your Mac OS X startup disk.
5. See Where did my Disk Space go?.
6. See The Storage Display.
You must Empty the Trash in order to recover the space they occupied on the hard drive.
You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.
If you select the disk icon for your hard drive on the Desktop, then Press COMMAND-I to open the Get Info window. In the upper panel it will show your drive's space statistics - Capacity, Used, and Available. It is the latter you are interested in to see how much space is left on the drive. If you have less than 1 GB or so, then you must stop trying to write to the drive or you may corrupt it completely.

IMovie - Console message: Error writing to disk! App indicates nothing..

My daughter spent hours working in iMovie v7.1.4, building a project. The system choked, in the end we went through a reboot and tried to reopen the project file. It indicated a 0s duration, with no pictures, music, etc...
Upon research, I notice that in the console messages, there are about 100+ messages in the following format. The application never once indicated there was an issue.
iMovie [[<PID>]] Project '/Users/<user>/Movies/iMovie Projects.localized/My First Project.rcproject' - save: Error writing to disk!
She was working in a user account that has parental restrictions. Not sure if this has any bearing...
Has anyone else ever had an issue like this? Where console indicates write errors, yet the application does not.

I would run Disk Utility and repair permissions. If that does not fix it, check to make sure that she has write access to the drive.

Mail program is CONSTANTLY writing changes to disk, and it bogs EVERYTHING down...

...everytime I open it, it starts redoing this (whatever it is) and it slows things down to a crawl. The other strange issue is when I send an email, esp with an attachment, it stays as a draft, even though it has been sent. Have the latest updates, and have been searching this forum regularly.
Hope they fix this, but in the meantime, any suggestions?
Cheers,
Cameron

Mavricks Mail is Writing Changes to Disk for gmail every reboot, still!
There was an update that was supposed to fix this. It hasn't. Is there some resinstall/delete prefs/stop-start I can do to get this to stop?
This needs to be fixed. I'm leaving for overseas trip and can't be sucking up bandwidth re-downloading 30,000 messages every day. Maybe I should have gmail forward to icloud, then just read icloud? WTH?

Firefox is constantly writing on the hard disk

When Firefox is open, the computer is writing on the hard disk every 3 seconds and it slows the computer quite a bit.

The same here. I have windows 8.1 64 bit too and i think it started quite recently... Any way to stop it?

PSE 8 - How do I fix the error message: An error has occurred reading files or writing to disk...?

Hello
I am using Photoshop Elements 8 on Windows 7 (64 bit). I have all my photos stored on an external hard drive connected by usb. The photos were transferred onto the HDD from a Windows XP machine. I bought a new computer so I installed Photoshop 8 and imported all my photos to the organiser from the HDD. I have also taken some photos yesterday which I have uploaded to the HDD.
Now, when I want to delete a photo I check the box to say I want it to be deleted on the hard disk and I get the error message: 'An error has occured while reading files or writing files to disc. The disc may be full or there may bea problem with the source media.' This does not happen with the photos I uploaded yesterday, only the ones which were put onto the HDD from the XP machine.
Please could someone help? I have tried the File>Catalog> repair and optimise functions. I have reinstalled the software. It still does the same.
Thank you in advance
Dave

David GW wrote:
The error message goes on to say, Please check your device settings or consult your device documentation regarding resolving writing errors. Which device do you think they are referring to?
Sorry, but I would have thought that this was rather obvious! The only device capable of being written to under these circumstances is your CD drive; after all, it's a CD you are trying to create...
You have two potential major causes of problems here. The most common cause of these difficulties is the disks themselves - you only need a batch with poor reflectivity to cause all sorts of read errors, so that's the first thing to try - using a different brand of disk to write to. The second thing you have to realise is that CD writers have a finite life - the lasers in them simply don't last for ever, and towards the end of their lives the power behaviour tends to be a bit erratic, and it tends to fall off somewhat - which causes the same sorts of errors, simply because the dye doesn't get evaporated efficiently. This causes mis-formed pits, hence the read errors. The only solution here is to install a new drive.
When it comes to reading, commercial CDs have a much higher reflectivity than ones you write yourself, so often these will play whilst your own will fail - a common cause of confusion, this. But it's worth checking; if you get failures to reproduce all of the tracks from a commercial pressed CD, then almost certainly your drive is failing.

NotSerializableException when writing to disk

Hi,
I am having a problem with simply writing an object to disk. Have a class called DataHolder which implements serializable. This class consists of about a dozen strings and nothing else:
class DataHolder implements Serializable{
String a="abc";
String b="def";
etc..........
I add instances to an ArrayList then pull them out.
DataHolder holder=(DataHolder)list.get(i);
When I try to write them to disk with:
ObjectOutputStream objectOut = new ObjectOutputStream(new FileOutputStream("myFile"));
objectOut.writeObject(holder);
I get an error:
java.io.NotSerializableException: DataHolder
I know there must be a simple explanation for this but I don't see it. I think DataHolder should be serializable since it implements Serializable, right?
thanks
john

Hi john,
The error[b] java.io.NotSerializableException:
thrown when an instance is required to have a Serializable interface. The serialization runtime or the class of the instance can throw this exception.
For this the argument should be the name of the class.
Try by doing
class DataHolder implements java.io.Serializable {
String a="abc";
String b="def";
Hope this will help you.
Regards,
Anil.
Tehnical Support Engineer.

Safari 4 constant writing to disk

I have just put safari 4 on an iBookG4 with tiger.11 and 700 odd mb ram.
If I leave the computer for a few minutes with safari running (not necessarily even a window open), I can hear constant and rhythmic writing to the disk. I check activity monitor and safari there is indeed 3MB/s writing going on and Safari is using a high % of CPU (say 40%).
Not that I don't enjoy rhythmic devices, but the noise is akin to when you stomach is gurgling and churning after eating something bad, but mainly I don't think Safari should be doing this!
I think it might be indexing or building the coverflow thumbnails, but should safari tell me about this first?
Anyone else get this?

Just normal activities, but it would do it quicker if you had more RAM!

IPhoto error writing to disk

I'm trying to import photos into iPhoto and I get this : iPhoto cannot import your photos because there was a problem writing to the volume containing your iPhoto library.
I've also gotten a message when trying to import from my iPhone4 that the photos are unregonizable or wrong format.

Sounds like some kind of corruption on your disk - maybe repair permissions (a wild guess)? If no one answers soon, there is a separate iPhoto Forum that might be of help:
https://discussions.apple.com/community/ilife/iphoto

Writing to disk with Oracle...

Hi,
does Oracle use the operating system input/output system calls in order to write/read from/to disk, or does it use its own routines. Does it use the caching mechanisms of UNIX-like systems? Since Oracle has its own caching mechanisms for writing asynchronously to the datafiles, is Oracle using the operating system specific caches?
Thanks in advance

If you are creating Oracle data files on a standard Linux file system, Oracle will use the operating system commands to read and write data. Oracle also has the ability to use "raw" disks, where the operating system does not have a file system, using its own I/O routines. Raw disks are historically slightly faster, but more effort to manage. Oracle can also use ASM in 10g, which adds to the options and the complexity.
I believe you can enable asynchronous I/O on Linux, but I'm not expert enough to really understand how that interacts with the OS caching algorithms.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Kworker, jbd2 constantly writing to disk

Similar Messages

Maybe you are looking for