{"id":103420,"date":"2022-02-23T21:36:49","date_gmt":"2022-02-23T19:36:49","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/razrabotchiki-yadra-linux-obsuzhdayut-vozmozhnost-udaleniya-reiserfs"},"modified":"2022-02-23T21:36:49","modified_gmt":"2022-02-23T19:36:49","slug":"razrabotchiki-yadra-linux-obsuzhdayut-vozmozhnost-udaleniya-reiserfs","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/razrabotchiki-yadra-linux-obsuzhdayut-vozmozhnost-udaleniya-reiserfs","title":{"rendered":"Linux kernel developers discuss the possibility of removing ReiserFS","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Matthew Wilcox from Oracle, known for creating the nvme (NVM Express) driver and the DAX filesystem direct access mechanism, proposed removing the ReiserFS filesystem from the Linux kernel, similar to the previously removed legacy filesystems ext and xiafs, or to reduce the ReiserFS code, keeping only read-only mode support. <\/p>\n
The motive for removal stems from the additional difficulties in modernizing the kernel infrastructure caused by the necessity to retain the outdated AOP_FLAG_CONT_EXPAND flag handler in the kernel specifically for ReiserFS, as it remains the only filesystem utilizing this flag in the write_begin function. The last code update for ReiserFS dates back to 2019, and it is unclear how much this filesystem is still in demand and whether it continues to be used. <\/p>\n
Jan K\u00e1ra from SUSE agreed that ReiserFS is on a path to obsolescence, but it is unclear whether it is outdated enough to be removed from the kernel. According to Jan, ReiserFS continues to be included in openSUSE and SLES, but the user base for this filesystem is small and shrinking. Support for ReiserFS in SUSE was discontinued for enterprise users 3-4 years ago, and the ReiserFS module is not included by default in the kernel package. As an option, Jan suggested starting to issue a deprecation warning when mounting ReiserFS partitions and considering this filesystem ready for removal if no one expresses a desire to continue using it within a year or two. <\/p>\n
The discussion was joined by Eduard Shishkin, the maintainer of the ReiserFS filesystem, who provided a patch removing the use of the AOP_FLAG_CONT_EXPAND flag from the ReiserFS code. Matthew Wilcox accepted the patch into his branch. Thus, the reason for removal has been eliminated, and the question of excluding ReiserFS from the kernel can be considered deferred for a considerable time. <\/p>\n
It is impossible to completely disregard the issue of ReiserFS obsolescence due to work aimed at removing file systems with unresolved 2038 problems from the kernel. For example, for this reason, a schedule has already been prepared for the removal of version four of the XFS file system from the kernel (the new XFS format was proposed in kernel 5.10 and pushed the time counter overflow to the year 2468). The XFS v4 build will be disabled by default in 2025, and the code will be removed in 2030. A similar schedule is proposed to be developed for ReiserFS, allowing at least five years for migration to other file systems or an altered metadata format. \n Source: opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"