On Tue, Oct 28, 2014 at 9:09 PM, Anton Aylward 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 8:14 PM, Carlos F. Lange wrote:

On Tue, Oct 28, 2014 at 9:09 PM, Anton Aylward 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