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@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
