100% I/O usage due to jbd2

Bug #1305237 reported by Volkan Gezer
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

I have 14.04 Beta 2 64-bit and Intel i7 Processor with 2.2Ghz clock, 4 GB RAM and 500 GB Harddrive.

After using Ubuntu for some time, everything goes so slow and I cannot even move my USB mouse cursor, but only touchpad. Not possible to open even a terminal window.

Here is the iotop output:

http://pastebin.ubuntu.com/7227394/

Also the cpu usage is around 3% only by chromium.

I unmounted all ntfs disks (I even don't have sda8), but the problem is the same.
---
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: volkan 4336 F.... pulseaudio
                      volkan 5310 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-04-16 (357 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300V3A/300V4A/300V5A/200A4B/200A5B
Package: linux 3.11.0.18.19 [origin: unknown]
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=69512adb-ab15-463f-85d4-29a19b1e8668 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.126
StagingDrivers: zram
Tags: trusty third-party-packages staging
Uname: Linux 3.13.0-20-generic x86_64
UnreportableReason: Bu resmi bir Ubuntu paketi değil. Lütfen herhangi bir üçüncü parti paketini kaldırıp tekrar deneyin.
UpgradeStatus: Upgraded to trusty on 2014-03-10 (30 days ago)
UserGroups: adm audio cdrom debian-tor dip libvirtd lpadmin netdev plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 11/02/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 10FI
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 300V3A/300V4A/300V5A/200A4B/200A5B
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr10FI:bd11/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300V3A/300V4A/300V5A/200A4B/200A5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn300V3A/300V4A/300V5A/200A4B/200A5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300V3A/300V4A/300V5A/200A4B/200A5B
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key trusty
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1305237

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Volkan Gezer (volkangezer) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected staging third-party-packages
description: updated
Revision history for this message
Volkan Gezer (volkangezer) wrote : BootDmesg.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : CRDA.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : Dependencies.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : IwConfig.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : Lspci.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : Lsusb.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : ProcEnviron.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : ProcModules.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : PulseList.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : RfKill.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : UdevDb.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : UdevLog.txt

apport information

Revision history for this message
Volkan Gezer (volkangezer) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Volkan Gezer (volkangezer) wrote :

Yes, it was an upgrade from 13.10 into 14.04 beta2. I don't know what the kernel version before I upgrade was, though.

Revision history for this message
Volkan Gezer (volkangezer) wrote :

Fstab file contents (for reference=:

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>

#Entry for /dev/sda6 :
UUID=69512adb-ab15-463f-85d4-29a19b1e8668 / ext4 errors=remount-ro 0 1
#Entry for /dev/sda4 :
UUID=345275CA527590FA /media/SAMSUNG_REC ntfs-3g defaults,locale=tr_TR.UTF-8 0 0
#Entry for /dev/sda1 :
UUID=26302889302861D3 /media/SYSTEM ntfs-3g defaults,locale=tr_TR.UTF-8 0 0
#Entry for /dev/sda2 :
UUID=42AED055AED042D9 /media/volkan/42AED055AED042D9 ntfs-3g defaults,nosuid,nodev,locale=tr_TR.UTF-8 00
#Entry for /dev/sda5 :
UUID=E0DA3E43DA3E15EE /media/volkan/E0DA3E43DA3E15EE ntfs-3g defaults,nosuid,nodev,locale=tr_TR.UTF-8 00

Revision history for this message
Volkan Gezer (volkangezer) wrote :

How often should this process (or whatever it is) be active? I unmounted all ntfs devices, but it still exists there. After the first boot with the newest kernel, it seems it is blocking less (between 25% to 85%) but it is the highest I/O using process in every 5-10 seconds.

Revision history for this message
Volkan Gezer (volkangezer) wrote :

No. Today it is seen again. I am adding a tag

tags: added: kernel-bug-exists-upstream
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Volkan Gezer (volkangezer) wrote :

Just to make it clear: I formatted and did a fresh install of Kubuntu 14.04. The problem has been solved.

Probably it was due to some configuration problems.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.