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

NAS-132244 / 25.04 / Reenable some initialization code for Fibre Channel #34

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

bmeagherix
Copy link

Previously had disabled some code for performance reasons because it was unnecessary for our iSCSI targets.

Turns out that we do need it for Fibre Channel targets, so reenable for non-iscsi.

@bmeagherix bmeagherix requested a review from yocalebo November 4, 2024 19:05
@yocalebo yocalebo added the jira label Nov 4, 2024
@bugclerk
Copy link

bugclerk commented Nov 4, 2024

@bugclerk bugclerk changed the title Reenable some initialization code for Fibre Channel NAS-132244 / None / Reenable some initialization code for Fibre Channel Nov 4, 2024
@bmeagherix bmeagherix changed the title NAS-132244 / None / Reenable some initialization code for Fibre Channel NAS-132244 / 25.04 / Reenable some initialization code for Fibre Channel Nov 4, 2024
@bmeagherix bmeagherix merged commit cca19a4 into truenas-3.9.0-pre Nov 4, 2024
0 of 4 checks passed
@bmeagherix bmeagherix deleted the fix_fc_npiv branch November 4, 2024 19:18
@bugclerk
Copy link

bugclerk commented Nov 4, 2024

Not updating JIRA ticket https://ixsystems.atlassian.net/browse/NAS-132244 target versions as no JIRA version corresponds to this PR

@bugclerk
Copy link

bugclerk commented Nov 4, 2024

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.

@truenas truenas locked as resolved and limited conversation to collaborators Nov 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants