Hi all. I just upgraded (fresh new installation) from 0.4 to 1.0. I like the new aufs plugins, I already used myself with 0.4 version.
Change request: is it possible to see the aufs filesystem in the storage -> filesystem section? It's quite interesting to see the amount of space used and available in a pool like the CLI df -h does.
Improvement: it seems that a resource limit is raised when a filesystem achieves 80% of used space. When you have 3 TB hard disks, 80% means 600GB free which is not low. Now if you have 3 same hard disks in a aufs pool, 1.8 TB is of course still huge. So is it possible to modify the resource limit threshold by hard disk, according his size, and add a resource limit in the same way to an aufs pool?
Thanks all for your great job.
Aufs & resource limit
-
- OMV 1.0
- gelöst
- viald
-
-
It will be possible to add it to filesystems soon with the changes being made in OMV now (I think).
To change the resource limit threshold (change 80 to whatever you want)
echo "OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=80" >> /etc/default/openmediavault -
Thanks ryecoaaron, I'll give a try to the threshold setting.
-
It works like a charm. Thank you.
-
It would be very nice to me to set this threshold individually.
So I have tried to set the threshold in the /etc/default/openmediavault like in the post above:
But is has no effect, i still get these monit messages:Zitat...
Description: space usage 80.4% matches resource limit [space usage>80.0%]
...
Any idea why it is not working for me?Thanks.
kalleomv 1.1 - 64 bit - 3.16 backport kernel
-
would you please post the output of
cat /etc/default/openmediavault -
I just started my server with this settings:
Code
Alles anzeigenroot@server:~# cat /etc/default/openmediavault # This file is part of OpenMediaVault. # # @license http://www.gnu.org/licenses/gpl.html GPL Version 3 # @author Volker Theile <volker.theile@openmediavault.org> # @copyright Copyright (c) 2009-2014 Volker Theile # # OpenMediaVault is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # any later version. # # OpenMediaVault is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with OpenMediaVault. If not, see <http://www.gnu.org/licenses/>. # Default values OMV_CONFIG_FILE="/etc/openmediavault/config.xml" OMV_CONFIG_TEMPLATE_FILE="/usr/share/openmediavault/templates/config.xml" OMV_PRODUCTINFO_FILE="/usr/share/openmediavault/productinfo.xml" OMV_SCRIPTS_DIR="/usr/share/openmediavault/scripts" OMV_I18N_LOCALE_DIR="/usr/share/openmediavault/locale" OMV_MOUNT_DIR="/media" OMV_NFSD_EXPORT_DIR="/export" OMV_CACHE_DIR="/var/cache/openmediavault" OMV_LOG_DIR="/var/log/openmediavault" OMV_CERTIFICATE_DIR="/etc/ssl" OMV_CERTIFICATE_PREFIX="openmediavault-" OMV_DPKGARCHIVE_DIR="/var/cache/openmediavault/archives" OMV_DOCUMENTROOT_DIR="/var/www/openmediavault" OMV_CRONSCRIPTS_DIR="/var/lib/openmediavault/cron.d" OMV_CONFIGIMPORT_SCRIPTS_DIR="/usr/share/openmediavault/configimport" OMV_MKCONF_SCRIPTS_DIR="/usr/share/openmediavault/mkconf" OMV_ENGINED_DIR="/usr/share/openmediavault/engined" OMV_ENGINED_SO_ADDRESS="/var/lib/openmediavault/engined.sock" OMV_ENGINED_SO_SNDTIMEO=10 OMV_ENGINED_SO_RCVTIMEO=180 OMV_ENGINED_DIRTY_MODULES_FILE="/var/lib/openmediavault/dirtymodules.json" OMV_INITSYSTEM_SCRIPTS_DIR="/usr/share/openmediavault/initsystem" OMV_INITSYSTEM_FILE="/var/lib/openmediavault/initsystem.req" OMV_FSTAB_MNTOPS_EXT2="defaults,nofail,acl,user_xattr,noexec" OMV_FSTAB_MNTOPS_EXT3="defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0" OMV_FSTAB_MNTOPS_EXT4="defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0" OMV_FSTAB_MNTOPS_JFS="defaults,nofail,noexec,usrquota,grpquota" OMV_FSTAB_MNTOPS_XFS="defaults,nofail,noexec,usrquota,grpquota" OMV_FSTAB_MNTOPS_VFAT="defaults,nofail" OMV_FSTAB_MNTOPS_NTFS="defaults,nofail" OMV_FSTAB_MNTOPS_HFSPLUS="defaults,nofail,force" OMV_USERMGMT_DEFAULT_GROUP="users" OMV_RRDGRAPH_DIR="/var/lib/openmediavault/rrd" OMV_RRDGRAPH_ERROR_IMAGE="/usr/share/openmediavault/icons/rrd_graph_error_64.png" OMV_WEBGUI_FILE_OWNERGROUP_NAME="openmediavault" OMV_DEBUG_SCRIPT="NO" OMV_DEBUG_PHP="NO" OMV_DEBUG_EXTJS="NO" OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=90
... and still get this "space usage>80.0%" mails by monit.
Any idea?
-
You probably need to run something like omv-mkconf monit and then service monit restart so the new config can be generated and used
-
And check here if the EV has being loaded /etc/monit/conf.d/openmediavault-filesystem.conf properly
-
That's the trick. Now, it works. The openmediavault-filesystem.conf looks good now.
An other question: Can I edit the openmediavault-filesystem.conf directly to set different space limits for each drive?
Or is this file newly generated on every startup?Thanks a lot.
kalle -
Not on every startup, but probably with OMV Updates.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!