From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org,
"Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
Cc: ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
hch@infradead.org
Subject: Re: [PATCH v2] xfs: Fix xfs_grow_last_rtg()
Date: Tue, 13 Jan 2026 14:10:40 +0100 [thread overview]
Message-ID: <176830984026.127908.1608705723447538666.b4-ty@kernel.org> (raw)
In-Reply-To: <9b2e055a1e714dacf37b4479e2aab589f3cec7f6.1768205975.git.nirjhar.roy.lists@gmail.com>
On Mon, 12 Jan 2026 13:54:02 +0530, Nirjhar Roy (IBM) wrote:
> The last rtg should be able to grow when the size of the last is less
> than (and not equal to) sb_rgextents. xfs_growfs with realtime groups
> fails without this patch. The reason is that, xfs_growfs_rtg() tries
> to grow the last rt group even when the last rt group is at its
> maximal size i.e, sb_rgextents. It fails with the following messages:
>
> XFS (loop0): Internal error block >= mp->m_rsumblocks at line 253 of file fs/xfs/libxfs/xfs_rtbitmap.c. Caller xfs_rtsummary_read_buf+0x20/0x80
> XFS (loop0): Corruption detected. Unmount and run xfs_repair
> XFS (loop0): Internal error xfs_trans_cancel at line 976 of file fs/xfs/xfs_trans.c. Caller xfs_growfs_rt_bmblock+0x402/0x450
> XFS (loop0): Corruption of in-memory data (0x8) detected at xfs_trans_cancel+0x10a/0x1f0 (fs/xfs/xfs_trans.c:977). Shutting down filesystem.
> XFS (loop0): Please unmount the filesystem and rectify the problem(s)
>
> [...]
Applied to for-next, thanks!
[1/1] xfs: Fix xfs_grow_last_rtg()
commit: a65fd81207669367504b6da7758e130ee23a7dfe
Best regards,
--
Carlos Maiolino <cem@kernel.org>
prev parent reply other threads:[~2026-01-13 13:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 8:24 [PATCH v2] xfs: Fix xfs_grow_last_rtg() Nirjhar Roy (IBM)
2026-01-12 21:51 ` Darrick J. Wong
2026-01-13 13:10 ` Carlos Maiolino [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=176830984026.127908.1608705723447538666.b4-ty@kernel.org \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nirjhar.roy.lists@gmail.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
/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