From: Mark Tinguely <tinguely@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Juerg Haefliger <juergh@gmail.com>, xfs@oss.sgi.com
Subject: Re: Still seeing hangs in xlog_grant_log_space
Date: Wed, 09 May 2012 21:10:05 -0500 [thread overview]
Message-ID: <4FAB237D.5050608@sgi.com> (raw)
In-Reply-To: <4FAADCA8.6030702@sgi.com>
On 05/09/12 16:07, Mark Tinguely wrote:
>
>
> Maybe I have a corrupted version of his first trace, it looks like there
> are 2 series of log grant/write/head/tail sequences. These sequences are
> not even close to each other:
>
> 188.116687: FSYNC_TS empty empty 1 847894476 1 847894476 1 1655998 1
> 1655971
> 188.116939: FSYNC_TS empty empty 1 847894476 1 847894476 1 1655998 1
> 1655971
> 188.117755: CREATE empty empty 4440 166388 4440 166388 4440 312 4440 310
> 188.117784: FSYNC_TS empty empty 1 847894476 1 847894476 1 1655998 1
> 1655971
> 188.117902: FSYNC_TS empty empty 1 847894476 1 847894476 1 1655998 1
> 1655971
> 188.118249: CREATE empty empty 4440 166844 4440 166844 4440 312 4440 310
> 188.118350: CREATE empty empty 4440 167300 4440 167300 4440 312 4440 310
> 188.118628: FSYNC_TS empty empty 4440 167300 4440 167300 4440 312 4440 310
> 188.118837: FSYNC_TS empty empty 1 847894476 1 847894476 1 1655998 1
> 1655971
> 188.118868: FSYNC_TS empty empty 1 847894476 1 847894476 1 1655998 1
> 1655971
Oops, there are multiple devices in that trace.
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. 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.
--Mark Tinguely.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-05-10 2:10 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 [this message]
2012-05-18 9:37 ` Dave Chinner
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=4FAB237D.5050608@sgi.com \
--to=tinguely@sgi.com \
--cc=david@fromorbit.com \
--cc=juergh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.