linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 217769] XFS crash on mount on kernels >= 6.1
Date: Tue, 14 Nov 2023 23:46:06 +0000	[thread overview]
Message-ID: <bug-217769-201763-5gEVnJRFUZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217769-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217769

--- Comment #18 from Darrick J. Wong (djwong@kernel.org) ---
On Tue, Nov 14, 2023 at 03:57:06PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=217769
> 
> Grant Millar (grant@cylo.net) changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |grant@cylo.net
> 
> --- Comment #17 from Grant Millar (grant@cylo.net) ---
> We're experiencing the same bug following a data migration to new servers.
> 
> The servers are all running a fresh install of Debian 12 with brand new
> hardware.
> 
> So far in the past 3 days we've had 2 mounts fail with:
> 
> [28797.357684] XFS (sdn): Internal error xfs_trans_cancel at line 1097 of
> file
> fs/xfs/xfs_trans.c.  Caller xfs_rename+0x61a/0xea0 [xfs]
> [28797.488475] XFS (sdn): Corruption of in-memory data (0x8) detected at
> xfs_trans_cancel+0x146/0x150 [xfs] (fs/xfs/xfs_trans.c:1098).  Shutting down
> filesystem.
> [28797.488595] XFS (sdn): Please unmount the filesystem and rectify the
> problem(s)
> 
> Both occurred in the same function on separate servers:
> xfs_rename+0x61a/0xea0
> 
> Neither mounts are the root filesystem.

This should be fixed in 6.6, could you try that and report back?

(See "xfs: reload entire unlinked bucket lists")

--D

> 
> versionnum [0xbcf5+0x18a] =
>
> V5,NLINK,DIRV2,ATTR,QUOTA,ALIGN,LOGV2,EXTFLG,SECTOR,MOREBITS,ATTR2,LAZYSBCOUNT,PROJID32BIT,CRC,FTYPE,FINOBT,SPARSE_INODES,REFLINK,INOBTCNT,BIGTIME
> 
> meta-data=/dev/sdk               isize=512    agcount=17, agsize=268435455
> blks
>          =                       sectsz=4096  attr=2, projid32bit=1
>          =                       crc=1        finobt=1, sparse=1, rmapbt=0
>          =                       reflink=1    bigtime=1 inobtcount=1
>          nrext64=0
> data     =                       bsize=4096   blocks=4394582016, imaxpct=50
>          =                       sunit=0      swidth=0 blks
> naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
> log      =internal log           bsize=4096   blocks=521728, version=2
>          =                       sectsz=4096  sunit=1 blks, lazy-count=1
> realtime =none                   extsz=4096   blocks=0, rtextents=0
> 
> Please let me know if I can provide more information.
> 
> -- 
> You may reply to this email to add a comment.
> 
> You are receiving this mail because:
> You are watching the assignee of the bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2023-11-14 23:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 16:35 [Bug 217769] New: XFS crash on mount on kernels >= 6.1 bugzilla-daemon
2023-08-07 17:17 ` [Bug 217769] " bugzilla-daemon
2023-08-07 18:06 ` bugzilla-daemon
2023-08-07 19:01 ` bugzilla-daemon
2023-08-07 19:40 ` bugzilla-daemon
2023-08-07 20:15 ` bugzilla-daemon
2023-08-07 22:34 ` bugzilla-daemon
2023-08-08 13:39 ` bugzilla-daemon
2023-08-08 14:51 ` bugzilla-daemon
2023-08-08 14:54 ` bugzilla-daemon
2023-08-08 14:55 ` bugzilla-daemon
2023-08-08 21:54 ` bugzilla-daemon
2023-08-08 22:07 ` bugzilla-daemon
2023-08-09 16:43 ` bugzilla-daemon
2023-08-09 18:31 ` bugzilla-daemon
2023-08-09 19:10 ` bugzilla-daemon
2023-08-29 23:42   ` Darrick J. Wong
2023-08-29 23:42 ` bugzilla-daemon
2023-11-14 15:57 ` bugzilla-daemon
2023-11-14 23:46   ` Darrick J. Wong
2023-11-14 23:46 ` 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-217769-201763-5gEVnJRFUZ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).