You are not logged in.
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.
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)
Offline
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...
Offline
Switching 'systemctl emergency' I only have systemd-journald going, which I configured to store in volatile memory.
Still [kworker/*:*] is writing to disk regularly. I suspect a kernel bug. At this point I like to hear if more people can confirm this for ext3 partitions.
At least 2 out of 3 Arch systems show this clearly for me.
Offline
I haven't done as much testing as you, but I believe I have the same issue with ext4 partitions.
Offline
I'm also experiencing this issue. I trawled google extensively, tried noatime, commit=60. I ran fsck on all partitions. I still have my hdd grinding every 5s. kernel 3.13.9
Offline