2008/10/7 Chris Mason <[EMAIL PROTECTED]>: > Ok, its important to understand which parts of the FS are using so much > cpu. It is pretty easy to tell based on the output of top (which procs > are consuming the most time).
Well, it's not about a process doing something intensive, but different procs doing a little i/o. Azurues (reading and writing no more than 40KB/s), Firefox (I've got cache in tmpfs, but history & co. in ~/.mozilla), IM (logs chat), Vim, and so on. So, usually, I see process in D (for too much time, I would say). I though "maybe it takes too long to find free space", I was at 80% full. A couple of hours ago I doubled the free space (now I am using the 33% of the partition). Things are not perfect, but a lot better. Loadavg is < 1, and things seems responsive. Anyway, I'll wait some days and I'll see. I need to use it for sometime to have a good idea. Less free space could be the problem? Ciao, Gelma -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
