public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [6.15-rc2 regression] xfs: assertion failed in inode allocation
Date: Wed, 16 Apr 2025 16:39:02 +1000	[thread overview]
Message-ID: <Z_9QhvYYhFP7Zk74@dread.disaster.area> (raw)
In-Reply-To: <20250416053006.GD25675@frogsfrogsfrogs>

On Tue, Apr 15, 2025 at 10:30:06PM -0700, Darrick J. Wong wrote:
> On Wed, Apr 16, 2025 at 02:49:56PM +1000, Dave Chinner wrote:
> > Hi folks,
> > 
> > After upgrading to ia current TOT kernel from 6.15-rc1, I'm now
> > seeing these assert failures during inode allocation when running
> > check-parallel:
> > 
> > [  355.630225] XFS: Assertion failed: freecount == to_perag(cur->bc_group)->pagi_freecount, file: fs/xfs/libxfs/xfs_ialloc.c, line: 280
> 
> I haven't seen this assertion tripping any more than it has in the past.
> 
> But I will say that I've seen a number of other problems, like page
> state corruption, null pointer derefs from the block layer, and weird
> behavior from the rest of the kernel.  Turning off LBS support fixes a
> lot of it.  -rc2 doesn't seem to have fixed anything over -rc1.

Yeah, that's pretty much my experience with the current TOT kernel -
it seems to be randomly corrupting block devices, failing to detect
filesystem features correctly (e.g. generic/577 seems to think that
XFS supports fsverity, then it fork bombs the machine with thousands
of child processes that never get reaped), stuff hanging in weird
places (e.g. udevadm getting stuck waiting on things that have
already happened) and so on.

I would not be running 6.15-rcX on anything important right now...

-Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2025-04-16  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16  4:49 [6.15-rc2 regression] xfs: assertion failed in inode allocation Dave Chinner
2025-04-16  5:30 ` Darrick J. Wong
2025-04-16  6:39   ` Dave Chinner [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=Z_9QhvYYhFP7Zk74@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@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