This happened again yesterday and I took the "echo w > /proc/sysrq-trigger".
Output - http://pastebin.com/rpKNSYY7On 16 July 2014 18:53, Hrishikesh Barua <talonx@xxxxxxxxx> wrote:
On 16 July 2014 18:17, Brian Foster <bfoster@xxxxxxxxxx> wrote:That one looks like a freeze hang whereas you see an unfreeze hang.
You are right. My bad.
Perhaps similar to this:
https://bugzilla.redhat.com/show_bug.cgi?id=1052004Looks like I can't access that bug report, even after logging in. The error message says "Most likely the bug has been restricted for internal development processes and we cannot grant access."
Do you have the hung task output for when this occurs (echo w >
>
> No resolution seems to have happened there. Is this a known bug, or has it
> been fixed since (I'm running xfsprogs 3.1.7) ?
>
/proc/sysrq-trigger)?No, but I'll get it the next time it happens. Thanks for the tip.
Brian
> Regards
> Hrish
> _______________________________________________
> xfs mailing list
> xfs@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs
--
You can't be normal and expect abnormal returns - Jeffrey Pfeffer
------------------------------------------
http://code.deepinspace.net
------------------------------------------
_______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs