Beiträge von Quiksmage

    Just wanted to add in case anyone else ever has this error show up.


    Rebooting the system and running snapraid sync again notified me that the uuid has changed rather than unsupported. subsequent sync had no warning.

    So it appears a reboot solves this issue :).

    Hello,


    I started using BTRFS as the filesystem for my individual disks and noticed that while I have 6 drives in my system using BTRFS (3 data, 3 parity), the newest data drive is stating the following on a snapraid sync.


    WARNING! UUID is unsupported for disks: 'tv4'. Not using inodes to detect move operations.


    The UUID is listed in File Systems, so I'm trying to figure out if I did something wrong with this disk as none of the others are throwing this warning.

    All of the 6 disks are formatted individually the same way with BTRFS as the filesystem.

    OK I think I have it fixed. Needed to reboot, uninstall mergerfs, reboot, and reinstall it.

    wanted to add to this that I just needed to uninstall and reinstall the plugin. rebooting was unecessary for me.

    This is for fixing the error "Failed to execute XPath query '/config/services/mergerfs/pools'." when creating a new pool.

    If you have a large amount of filesystems, it can take a long time too.

    That would make sense I guess since I'm using about 26 disks now. Thanks for letting me know!




    Depends. If your Linux skills are solid, I think it is a good upgrade but I would install fresh over upgrading. There is no OMV provided upgrade path. So, you will have to manually upgrade OMV stuff.

    Is there an improvements or additions changelog in 5? Everything is working quite nicely for me right now, but I'm always interested in newer/better things. If there's not too much different, I'll probably stay as is for a while :D. Thank you for the information.

    Hi everyone. I can't seem to find the ability to search this thread, so I hope this isn't already answered. I have snapraid setup to send an e-mail to me from its nightly sync/scrub per the diff script.


    Everything is working fine except the e-mail is a bit spammy. It gives me every change to the % and time remaining. Is it possible to exclude these redundant lines from the e-mail?


    example below -
    Using 4527 MiB of memory for the FileSystem.
    Initializing...
    Scrubbing...
    Using 168 MiB of memory for 32 blocks of IO cache.
    0%, 2 MB
    0%, 348 MB
    0%, 1487 MB
    0%, 2710 MB
    0%, 3909 MB
    0%, 5143 MB, 1198 MB/s, CPU 72%, 1:53 ETA
    0%, 6331 MB, 1196 MB/s, CPU 72%, 1:53 ETA
    0%, 7568 MB, 1203 MB/s, CPU 72%, 1:53 ETA
    0%, 8767 MB, 1202 MB/s, CPU 72%, 1:53 ETA
    0%, 9975 MB, 1203 MB/s, CPU 72%, 1:53 ETA
    0%, 11201 MB, 1214 MB/s, CPU 71%, 1:52 ETA
    0%, 12415 MB, 1214 MB/s, CPU 71%, 1:52 ETA
    0%, 13614 MB, 1212 MB/s, CPU 71%, 1:52 ETA
    0%, 14846 MB, 1214 MB/s, CPU 71%, 1:52 ETA
    0%, 16045 MB, 1213 MB/s, CPU 71%, 1:52 ETA
    0%, 17262 MB, 1212 MB/s, CPU 71%, 1:52 ETA
    0%, 18476 MB, 1212 MB/s, CPU 70%, 1:52 ETA
    0%, 19704 MB, 1213 MB/s, CPU 70%, 1:52 ETA
    0%, 20880 MB, 1211 MB/s, CPU 70%, 1:52 ETA
    .... all the way to 100%


    is there a way to have this removed from the nightly e-mail?

    I have this exact issue. I logged in via ssh and saw 23 zombie processes.


    After running ps aux | grep Z, I found that I had a list like the first post in here.



    edit: nevermind. Per another post I found


    "And since these zombies die pretty fast (look at your timestamps) it's just the result of monit calling '/bin/mountpoint' to get a clue which mountpoints or directories below /srv or /media belong to which block device (to graph disk utilization or whatever). They come and go most probably every minute or even seconds and are harmless"