[opensuse] file browsing (dolphin and konqueror) hangs for 2 min periodically
I have a 13.1 installation with KDE that is showing some annoying behaviour. Every 10 minutes or so dolphin just hangs for approx. 2 minutes and does not do anything. The entire window freezes and jsut buffers every click I do. There is no process keeping it busy and no indication what it is waiting for. When the freeze happens, all instances of dolphin and of konqueror (as file browser) also freeze. When the freeze passes, everything works fine and fast. I have no clue what to look for. What could be causing it? -- Carlos F Lange Gaúcho nas Pradarias http://goo.gl/fvVhr -- Recursive: Adj. See Recursive. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/28/2014 10:01 PM, Carlos F. Lange wrote:
I have a 13.1 installation with KDE that is showing some annoying behaviour. Every 10 minutes or so dolphin just hangs for approx. 2 minutes and does not do anything. The entire window freezes and jsut buffers every click I do. There is no process keeping it busy and no indication what it is waiting for. When the freeze happens, all instances of dolphin and of konqueror (as file browser) also freeze. When the freeze passes, everything works fine and fast.
I have no clue what to look for. What could be causing it?
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. My rootFS is a BtrFS but it has never given me any problems. Curios. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. -- Carlos F Lange Gaúcho nas Pradarias http://goo.gl/fvVhr -- Recursive: Adj. See Recursive. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 10/28/2014 8: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.
Well, I had the same problem with ext4. In my case the disk had developed bad sectors. The long pauses we caused by the system trying and trying and trying to read the disk. I used smartctl to determine that the disk was going bad, and had already reassigned sectors automatically. I stopped using the machine and I I bought a new drive. I copied everything that I could off the drive onto a new drive in an external enclosure. I used clonzilla bootable CD to do this copy, but there are any number of other utilities that could be used. The key point is STOP using that disk, while it is still operating, because the more you try to run from it the deeper you dig your grave. You need to save its remaining hours for the recovery. There is some minor dicking around with grub2 to to tell it the id of the new boot disk. (see its name while booting with a Recovery CD, photograph the screen with your cell phone then put the drive in as the boot drive and hand edit boot.list entry. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Tue, Oct 28, 2014 at 9:45 PM, John M Andersen <jsamyth@gmail.com> wrote:
I use a RAID1 with ext4 in all partitions. I will try to keep an eye on 'iotop'. Thanks.
Well, I had the same problem with ext4.
In my case the disk had developed bad sectors. The long pauses we caused by the system trying and trying and trying to read the disk. I used smartctl to determine that the disk was going bad, and had already reassigned sectors automatically. I stopped using the machine and I bought a new drive.
OK, this might be a possibility. Since my system does not show high loads, when the file browsers are hanging and nothing else in the machine slows down, suspecting the disks is fair. I do have a RAID1 and I checked that both disks are active and synchronized. I had never used smartctl (thanks for the hint), but the test shows both disks are old (Old_age), but still working without errors. There is also no disk errors in /var/log/messages, where I am used to find errors when a disk goes bad. Anyway, tomorrow I will open the case and check if the disks are spinning, when dolphin hangs. -- Carlos F Lange Gaúcho nas Pradarias http://goo.gl/fvVhr -- Recursive: Adj. See Recursive. -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Anton Aylward -
Carlos F. Lange -
John M Andersen