MergerFS

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • I started getting the same message in the last 48 hours. Had been rock solid for at least 6 months prior to that without issue. If I deleted and created the diskpool while it was up and running it survived a while, but definitely wouldn't survive a reboot.
      I did try changing the boot kernel back a version but that didnt change anything. Eventually I found this on the git for mergerfs and thought it was worth trying at least considering all my shares were based on this pool. Here's what I did to install the later versions which are from Debian Sid I believe.


      Shell-Script

      1. wget http://ftp.au.debian.org/debian/pool/main/f/fuse/fuse_2.9.7-1_amd64.deb
      2. wget http://ftp.au.debian.org/debian/pool/main/f/fuse/libfuse2_2.9.7-1_amd64.deb
      3. dpkg -i fuse_2.9.7-1_amd64.deb libfuse2_2.9.7-1_amd64.deb
      I rebooted after that and the mergefs mount came back up online and everything seems to be reasonably happy. YMMV.
    • I compiled those packages on Jessie quite a while ago. I recommend the packages compiled on Jessie rather than sid.
      omv-extras.org/testing/fuse_jessie/
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • From one of the latest commits to mergerfs repo, it looks like trapexit added libfuse to the mergerfs package so it doesn't depend on the OS installed version.
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • trapexit wrote:

      Correct. v2.22.0 includes libfuse. The general fuse package is still required so you have fusermount and mount.fuse or whatnot but they will work with the version of libfuse included in mergerfs now.


      Trapexit
      I managed to install libfuse 2.9.7.1 previously on Debian Jesse as I was getting transport endpoint problems. And this fixed it. I had to restore from backup and now the transport endpoint errors are back I I can't remember how I installed libfuse2.9.7.1. Can you help


      Sent from my iPhone using Tapatalk
    • 2.22.0 is in the repo and should show up in the Updates tab now.

      Source Code

      1. $ mergerfs -v
      2. mergerfs version: 2.22.0
      3. FUSE library version: 2.9.7
      4. fusermount version: 2.9.3
      5. using FUSE kernel interface version 7.19
      omv 4.1.12 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!

      The post was edited 1 time, last by ryecoaaron ().

    • I'm having the same problem in a fresh installation of OMV3 in a VirtualBox VM.

      The system is updated to the latest version, including mergerfs (v 2.22.0).

      I'm getting Transport endpoint is not connected every time a disk is filled by a file and moveonenospc is set to true: the file filling the disk is left truncated.






      Source Code

      1. # mergerfs -v
      2. mergerfs version: 2.22.0
      3. FUSE library version: 2.9.7
      4. fusermount version: 2.9.3
      5. using FUSE kernel interface version 7.19


      Source Code

      1. # getfattr -d .mergerfs# file: .mergerfs
      2. user.mergerfs.category.action="all"
      3. user.mergerfs.category.create="eplfs"
      4. user.mergerfs.category.search="ff"
      5. user.mergerfs.dropcacheonclose="false"
      6. user.mergerfs.func.access="ff"
      7. user.mergerfs.func.chmod="all"
      8. user.mergerfs.func.chown="all"
      9. user.mergerfs.func.create="eplfs"
      10. user.mergerfs.func.getattr="ff"
      11. user.mergerfs.func.getxattr="ff"
      12. user.mergerfs.func.link="all"
      13. user.mergerfs.func.listxattr="ff"
      14. user.mergerfs.func.mkdir="eplfs"
      15. user.mergerfs.func.mknod="eplfs"
      16. user.mergerfs.func.open="ff"
      17. user.mergerfs.func.readlink="ff"
      18. user.mergerfs.func.removexattr="all"
      19. user.mergerfs.func.rename="all"
      20. user.mergerfs.func.rmdir="all"
      21. user.mergerfs.func.setxattr="all"
      22. user.mergerfs.func.symlink="eplfs"
      23. user.mergerfs.func.truncate="all"
      24. user.mergerfs.func.unlink="all"
      25. user.mergerfs.func.utimens="all"
      26. user.mergerfs.minfreespace="52428800"
      27. user.mergerfs.moveonenospc="true"
      28. user.mergerfs.pid="503"
      29. user.mergerfs.policies="all,epall,epff,eplfs,eplus,epmfs,eprand,erofs,ff,lfs,lus,mfs,newest,rand"
      30. user.mergerfs.srcmounts="/srv/dev-disk-by-label-one:/srv/dev-disk-by-label-two:/srv/dev-disk-by-label-three"
      31. user.mergerfs.symlinkify="false"
      32. user.mergerfs.symlinkify_timeout="3600"
      33. user.mergerfs.version="2.22.0"
      Display All

      Found this in /var/log/kern.log


      Source Code

      1. Jun 23 15:33:10 omv3 kernel: [ 98.853829] mergerfs[506]: segfault at 0 ip 00007fee3d7d0c3a sp 00007fee3cf441d8 error 4 in libc-2.19.so[7fee3d74f000+1a1000]
    • Problem seems solved with last version 2.22.1, thank you trapexit. Tested copying files via shell.

      Is it normal that, with moveonenospc=true, filezilla has a weird behavior and continues to show to "skip/rename/etc." the file untill the same file is written and left truncated in the (filled) HD (see img)?



      Policy are not path preserving.
      Is this a case similar to that reported in the readme on github (rename & link paragraph)?

      The post was edited 1 time, last by rbnet: typos ().

    • The setup is the one published above. It is a fresh and updated test-installation of OMV3 in Virtualbox under Linux (4.10.0-24). In OMV3 I have activated only SSH and FTP (with default options) services and MergerFS (2.22.1) is the only plugin installed. There's only a shared folder created in the MergerFS pool device. I'm using the default options for mergerfs plus moveonenospc=true. That's all. Let me know if you need more infos.
    • I didn't mean your OS and such... I mean... at the time the file is being written what is the directory layouts, size of every drive, files which may or may not exist already, etc. The literal state of the filesystems at the time.

      Regardless... I'm not going to be able to comment about what's going on without a simple reproduction. A clean example. To do that I need the above information + exactly the behavior of the tool. Ideally it'd be reproduced via "mv" or "cp" without me needing a ftp server and filezilla.