MAX LUN limits

[CMAPTu]

There is a variable in FreeNAS.pm script:

$MAX_LUNS = 255;

As it follows from RedHat documentation: https://access.redhat.com/solutions/5120951 , this limit is not actual. So every time we install freenas-proxmox plugin, we have to edit script to enlarge this limit.

Please, make changes to the script. Set variable as big as it is possible.

[TheGrandWazoo]

Thanks for reporting it. I will review the Redhat document and figure out a solution.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[tuxick]

There is a variable in FreeNAS.pm script:

$MAX_LUNS = 255;

As it follows from RedHat documentation: https://access.redhat.com/solutions/5120951 , this limit is not actual. So every time we install freenas-proxmox plugin, we have to edit script to enlarge this limit.

Please, make changes to the script. Set variable as big as it is possible.

Are you sure more than 255 is supported by freenas/truenas? here they suggest 256 luns is a hard limit.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[CMAPTu]

There is a variable in FreeNAS.pm script:
$MAX_LUNS = 255;
As it follows from RedHat documentation: https://access.redhat.com/solutions/5120951 , this limit is not actual. So every time we install freenas-proxmox plugin, we have to edit script to enlarge this limit.
Please, make changes to the script. Set variable as big as it is possible.

Are you sure more than 255 is supported by freenas/truenas? here they suggest 256 luns is a hard limit.

Yes, I am pretty sure of that. Here is the kernel variable value:

We successfully multiplied it by two in /boot/loader.conf of FreeNAS. After reboot it worked.

kern.cam.ctl.max_luns=2048

[TheGrandWazoo]

Bringing out of closed as this is as a few solutions to the issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.