Re: Debugging system freezes on filesystem writes

[Jan Kara <jack@suse.cz>]

On Wed 20-02-13 13:40:03, Marcus Sundman wrote:
> On 20.02.2013 10:42, Marcus Sundman wrote:
> >On 05.12.2012 17:32, Jan Kara wrote:
> >>   I see. Maybe you could have something like
> >>while true; do echo w >/proc/sysrq-trigger; sleep 10; done
> >>   running in the background?
> >
> >Sure, but I suspect it'll take until the worst is over before it
> >manages to load and execute that "echo w".
> 
> Here is a big run of sysrq-triggering, all while I was uncompressing
> a big rar file causing the whole system to be utterly unusable.
> NB: Even with realtime I/O-priority the sysrq couldn't be triggered
> between 12:41:54 and 12:42:49, as you can see from the dmesg-3.txt
> file.
> 
> $ sudo ionice -c 1 su
> # ionice
> realtime: prio 4
> # while true; do sleep 10; echo w >/proc/sysrq-trigger; done
> ^C
> # tail -n +1700 /var/log/syslog >dmesg-3.txt
> 
> http://sundman.iki.fi/dmesg-3.txt
  Thanks for the traces. I was looking at them and we seem to be always
waiting for IO. There don't seem to be that much CPU load either.

I'm actually starting to suspect the SSD in your laptop. The svctm field
from iostat output shows it takes 1 second on average to complete an IO
request. That is awfully slow given one request has ~180 KB of data on
average. Ah, one more idea - can you post your /proc/mounts please?

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR