Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Temporarily disable Direct IO by default #16597

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

behlendorf
Copy link
Contributor

@behlendorf behlendorf commented Oct 2, 2024

Motivation and Context

Prior to creating the 2.3 release branch disable direct IO by default. Direct IO will be disabled in the -RC1 tag, we expect to finishing integrating fixes for the known issues and enable it by default in -RC2.

Description

While some remaining issues are resolved with the recently merged Direct IO functionality disable it by default.

Outstanding issues: #16594, #16596, read-only-verify PR pending.

How Has This Been Tested?

Will be tested by the CI. The direct IO test cases are already aware of this tuning and should be skipped.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Performance enhancement (non-breaking change which improves efficiency)
  • Code cleanup (non-breaking change which makes code smaller or more readable)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
  • Documentation (a change to man pages or other documentation)

Checklist:

While some remaining issues are resolved with the recently merged
Direct IO functionality disable it by default.

Signed-off-by: Brian Behlendorf <[email protected]>
@behlendorf behlendorf added Status: Accepted Ready to integrate (reviewed, tested) and removed Status: Code Review Needed Ready for review and testing labels Oct 2, 2024
@behlendorf behlendorf merged commit 4121059 into openzfs:master Oct 3, 2024
15 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Ready to integrate (reviewed, tested)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants