OMV cleanup cron fails

  • Since a few days I am getting this error message every hour. I have not changed anything to my system in several weeks.

    Has anyone seen this? Seems to be related to BTRFS cleanup tasks.

    Any ideas how to fix this?


    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

  • I have not done anything. The system has been fixed for at least 1 month. All I did was keeping it up to date with updates.

    Sorry - I dont know how to reproduce it as the above cron job seems to be an OMV system job which I cannot even see.

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

  • output:

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

  • I also noticed that my mergerfs pool is not mounting. The pool has two disks


    Pool1
    /srv/dev-disk-by-uuid-01cc26c2-19ae-48f8-ab41-377f9028a8cf

    /srv/dev-disk-by-uuid-52c56732-4fd7-4cc3-ac37-64760ac981ca


    and this is the error message:

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; systemctl restart srv-mergerfs-Pool1.mount' with exit code '1': 
    
    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; export LANGUAGE=; systemctl restart srv-mergerfs-Pool1.mount' with exit code '1':  in /usr/share/php/openmediavault/system/process.inc:242
    Stack trace:
    #0 /usr/share/openmediavault/engined/rpc/mergerfs.inc(203): OMV\System\Process->execute(Array, 1)
    #1 [internal function]: OMVRpcServiceMergerfs->restartPool(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('restartPool', Array, Array)
    #4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Mergerfs', 'restartPool', Array, Array, 1)
    #5 {main}

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

  • Any ideas about the

    /etc/cron.hourly/openmediavault-cleanup_sf_snapshots:

    error.

    ERROR: Could not destroy subvolume/snapshot: Directory not empty


    It still appears every hour, even after upgrading to latest OMV version.

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

    • Offizieller Beitrag

    You still did not answer my question if this shared folder contains other shared folders.

  • Sorry I didnt see your 2nd question.

    -> No there are no other shared folders inside that folder. Below is the list of all Shared Folders:



    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

  • btrfs subvolume list -o /srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d/.snapshots gives the following output:

    Code
    root@elite2:/srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d#  btrfs subvolume list -o /srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d/.snapshots
    ID 290 gen 49329 top level 289 path .snapshots/LIVE180_20230826T151017
    ID 1877 gen 205521 top level 289 path .snapshots/OMVmoving@hourly_20231029T010001
    ID 2049 gen 202888 top level 289 path .snapshots/LIVE180@daily_20231104T160808
    ID 2058 gen 203770 top level 289 path .snapshots/LIVE180@daily_20231105T000001
    ID 2070 gen 205076 top level 289 path .snapshots/OMVmoving@hourly_20231105T120001
    ID 2071 gen 205186 top level 289 path .snapshots/OMVmoving@hourly_20231105T130001
    ID 2072 gen 205300 top level 289 path .snapshots/OMVmoving@hourly_20231105T140001
    ID 2073 gen 205410 top level 289 path .snapshots/OMVmoving@hourly_20231105T150001

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

  • Did some more digging and there seems to be a problem with a nested sub-volume.

    There is a subvolume

    ID 1878 gen 200649 top level 1877 path OMVmoving@hourly_20231029T010001/OMVmoving


    I dont know how this subvolume got created but it becomes visible with "btrfs subvol list .snapshots"

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

    • Offizieller Beitrag

    btrfs subvolume list -o /srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d/.snapshots gives the following output:

    Code
    root@elite2:/srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d#  btrfs subvolume list -o /srv/dev-disk-by-uuid-786fbfe4-2782-4b41-b28a-9ec8130edb8d/.snapshots
    ID 290 gen 49329 top level 289 path .snapshots/LIVE180_20230826T151017
    ID 1877 gen 205521 top level 289 path .snapshots/OMVmoving@hourly_20231029T010001
    ID 2049 gen 202888 top level 289 path .snapshots/LIVE180@daily_20231104T160808
    ID 2058 gen 203770 top level 289 path .snapshots/LIVE180@daily_20231105T000001
    ID 2070 gen 205076 top level 289 path .snapshots/OMVmoving@hourly_20231105T120001
    ID 2071 gen 205186 top level 289 path .snapshots/OMVmoving@hourly_20231105T130001
    ID 2072 gen 205300 top level 289 path .snapshots/OMVmoving@hourly_20231105T140001
    ID 2073 gen 205410 top level 289 path .snapshots/OMVmoving@hourly_20231105T150001

    You did not execute the command I requested. Please check my last post.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!