Am 31.01.26 um 11:02 schrieb Salvatore Bonaccorso:
> Hi,
>
> On Sat, Jan 31, 2026 at 10:08:25AM +0100, 10dmar10 wrote:
>> Package: src:linux
>> Version: 6.18.5-1
>> Severity: normal
>> X-Debbugs-Cc: [email protected]
>>
>> Dear Maintainer,
>>
>> linux-image-6.18.5+deb14-amd64 seems to be unable to mount existing legacy
XFS V4 filesystems
>> reporting:
>>
>> XFS (...): Depricated V4 format (crc=0) not supported by kernel.
>>
>> reason seems to be a missing setting
>>> cat /boot/config-6.18.5+deb14-amd64 | grep CONFIG_XFS_SUPPORT_V4
>> # CONFIG_XFS_SUPPORT_V4 is not set
>>
>>
>> this setting was recently still enabled:
>>
>> XFS (sda3): Deprecated V4 format (crc=0) will not be supported after
September 2030.
>>
>>> cat /boot/config-6.17.13+deb14-amd64 | grep CONFIG_XFS_SUPPORT_V4
>> CONFIG_XFS_SUPPORT_V4=y
>>
>>
>> while no longer used by default, XFS V4 support is still useful for accessing
>> legacy XFS V4 file systems as long as kernel supports it.
>
> This is correct, the default was changed in upstream with f69260511c69
> ("xfs: disable deprecated features by default in Kconfig") and I
> believe we should follow that within the forky release cycle.
>
> Thus for forky I do not think we should diverge here from the default
> and re-enable deprecated features, but probably we should document it
> at least in the release notes so that people upgrading from trixie to
> forky are awaere that V4 filesystems will not be supported anymore.
>
> A NEWS entry in the packaging itself might be a good idea as well.
>
> Regards,
> Salvatore
Hi,
I wrote this bug report because I assumed the release interval for forky as 2027
-2030, which is within the kernel removal date for XFS V4 feature in 2030.
Enabling CONFIG_XFS_SUPPORT_V4 would allow to continue running otherwise
perfectly fine existing legacy XFS V4 filesystems without unnecessary breaking
anything within forky's release cycle...
