From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 216343] XFS: no space left in xlog cause system hang
Date: Wed, 17 Aug 2022 10:05:42 +0000 [thread overview]
Message-ID: <bug-216343-201763-sk71fw4i3o@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216343-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216343
--- Comment #5 from zhoukete@126.com ---
(In reply to Amir Goldstein from comment #4)
>
> According to xfs_trans_dirty_buf() I think it could mean uptodate and
> dirty buffer.
>
when I review the xfs_trans_dirty_buf code, I found that xfs inode item
b_log_item is null,
crash> xfs_log_item.li_buf,li_ops 0xffff0340999a0a80 -x
li_buf = 0xffff0200125b7180
li_ops = 0xffff800008faec60 <xfs_inode_item_ops>
crash> xfs_buf.b_log_item 0xffff0200125b7180
b_log_item = 0x0
and only xfs buf log item b_log_item has value
crash> xfs_log_item.li_buf,li_ops ffff033f8d7c9de8 -x
li_buf = 0x0
li_ops = 0xffff800008fae8d8 <xfs_buf_item_ops>
crash> xfs_buf_log_item.bli_buf ffff033f8d7c9de8
bli_buf = 0xffff0200125b4a80
crash> xfs_buf.b_log_item 0xffff0200125b4a80
b_log_item = 0xffff033f8d7c9de8
crash> xfs_buf_log_item.bli_flags 0xffff033f8d7c9de8
bli_flags = 2 (XFS_BLI_DIRTY)
crash> xfs_buf_log_item.bli_item.li_flags ffff033f8d7c9de8
bli_item.li_flags = 1, (XFS_LI_IN_AIL)
So xfs buf log item XFS_DONE is set because of xfs_trans_dirty_buf(),buf xfs
inode log item never call xfs_trans_dirty_buf() because of b_log_item == 0x0.
Do you know the reason why xfs inode log item XFS_DONE is set?
>
> Maybe the hardware never returned with a response?
> Hard to say. Maybe someone else has ideas.
>
If we can prove that XFS_DONE isn't stand for iodone, I think this issue may
cause by the hardware error.
I find the err msg in dmesg:
[ 9824.111366] mpt3sas_cm0: issue target reset: handle = (0x0034)
Maybe it tell us mpt3sas lost the io requests before.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-08-17 10:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 11:46 [Bug 216343] New: XFS: no space left in xlog cause system hang bugzilla-daemon
2022-08-11 7:04 ` [Bug 216343] " bugzilla-daemon
2022-08-14 23:54 ` [Bug 216343] New: " Dave Chinner
2022-08-15 16:12 ` Amir Goldstein
2022-08-14 23:54 ` [Bug 216343] " bugzilla-daemon
2022-08-15 16:12 ` bugzilla-daemon
2022-08-16 6:56 ` bugzilla-daemon
2022-08-16 14:32 ` Amir Goldstein
2022-08-16 14:32 ` bugzilla-daemon
2022-08-17 10:05 ` bugzilla-daemon [this message]
2022-08-17 13:15 ` Amir Goldstein
2022-08-17 13:15 ` bugzilla-daemon
2022-08-18 8:23 ` bugzilla-daemon
2023-09-21 6:58 ` bugzilla-daemon
2023-09-21 6:59 ` bugzilla-daemon
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=bug-216343-201763-sk71fw4i3o@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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.