Richmond wrote:
David C. Rankin wrote:
Is this a bug, a feature, a valgrind special environment issue? If I recall the earlier thread (there have been a couple - Why swap?, etc.. recently), James or whoever it was was seeing similar unresponsiveness during the swap. I think it might have been me. I ended up replacing the drive which seemed to improve things. But since then I have switched to a different computer and saw the same unresponsiveness yesterday. I had google chrome running.
One thing I didn't check and wished I had (on that old drive) was the SMART data to see if there were read errors.
Looking at this current machine I see these: smartd[1093]: Device: /dev/sda [SAT], 16075 Currently unreadable (pending) sectors smartd[1093]: Device: /dev/sda [SAT], 36223 Offline uncorrectable sectors (changed +1) smartd[1093]: Device: /dev/sda [SAT], 16075 Currently unreadable (pending) sectors smartd[1093]: Device: /dev/sda [SAT], 36223 Offline uncorrectable sectors smartd[1093]: Device: /dev/sda [SAT], 16075 Currently unreadable (pending) sectors smartd[1093]: Device: /dev/sda [SAT], 36226 Offline uncorrectable sectors (changed +3) smartd[1093]: Device: /dev/sda [SAT], 16075 Currently unreadable (pending) sectors smartd[1093]: Device: /dev/sda [SAT], 36226 Offline uncorrectable sectors smartd[1093]: Device: /dev/sda [SAT], 16075 Currently unreadable (pending) sectors smartd[1093]: Device: /dev/sda [SAT], 36226 Offline uncorrectable sectors I can't check yesterday though, journalctl says there is no persistent journal. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org