public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Hrishikesh Barua <talonx@gmail.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: Occassional problems with unfreeze
Date: Thu, 25 Sep 2014 17:18:52 +1000	[thread overview]
Message-ID: <20140925071852.GE4758@dastard> (raw)
In-Reply-To: <CAD2VtSgdYt2zxmEeWEXmK2B44BKuB-wRKvX4H=jRA9Rj7pyamA@mail.gmail.com>

On Thu, Sep 25, 2014 at 11:37:47AM +0530, Hrishikesh Barua wrote:
> This happened again yesterday and I took the "echo w >
> /proc/sysrq-trigger".
> Output - http://pastebin.com/rpKNSYY7

How long have you been ignoring these messages for?

[30278027.798067] XFS (xvdj): xlog_space_left: head behind tail
[30278027.798069]   tail_cycle = 1085, tail_bytes = 1041920
[30278027.798070]   GH   cycle = 1085, GH   bytes = 1039296

XFS is emitting that warning several times a second. Isn't that a
pretty good sign that there's something not quite right and is worth
reporting?

Indeed, you are running an old kern (3.2.0-54) which means it won't
have this fix:

3948659 xfs: Account log unmount transaction correctly

And that's likely to be the source of all your freeze/unfreeze
problems because it will eventually hang the log when it's leaked
all it's space in the ether....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2014-09-25  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 11:20 Occassional problems with unfreeze Hrishikesh Barua
2014-07-16 12:47 ` Brian Foster
2014-07-16 13:23   ` Hrishikesh Barua
2014-09-25  6:07     ` Hrishikesh Barua
2014-09-25  7:18       ` Dave Chinner [this message]
2014-09-26 12:02         ` Hrishikesh Barua

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140925071852.GE4758@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=talonx@gmail.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox