[Bug 282704] KDE 4.7 is very slow on ext3 root partition

Nicola Mori nicolamori at aol.com
Sat Nov 19 16:09:07 GMT 2011


https://bugs.kde.org/show_bug.cgi?id=282704





--- Comment #20 from Nicola Mori <nicolamori aol com>  2011-11-19 16:09:06 ---
I found the way to mount filesystem as journal or writeback. As explained here:

http://wiki.centos.org/HowTos/Disk_Optimization

"To use any other mode than 'data=ordered' on the root file system, you have to
pass the mode to the kernel as a boot parameter, by adding it to the kernel
command line: rootflags=data=writeback."

So I did it and I've been able to mount using kriteback and the journal. But it
did not help at all, I see the same regardless of any setting.

But in doing this I found a very interesting thing. I set writeback, then
rebooted and logged into console. I checked the mount by typing "cat /etc/mtab"
and this is what I got for root partition:

/dev/disk/by-uuid/a6010950-6a72-4422-98a3-0e9f7e2a49f7 / ext3
rw,noatime,errors=continue,barrier=1,data=writeback

OK, it looked fine so I typed startx and started KDE. After KDE's start, I
checked again /etc/mtab and I was really surprised to see this:

/dev/disk/by-uuid/a6010950-6a72-4422-98a3-0e9f7e2a49f7 / ext3
rw,noatime,data=writeback,commit=0 0 0

It seems that something in the KDE satrtup procedure changes the mount options.
I cannot figure out how this can happen, nor if it is some mistake made by me.
But I tried many times and the outcome is always the same. I even cannot say if
this is the source of my problems or not, but it is quite weird in my opinion.
I also checked that this does not happen when using ext4.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list