On 10/28/2014 11:14 PM, Carlos F. Lange wrote:
On Tue, Oct 28, 2014 at 9:09 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
If you go back though the archives you'll see I've asked about this as well. The answers I got were inconclusive.
Keeping 'top' and later 'iotop' running an a window I determined that it was a disk activity and I thought it was related to BtrFS.
Some while alter a fsck-ing/repair of one of my BtrFS volumes found it was damaged. I cleaned it up, but with the loss of many files. I had backups so it was survivable.
After the 'correction' (reformat the partition and restore) the problem went away.
I use a RAID1 with ext4 in all partitions. I will try to keep an eye on 'iotop'. Thanks.
One reason I used 'top' was that it also showed the load factor and use of each CPU. When those delays occurred to load factor went high! Sometimes so high I couldn't switch back to an application. But it did show the kernel thread that was ... I suspect in a spin loop. -- We must become the change we want to see. - Mahatma Gandhi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org