From: Dave Chinner <david@fromorbit.com>
To: Mark Tinguely <tinguely@sgi.com>
Cc: Juerg Haefliger <juergh@gmail.com>, xfs@oss.sgi.com
Subject: Re: Still seeing hangs in xlog_grant_log_space
Date: Fri, 18 May 2012 19:37:43 +1000 [thread overview]
Message-ID: <20120518093743.GV25351@dastard> (raw)
In-Reply-To: <4FAB237D.5050608@sgi.com>
On Wed, May 09, 2012 at 09:10:05PM -0500, Mark Tinguely wrote:
> On 05/09/12 16:07, Mark Tinguely wrote:
>
> I notice in the trace_report_180secs.txt file, lsn (ail_push and the
> ungrants) displays are not correct. It acts like the BLOCK_LSN() is
> shifting too much.
What do you mean by "not correct"?
> Block sequence numbers never make it too far
> above 1100 before incrementing the cycle. I think the problem is the
> trace not the sequence numbers.
The log is only 576 filesystem blocks (which are 1k in size) long,
which means 1152 sectors, so the LSN block number portion will never
go above 1152. It looks correct to me....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-18 9:37 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 12:09 Still seeing hangs in xlog_grant_log_space Juerg Haefliger
2012-04-23 14:38 ` Dave Chinner
2012-04-23 15:33 ` Juerg Haefliger
2012-04-23 23:58 ` Dave Chinner
2012-04-24 8:55 ` Juerg Haefliger
2012-04-24 12:07 ` Dave Chinner
2012-04-24 18:26 ` Juerg Haefliger
2012-04-25 22:38 ` Dave Chinner
2012-04-26 12:37 ` Juerg Haefliger
2012-04-26 22:44 ` Dave Chinner
2012-04-26 23:00 ` Juerg Haefliger
2012-04-26 23:07 ` Dave Chinner
2012-04-27 9:04 ` Juerg Haefliger
2012-04-27 11:09 ` Dave Chinner
2012-04-27 13:07 ` Juerg Haefliger
2012-05-05 7:44 ` Juerg Haefliger
2012-05-07 17:19 ` Ben Myers
2012-05-09 7:54 ` Juerg Haefliger
2012-05-10 16:11 ` Chris J Arges
2012-05-10 21:53 ` Mark Tinguely
2012-05-16 18:42 ` Ben Myers
2012-05-16 19:03 ` Chris J Arges
2012-05-16 21:29 ` Mark Tinguely
2012-05-18 10:10 ` Dave Chinner
2012-05-18 14:42 ` Mark Tinguely
2012-05-22 22:59 ` Dave Chinner
2012-06-06 15:00 ` Chris J Arges
2012-06-07 0:49 ` Dave Chinner
2012-05-17 20:55 ` Chris J Arges
2012-05-18 16:53 ` Chris J Arges
2012-05-18 17:19 ` Ben Myers
2012-05-19 7:28 ` Juerg Haefliger
2012-05-21 17:11 ` Ben Myers
2012-05-24 5:45 ` Juerg Haefliger
2012-05-24 14:23 ` Ben Myers
2012-05-07 22:59 ` Dave Chinner
2012-05-09 7:35 ` Dave Chinner
2012-05-09 21:07 ` Mark Tinguely
2012-05-10 2:10 ` Mark Tinguely
2012-05-18 9:37 ` Dave Chinner [this message]
2012-05-18 9:31 ` Dave Chinner
2012-05-24 20:18 ` Peter Watkins
2012-05-25 6:28 ` Juerg Haefliger
2012-05-25 17:03 ` Peter Watkins
2012-06-05 23:54 ` Dave Chinner
2012-06-06 13:40 ` Brian Foster
2012-06-06 17:41 ` Mark Tinguely
2012-06-11 20:42 ` Chris J Arges
2012-06-11 23:53 ` Dave Chinner
2012-06-12 13:28 ` Chris J Arges
2012-06-06 22:03 ` Mark Tinguely
2012-06-06 23:04 ` Brian Foster
2012-06-07 1:35 ` Dave Chinner
2012-06-07 14:16 ` Brian Foster
2012-06-08 0:28 ` Dave Chinner
2012-06-08 17:09 ` Ben Myers
2012-06-11 20:59 ` Mark Tinguely
2012-06-05 15:21 ` Chris J Arges
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=20120518093743.GV25351@dastard \
--to=david@fromorbit.com \
--cc=juergh@gmail.com \
--cc=tinguely@sgi.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