my-ship-it commented on issue #1655:
URL: https://github.com/apache/cloudberry/issues/1655#issuecomment-4167860865
Thanks for reporting the issue.
### Root Cause Analysis
This is a documentation issue, not a code bug:
1. nobarrier is a filesystem mount option that disables write barriers to
improve I/O performance.
2. In newer Linux kernels (5.x+), XFS and ext4 have removed support for
the nobarrier option. Passing an unrecognized mount option causes the mount to
fail.
3. Virtual machine environments typically use newer kernels, making this
issue more likely to occur.
4. CloudBerry's deployment documentation (inherited from Greenplum)
recommends adding nobarrier to /etc/fstab for disk performance optimization,
but this recommendation is
outdated.
### Recommended Fix
The fix should target the deployment documentation:
1. Remove or annotate the nobarrier recommendation — Note that this option
is no longer supported on Linux 5.x+ kernels.
2. Provide alternatives — For ext4, barrier=0 may still work. For
production environments with BBU-backed RAID controllers, this option can be
safely omitted entirely.
3. Add a warning — Advise users to test with mount -o nobarrier first to
verify kernel support before writing it to fstab.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]