From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 210341] XFS (dm-3): Internal error xfs_trans_cancel at line 1041 of file fs/xfs/xfs_trans.c.
Date: Tue, 24 Nov 2020 20:29:13 +0000 [thread overview]
Message-ID: <bug-210341-201763-dqLJ7gmDrD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210341-201763@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210341
--- Comment #1 from Dave Chinner (david@fromorbit.com) ---
On Tue, Nov 24, 2020 at 05:53:09AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=210341
>
> Bug ID: 210341
> Summary: XFS (dm-3): Internal error xfs_trans_cancel at line
> 1041 of file fs/xfs/xfs_trans.c.
> Product: File System
> Version: 2.5
> Kernel Version: 4.18.0-147
> Hardware: Intel
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: blocking
> Priority: P1
> Component: XFS
> Assignee: filesystem_xfs@kernel-bugs.kernel.org
> Reporter: lokendra.rathour@hsc.com
> Regression: No
>
> Created attachment 293797
> --> https://bugzilla.kernel.org/attachment.cgi?id=293797&action=edit
> Detailed logs as shown above
>
> Getting errror for xfs file system :
>
> 2020-11-11T11:55:16.809 controller-1 kernel: alert [419472.614847] XFS
> (dm-3):
> xfs_dabuf_map: bno 8388608 dir: inode 122425344
> 2020-11-11T11:55:16.809 controller-1 kernel: alert [419472.621963] XFS
> (dm-3):
> [00] br_startoff 8388608 br_startblock -2 br_blockcount 1 br_state 0
> 2020-11-11T11:55:16.823 controller-1 kernel: alert [419472.630908] XFS
> (dm-3):
> Internal error xfs_da_do_buf(1) at line 2558 of file
> fs/xfs/libxfs/xfs_da_btree.c. Caller xfs_da_read_buf+0x6c/0x120 [xfs]
> 2020-11-11T11:55:16.824 controller-1 kernel: warning [419472.644671] CPU: 1
> PID: 83210 Comm: heat-manage Kdump: loaded Tainted: G O
> ---------
> -t - 4.18.0-147.3.1.el8_1.7.tis.x86_64 #1
So you have a corrupt directory (missing a leaf root pointer). Have
you run `xfs_repair -n` on that filesystem to see if it finds the
same corruption?
Keep in mind that you are running on a CentOS8/RHEL8 kernel. It is
unlikely that upstream developers will be able to reliably diagnose
the root cause of your issue as the kernel codebase is a highly
modified vendor kernel. You really should report this to your
vendor support contacts, not upstream....
Cheers,
Dave.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-11-24 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 5:53 [Bug 210341] New: XFS (dm-3): Internal error xfs_trans_cancel at line 1041 of file fs/xfs/xfs_trans.c bugzilla-daemon
2020-11-24 20:29 ` Dave Chinner
2020-11-24 20:29 ` bugzilla-daemon [this message]
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-210341-201763-dqLJ7gmDrD@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox