trid: Take Host NQN into account #379
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When booting from SAN (BFS), the Host NQN specified in the NBFT files is often different from the Host NQN specified in /etc/nvme/hostnqn. Therefore, connections made after the system is fully booted will be made with a different Host NQN than the connections made during boot. nvme-stas did not consider the Host NQN when scanning for existing connections, which means that it would reuse a BFS connection when in fact it needed to create a new one using a different Host NQN. Note that the same issue is seen in nvme-cli and libnvme as well. These will need to be fixed separately. Signed-off-by: Martin Belanger <martin.belanger@dell.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When booting from SAN (BFS), the Host NQN specified in the NBFT files is often different from the Host NQN specified in /etc/nvme/hostnqn. Therefore, connections made after the system is fully booted will be made with a different Host NQN than the connections made during boot. nvme-stas did not consider the Host NQN when scanning for existing connections, which means that it would reuse a BFS connection when in fact it needed to create a new one using a different Host NQN.
Note that the same issue is seen in nvme-cli and libnvme as well. These will need to be fixed separately.