I'd am running btrfs on a SSD RAID and would like to mount it with options such as -o ssd and -o autodefrag
How can I define customised mount options in OMV?
I'd am running btrfs on a SSD RAID and would like to mount it with options such as -o ssd and -o autodefrag
How can I define customised mount options in OMV?
Please post your fstab
while I believe fstab is no longer used for mounting.
Am I right?
for merged filesystems yes, but not for the filesystems that are being merged AFAIK
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdf1 during installation
UUID=ea9f53b8-b013-42ca-b749-3e40eaefe400 / ext4 errors=remount-ro 0 1
# swap was on /dev/sdf5 during installation
UUID=bd337132-4fd1-4d26-9924-943ad48cfd60 none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-uuid/786fbfe4-2782-4b41-b28a-9ec8130edb8d /srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d btrfs defaults,nofail,ssd 0 2
/dev/disk/by-uuid/01cc26c2-19ae-48f8-ab41-377f9028a8cf /srv/dev-disk-by-uuid-01cc26c2-19ae-48f8-ab41-377f9028a8cf btrfs defaults,nofail,ssd 0 2
/dev/disk/by-uuid/80b0a654-1c23-4a49-af6b-2812fddf71f2 /srv/dev-disk-by-uuid-80b0a654-1c23-4a49-af6b-2812fddf71f2 btrfs defaults,nofail,ssd 0 2
/dev/disk/by-uuid/52c56732-4fd7-4cc3-ac37-64760ac981ca /srv/dev-disk-by-uuid-52c56732-4fd7-4cc3-ac37-64760ac981ca btrfs defaults,nofail,ssd 0 2
# <<< [openmediavault]
Alles anzeigen
Looks like you have four filesystems with btrfs mounted from the GUI of OMV.
# >>> [openmediavault]
/dev/disk/by-uuid/786fbfe4-2782-4b41-b28a-9ec8130edb8d /srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d btrfs defaults,nofail,ssd 0 2
/dev/disk/by-uuid/01cc26c2-19ae-48f8-ab41-377f9028a8cf /srv/dev-disk-by-uuid-01cc26c2-19ae-48f8-ab41-377f9028a8cf btrfs defaults,nofail,ssd 0 2
/dev/disk/by-uuid/80b0a654-1c23-4a49-af6b-2812fddf71f2 /srv/dev-disk-by-uuid-80b0a654-1c23-4a49-af6b-2812fddf71f2 btrfs defaults,nofail,ssd 0 2
/dev/disk/by-uuid/52c56732-4fd7-4cc3-ac37-64760ac981ca /srv/dev-disk-by-uuid-52c56732-4fd7-4cc3-ac37-64760ac981ca btrfs defaults,nofail,ssd 0 2
# <<< [openmediavault]
Then you might have merged them in the plugin.
for merged filesystems yes, but not for the filesystems that are being merged AFAIK
Ah. I see. So I can use fstab for changes.
thanks
Ah. I see. So I can use fstab for changes.
thanks
Changes within the openmediavault section of fstab will get overwritten the next time a system change is applied if I am not mistaken (the yellow confirmation bar)
The environment veriables method that was pointed out will not get changed, as it specifies the default mounting options OMV uses when it applies the config changes.
omv always uses fstab. omv-extras plugins (remotemount and mergerfs) use systemd mounts.
You will have to edit the mntent entry in the database to change the mount option. Run sudo omv-salt deploy run fstab after.
Actually the change of env variables will only have an effect on newly mounted filesystem. For already mounted systems config.xml has to be changed. This is mentioned in the docu I linked, but might not be very obvious.
You can modify the mount options in the /etc/openmediavault/config.xml file. Look out for something like
<mntent>
<uuid>adc867bb-9fae-4abb-80e0-fa48b4e48ce5</uuid>
<fsname>/dev/disk/by-uuid/b43e258e-5e0c-43e6-8938-f35cf67daa07</fsname>
<dir>/srv/dev-disk-by-uuid-b43e258e-5e0c-43e6-8938-f35cf67daa07</dir>
<type>btrfs</type>
<opts>defaults,nofail</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
<usagewarnthreshold>85</usagewarnthreshold>
<comment></comment>
</mntent>
Alles anzeigen
and set defaults,nofail,ssd,autodefrag for <opts></opts>. Finally run omv-salt deploy run fstab. Make sure to create a backup copy of the config database before doing your modifications.
got it thanks
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!