Dear Salvatore,
On 2026-02-19 19:51, Salvatore Bonaccorso wrote:
Hi Janos,
On Thu, Feb 19, 2026 at 05:35:39PM +0100, Pásztor János wrote:
Package: src:linux
Version: 6.18.5-1~bpo13+1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: [email protected]
Dear Maintainer,
* What led up to the situation?
Upgrade from 6.17.13+deb13-amd64 to 6.18.5-1~bpo13+1
From what I see above you are using a XFS V4 filesystem, right?
XFS V4 support was long deprecated and is removed with 6.18.5, we will
add a NEWS entry (which is yet missing) and adding release notes. That
is, you need to move to a V5 format XFS.
We might want to handle it differently for the backports kernel, but
will ask Ben about it.
I will for now merge both bugs as this will need to be handled in
documentation for users upgrading to Debian forky. It is not the right
time to do it, as people wanting to stick with the kernel still
supporting it are able to compile a own kernel with the config option
enabled, but which will be dropped completely in next versions of
Linux. Keeping it enabled for another cycle will be worse afterwards.
Unfortunately the only option for you to mgirate to a V5 XFS
filesystem is to actually create a new one. There is not the
possibility to covert a V4 to a V5.
Regards,
Salvatore
Yes, I am using XFS V4 thanks to the magic of lvm and my trusty
screwdriver :-) The installation happened in 2013 and since than I just
upgraded through both sw and hw.
I agree with you that the support for V4 has to go with forky, but I
would like to ask you to keep it as close to the release as possible,
and handle the backports kernel in a way that it could boot up with such
a setup.
With that the owners of the affected systems would get some time to
prepare and backports would keep continue working.
Thanks in advance!
Regards,
János Pásztor
