Fully agree with this request — I'm hit by it as well. All my shares start with a number to keep them in order (01-xx, 02-xx, 03-xx…). Since the new validation, I can no longer create a share with the naming scheme I've used for years. I don't use ZFS at all and don't intend to (XFS/BTRFS covers my needs), so being blocked by a ZFS-related rule is really frustrating. On top of that, the "must start with a letter" rule seems stricter than ZFS itself: only pool names have to start with a letter, while dataset names (which is what a share becomes on a ZFS pool) may start with any alphanumeric character, digits included. Several users in other threads have digit-prefixed shares on ZFS pools without any issue. Suggested fix: - Apply the ZFS rules only when a ZFS pool is selected as primary/secondary storage (or when switching an existing share to one). - Otherwise, show a warning instead of blocking. - Align the rule with the actual ZFS dataset naming rules, so leading digits are allowed. Running Unraid 7.3.1. Thanks for considering it.