From: Lachlan McIlroy <lachlan@sgi.com>
To: lachlan@sgi.com
Cc: Timothy Shimmin <tes@sgi.com>, xfs@oss.sgi.com
Subject: Re: 2.6.24-rc3 oopses while mounting fs
Date: Wed, 05 Dec 2007 16:47:31 +1100 [thread overview]
Message-ID: <47563B73.2030403@sgi.com> (raw)
In-Reply-To: <4754FCEC.30906@sgi.com>
> ============================================================================
>
> cycle: 154 version: 2 lsn: 154,5248 tail_lsn: 153,253056
> length of Log Record: 61440 prev offset: 5120 num ops: 303
> uuid: b02fc6bd-662f-40a5-8f0c-e260a881a3e7 format: little endian linux
> h_size: 262144
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> extended-header: cycle: 154
> ----------------------------------------------------------------------------
>
> Oper (0): tid: 5769cd60 len: 0 clientid: TRANS flags: START
> ----------------------------------------------------------------------------
>
> Oper (1): tid: 5769cd60 len: 16 clientid: TRANS flags: none
> TRAN: type: STRAT_WRITE tid: 0 num_items: 5
> ----------------------------------------------------------------------------
>
> Oper (2): tid: 5769cd60 len: 56 clientid: TRANS flags: none
> INODE: #regs: 3 ino: 0x1400005c flags: 0x5 dsize: 16
> blkno: 610338736 len: 16 boff: 4096
> Oper (3): tid: 5769cd60 len: 96 clientid: TRANS flags: none
> INODE CORE
> magic 0x494e mode 0100600 version 1 format 2
> nlink 1 uid 14029 gid 1474
> atime 0x4716b870 mtime 0x4716bade ctime 0x4716bade
> size 0x1ce00000 nblocks 0x1c840 extsize 0x0 nextents 0x1
> naextents 0x0 forkoff 0 dmevmask 0x0 dmstate 0x0
> flags 0x0 gen 0x4
> Oper (4): tid: 5769cd60 len: 16 clientid: TRANS flags: none
> EXTENTS inode data
> ----------------------------------------------------------------------------
Another interesting point is that the transaction id has changed between
these operations from 5769cd60 to 5769cf18. It should stay the same.
We may be reading old log data.
>
> Oper (5): tid: 5769cf18 len: 24 clientid: TRANS flags: none
> BUF: #regs: 2 start blkno: 610338561 (0x24610701) len: 1 bmap size:
> 1 flags: 0x0
> Oper (6): tid: 5769cf18 len: 128 clientid: TRANS flags: none
> AGF Buffer: XAGF
> ver: 1 seq#: 5 len: 15258464
> root BNO: 1 CNT: 2
> level BNO: 1 CNT: 1
> 1st: 0 last: 3 cnt: 4 freeblks: 2491090 longest: 581471
> ----------------------------------------------------------------------------
>
> Oper (7): tid: 5769cf18 len: 28 clientid: TRANS flags: none
> BUF: #regs: 2 start blkno: 610338568 (0x24610708) len: 8 bmap size:
> 2 flags: 0x0
> Oper (8): tid: 5769cf18 len: 128 clientid: TRANS flags: none
> BUF DATA
> ----------------------------------------------------------------------------
>
next prev parent reply other threads:[~2007-12-05 5:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 13:45 2.6.24-rc3 oopses while mounting fs KELEMEN Peter
2007-11-28 23:56 ` Lachlan McIlroy
2007-11-30 22:31 ` KELEMEN Peter
2007-12-03 3:24 ` Lachlan McIlroy
2007-12-03 22:02 ` KELEMEN Peter
2007-12-04 0:11 ` Timothy Shimmin
2007-12-04 7:08 ` Lachlan McIlroy
2007-12-04 9:57 ` KELEMEN Peter
2007-12-05 5:47 ` Lachlan McIlroy [this message]
2007-12-05 6:38 ` Timothy Shimmin
2007-12-05 7:04 ` Lachlan McIlroy
2007-12-04 9:42 ` KELEMEN Peter
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=47563B73.2030403@sgi.com \
--to=lachlan@sgi.com \
--cc=tes@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 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.