GUI hangs - quota check running in background

  • I did a new install of OMV yesterday on my existing system. I am on 5.6.2.1.


    The GUI is unresponsive - I will get a communication error with messages like:


    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color quota 2>&1' with exit code '1': debian: ---------- ID: quota_off_no_quotas_c75776fd-72f7-470a-8d4f-71bcb020bed3 Function: cmd.run Name: quotaoff --group --user /dev/disk/by-uuid/c75776fd-72f7-470a-8d4f-71bcb020bed3 || true Result: True Comment: Command "quotaoff --group --user /dev/disk/by-uuid/c75776fd-72f7-470a-8d4f-71bcb020bed3 || true" run Started: 07:31:35.131664 Duration: 101.865 ms Changes: ---------- pid: 23113 retcode: 0 stderr: stdout: ---------- ID: quota_check_no_quotas_c75776fd-72f7-470a-8d4f-71bcb020bed3 Function: cmd.run Name: quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/c75776fd-72f7-470a-8d4f-71bcb020bed3 Result: True Comment: Command "quotacheck --user --group --create-files --no-remount --verbose /dev/disk/by-uuid/c75776fd-72f7-470a-8d4f-71bcb020bed3" run Started: 07:31:35.233957 Duration: 1072980.357 ms Changes: ---------- pid: 23115 retcode: 0 stderr: quotacheck: Scanning /dev/md127 [/srv/dev-disk-by-uuid-c75776fd-72f7-470a-8d4f-71bcb020bed3] quotacheck: Checked 102831 directories and 769655 files stdout: |/-\|/-\|/-\|/-\|/-\|/-\|/

    If I run top is shows quotacheck is running. Once it stops, the GUI works fine.


    I saw that this was fixed in 5.5.13 I believe, in this post "Quota Error when mounting XFS FileSystem"

    What can I do to get the GUI functionality back?


    Thanks

    Gwarph

  • I now cannot save/apply changes to the GUI. I get the following error:


    Error #0:
    OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color quota 2>&1' with exit code '1': debian: Data failed to compile:
    ---------- Rendering SLS 'base:omv.deploy.quota.default' failed: while constructing a mapping in "<unicode string>", line 42, column 1
    found conflicting ID 'quota_off_no_quotas_' in "<unicode string>", line 96, column 1 in /usr/share/php/openmediavault/system/process.inc:195
    Stack trace:
    #0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
    #1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
    #2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
    #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusLp...', '/tmp/bgoutputnQ...')
    #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
    #7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
    #8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
    #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
    #11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
    #12 {main}


    I think I will wipe out my boot volume again and re-load from scratch.

  • Update 3:

    I reloaded OMV from scratch.

    Everything works fine until I load my ext4 raid array; at that point quota check starts running and the GUI will hang and eventually error out with a communication error.


    I edited /etc/fstab and removed the aquota parameters, but next boot, OMV mounts them with the quota parameters.


    Anyone have an idea on what I can do next?

    • Official Post

    Quotas have been disabled (by default) for a long time in OMV.. this was an issue for users back in early versions of OMV (maybe even pre 1.0 so at least 10yrs ago) so they were disabled.... so I'm assuming you had them on from another system. Just editing fstab won't cut it, as if I'm not mistaken Quota's are a service that needs to be disabled.. the command escapes me at the moment.


    FWIW... If you just give the quotacheck time to finish... (probably 7-10min)... everything will be fine on that first boot.


    ryecoaaron

    • Official Post

    You have to remove the quota parameters from the mntent entries in /etc/openmediavault/config.xml. Backup the file first.

    omv 8.2.2-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.2.1 | compose 8.1.6 | cterm 8.0 | borgbackup 8.1.7 | tempmon 8.0.3 | mergerfs 8.0.1 | scripts 8.0.1 | writecache 8.1.7


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • As said by ryecoaaron , open terminal (or ssh) and:


    sudo cp /etc/openmediavault/config.xml /etc/openmediavault/config.bak


    Then:

    sudo nano /etc/openmediavault/config.xml


    Use Ctrl+W and search for fstab

    Eventually, you'll see some entries like this:

    Now, delete WITH EXTRA CAREFULL the quota parts (--^^^would look like "<opts>defaults....exec,jqfmt=....</opts>"


    After this, Ctrl+O then Enter and then Ctrl+X


    All it's left is:

    sudo omv-salt deploy run fstab


    Now test it with a reboot, ;)

  • FWIW... If you just give the quotacheck time to finish... (probably 7-10min)... everything will be fine on that first boot.

    Yes, I just checked and it had stopped. However, I created some shares on the array and it started up again, but again finished.


    I will give what Soma and ryecoaaron suggested a go tomorrow (I'm backing up the array now).


    Thanks for the responses!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!