2017-11-20 23:38 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001843openmediavaultBugpublic2017-11-04 09:31
Reporterpetaramesh 
Assigned Tovotdev 
PrioritylowSeverityminorReproducibilityalways
StatusresolvedResolutionunable to reproduce 
Product VersionArrakis (4.x) 
Target VersionFixed in Version 
Summary0001843: OMV_FSTAB_MNTOPS_BTRFS ignored in /etc/default/openmediavault
DescriptionHello,

According to Volker in https://forum.openmediavault.org/index.php/Thread/8778-BTRFS-support-mount-options/?postID=81858#post81858 it should be possible to specify BTRFS default mount options using

OMV_FSTAB_MNTOPS_BTRFS in /etc/default/openmediavault

However this is ignored (and was already ignored in OMV 3.x)

It seems that setting the option in /usr/share/php/openmediavault/globals.inc works, but it is overwritten when OMV is upgraded.

Also, the default options for BTRFS in /usr/share/php/openmediavault/globals.inc should _absolutely_ contain "noatime" (because NOT using noatime with BTRFS causes terrible performance issues).

Kind regards.
TagsNo tags attached.
Product buildVersion: 4.0.8-1
Attached Files

-Relationships
+Relationships

-Notes

~0005012

votdev (administrator)

Did you restart omv-engined after you've changed /etc/default/openmediavault?

~0005014

petaramesh (reporter)

I don't think I specifically restarted omv-engined, but I've set this option back somewhere in 2015 and it's been ignored since and over reboots...

~0005016

votdev (administrator)

I can not reproduce this. After setting 'OMV_FSTAB_MNTOPS_BTRFS="defaults,nofail,noatime"' in /etc/default/openmediavault and restarting the omv-engined daemon the fstab options are taken into action when a BTRFS file system is mounted.
If the file system is already mounted via UI then the modifications are NOT taken into action because the mount point information is already stored in the database then.
+Notes

-Issue History
Date Modified Username Field Change
2017-11-03 10:11 petaramesh New Issue
2017-11-03 10:11 petaramesh Status new => assigned
2017-11-03 10:11 petaramesh Assigned To => votdev
2017-11-03 23:37 votdev Note Added: 0005012
2017-11-03 23:41 petaramesh Note Added: 0005014
2017-11-04 09:31 votdev Status assigned => resolved
2017-11-04 09:31 votdev Resolution open => unable to reproduce
2017-11-04 09:31 votdev Note Added: 0005016
+Issue History