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

Restrict the number of LUNs to 256 #22

Open
dillaman opened this issue Sep 14, 2017 · 2 comments
Open

Restrict the number of LUNs to 256 #22

dillaman opened this issue Sep 14, 2017 · 2 comments
Labels

Comments

@dillaman
Copy link

This is the maximum supported by Linux and defining more than 256 images results in the rbd-target-gw crashing and burning

@dillaman dillaman added the bug label Sep 14, 2017
@mikechristie
Copy link
Contributor

One correction to what I wrote in the email to QE.

In older distro kernels like in RHEL 7 there is a hard coded limit of 256 in the kernel target layer. There is also a limit in some versions of rtslib.

In the current upstream kernel and rtslib we are probably limited by the system. There is a SCSI spec limit due to the LUN being limited to 8 bytes. I think in the target code though we use a uint32_t in some places so that is probably the max in theory. I think we would hit some memory or other resource limit before getting 2^32 LUNs.

@pcuzner
Copy link
Collaborator

pcuzner commented Sep 14, 2017

There are two limits here - one is the number of storage objects defined to the target, and the other the number of SO's masked to a client. It sounds like for now we should make them the same - but the goal would be to lift the SO's per target to something like 4096

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants