I have an external SSD drive that needs two changes in fstab to work as expected. First, there is the option “ssd” to make it load ssd optimizations. Additionally, “noauto” is removed to make it work as needed in my setup.
[ 7.230446] BTRFS info (device sda1): enabling ssd optimizations
[ 7.230484] BTRFS info (device sda1): disk space caching is enabled
[ 7.230496] BTRFS info (device sda1): has skinny extents
However, these changes only last until dietpi-drive_manager is launched again.
How can these changes be made persistent and survive drive_manager?
Actually this is how drive manager is working, to remove custom entries and replace it with default values . We are aware of these downside and planning to change the behaviour. However we don’t have an ETA.
Workaround would be not to use drive manager to configure fstab entries.
Regarding the ssd option: The driver is nowadays clever enough to autodetect via /sys/block/*/queue/rotational whether it is an SSD (or other flash drive) or not to set the flag/optimisations automatically. So this should usually not be requried.
The fstrim.timer is enabled by default to run fstrim.service once a week. So the discard=async option could be skipped if the drive’s free space isn’t fully rewritten once in a week.
But yes, I agree we need to change dietpi-drive_manager’s behaviour to not rewrite the whole /etc/fstab when you run it.
Sorry to drag up an old thread, but this would be amazing if possible.
Even better would be an options tab in dietpi-drive_manager, where you can add in various SMB options. This would mean you wouldn’t have to change the behaviour of it re-writing /etc/fstab if we didn’t have to manually modify it.