WebUI for dataset "Metadata (Special) Small Block Size" is artificially limited to 1 MiB
Description
Attachments
Activity

Kris Moore July 18, 2024 at 5:56 PM
Thank you for submitting this feature request! To better accommodate and gauge community interest for future versions of TrueNAS we have moved the submission process to our TrueNAS Community Forums. If this feature is still important and relevant for consideration, please refer to the links below on how to submit it for community voting and TrueNAS roadmap review.
Feature Requests Forum:
https://forums.truenas.com/c/features/12
Feature Requests FAQ:
https://forums.truenas.com/t/about-the-feature-requests-category-readme-first/8802

Andrius Kr September 28, 2023 at 3:27 PM
Debug log not required from my PoV - case seems to be clear.

Automation for Jira September 27, 2023 at 1:01 PM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
Details
Details
Priority
Assignee
Reporter

This issue is the development of the old issues here: and here:
TrueNAS WebUI in the dataset “Edit Options” panel does not allow to set “Metadata (Special) Small Block Size“ even when vfs.zfs.max_recordsize>=special_small_blocks is set. Therefore “Metadata (Special) Small Block Size“ is artificially limited to 1 MiB. As per older cases of artificially limited small block sizes to 128 KiB , then 1 MiB, then in principle - unlimited to 16 MiB (if set in the command line), WebUI limit should be lifted.
Motivation is simple (as was before, described in the above bugs) - it should be allowed, because there are use-cases, where 2-8 MiB “small block sizes” would allow to land whole files on SSD media, instead of HDD. An example would be typical pictures from DSRL cameras, which can be outputed in 2 simultaneous files - small .JPG and big .RAW. JPG often fit as small files to SSD, while RAWs would land on HDD vdevs.
At this moment there is a manual work around, which is inconvenient - if one has to edit dataset options, it must do everything either in the command-line or change small_block_size temporarily to 1 MiB while committing dataset options form, and then set small_block_size in the command line above 1 MiB artifial WebUI limit.