Todo #13108
closed
ZFS filesystem implications
0%
Description
One of the recent file system changes to the default ZFS install was to mount some things as 'noexec'.
This includes /conf which may be an issue for some users who have custom scripts at that location. At one time that was the recommended location for such scripts.
Users using that should move custom scripts to an executable location, such as /root, and update and commands that reference them.
Updated by Steve Wheeler almost 3 years ago
- Subject changed from ZFS filesystem layout changes implications to ZFS filesystem layout change implications
Updated by Jim Pingle almost 3 years ago
- Subject changed from ZFS filesystem layout change implications to ZFS filesystem implications
- Category changed from Administrivia to Installation / Upgrades
- Target version deleted (
2.7.0)
This isn't a recent change in ZFS, as the /cf/conf dataset has been configured with the exec property set to off for quite some time. Even back on Plus 21.05.2/CE 2.5.2 it was set that way.
So more likely this may impact someone moving from UFS to ZFS and not someone upgrading ZFS in-place.
For reference, here is a list of current ZFS datasets and their properties:
: zfs get exec NAME PROPERTY VALUE SOURCE pfSense exec on default pfSense/ROOT exec on default pfSense/ROOT/default exec on default pfSense/cf exec off local pfSense/cf/conf exec off local pfSense/home exec on default pfSense/reservation exec on default pfSense/tmp exec on local pfSense/var exec on default pfSense/var/cache exec off local pfSense/var/db exec off local pfSense/var/log exec off local pfSense/var/tmp exec on default
This may change again before release (#12967) so it might be good to wait until after all the pending work gets merged before making updates to the docs.
Updated by Jim Pingle 7 months ago
- Status changed from New to Rejected
It's been a couple years and this hasn't really been an issue. If people start hitting it regularly we can work it in somewhere.