https://bugzilla.kernel.org/show_bug.cgi?id=217769 Grant Millar (grant@xxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |grant@xxxxxxxx --- Comment #17 from Grant Millar (grant@xxxxxxxx) --- 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. 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.