File System Issues
The following are known file systems issues that have been encountered in this release of Oracle Linux 8.
BTRFS File System Not Supported on RHCK
The Btrfs file system is removed from RHCK in Oracle Linux 8, which means you cannot create or mount this file system when using this kernel. Also, any Btrfs user space packages that are provided are not supported with RHCK.
Support for the Btrfs file system is enabled in UEK R7 and UEK R6. Starting with Oracle Linux 8.3, during an installation, you have the option to create a Btrfs root file system, as well as select Btrfs as the file system type when formatting devices.
For further details about these changes, see the following documentation:
-
For information about creating a Btrfs root file system during an installation, see Oracle Linux 8: Installing Oracle Linux.
-
For information about managing the Btrfs file system, see Oracle Linux 8: Managing Local File Systems.
-
For the latest information about other enhancements that have been made to Btrfs in UEK R6, see Unbreakable Enterprise Kernel Release 6 Update 3: Release Notes (5.4.17-2136).
For information about UEK R7, see Unbreakable Enterprise Kernel Release 7: Release Notes (5.15.0-0.30).
OCFS2 File System Not Supported on RHCK
The OCFS2 file system is removed from RHCK in Oracle Linux 8, which means you cannot create or mount this file system when using this kernel. Also, OCFS2 user space packages that are provided are not supported with RHCK.
Note that support for OCFS2 file systems is enabled in UEK R7 and UEK R6. For the latest information and other enhancements that have been made to OCFS2 in UEK R6, see Unbreakable Enterprise Kernel Release 6 Update 3: Release Notes (5.4.17-2136). See also Unbreakable Enterprise Kernel Release 7: Release Notes (5.15.0-0.30).
ext4
: Frequent or repeated system shutdowns can cause file system
corruption
If a system that is using the ext4
file system is repeatedly or frequently
shut down, the file system might become corrupted. This issue is difficult to replicate and is
therefore considered to be a corner-case issue. The issue exists in the upstream code and
proposed patches are currently under review.
(Bug ID 27547113)