Re: task blocked for more than 120 seconds

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Apr 21, 2012 at 10:29:32AM +1000, Dave Chinner wrote:
> On Fri, Apr 20, 2012 at 09:58:20AM -0400, Josef 'Jeff' Sipek wrote:
...
> > Right.  Here's the output from a few minutes ago (I removed the empty lines
> > and redundant column headings):
> 
> Thanks, that makes it easy to read ;)

Yeah, I don't know who's brilliant idea it was to output the headings every
time.

> Now comes the "more data needed" bit. I still need the sysrq-w
> output,

D'oh!  Totally forgot to put that up somewhere.

http://31bits.net/download/xfs_log.gz

Sadly, it looks like the kernel's ring buffer wrapped while dumping the ~180
stacks.

> but also given the length of the incident, some other data
> is definitely needed:
> 
> 	- a 30s event trace - it'll compress pretty well
> 	  (trace-cmd record -e xfs* sleep 30; trace-cmd report > output.txt)

Hrm... Time to figure out how to get ftrace going on Gentoo.  I don't see an
obvious package to install to get trace-cmd.

> 	- vmstat 1 output for the same period
> 	- output of /proc/meminfo at the same time
> 	- the same iostat output for comparison.

Jeff.

-- 
I'm somewhere between geek and normal.
		- Linus Torvalds

_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs


[Index of Archives]     [Linux XFS Devel]     [Linux Filesystem Development]     [Filesystem Testing]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux