Hey sno0k,
you got it. That was my fault. Thanks a lot, bro.
Peter
Finally decided to take the leap and move away from Unraid and over to OMV. After researching extensively about pooling solutions, MergerFS and OMV seem to be a perfect match.
I noticed that the create policies options are not fully up to date for MergerFS as it's missing "Existing path, least free space."
I've already edited /etc/default/openmediavault and added the following:
OMV_FSTAB_MNTOPS_MERGERFS="category.create=eplfs,category.search=newest,defaults,allow_other,moveonenospc=true,minfreespace=20G,fsname=mergerfs"and then ran
omv-mkconf fstab.
After rebooting, I verified if the changes were applied and it appears that EPLFS was not applied:
xattr -l /mnt/storage/.mergerfs
user.mergerfs.srcmounts: /media/840b13bb-6430-4a3c-931f-d21b337c2c31:/media/f197c2ee-66bd-48c5-afe6-0b47593efdb1:/media/acb75912-f70f-452e-abe0-bf804af23143:/media/af80c3e1-713c-4597-bfe9-8fce1ce84b44
user.mergerfs.minfreespace: 21474836480
user.mergerfs.moveonenospc: true
user.mergerfs.policies: all,eplfs,epmfs,erofs,ff,fwfs,lfs,mfs,newest,rand
user.mergerfs.version: 2.11.0
user.mergerfs.pid: 606
user.mergerfs.category.action: all
user.mergerfs.category.create: epmfs
user.mergerfs.category.search: newest
user.mergerfs.func.access: newest
user.mergerfs.func.chmod: all
user.mergerfs.func.chown: all
user.mergerfs.func.create: epmfs
user.mergerfs.func.getattr: newest
user.mergerfs.func.getxattr: newest
user.mergerfs.func.link: all
user.mergerfs.func.listxattr: newest
user.mergerfs.func.mkdir: epmfs
user.mergerfs.func.mknod: epmfs
user.mergerfs.func.open: newest
user.mergerfs.func.readlink: newest
user.mergerfs.func.removexattr: all
user.mergerfs.func.rename: all
user.mergerfs.func.rmdir: all
user.mergerfs.func.setxattr: all
user.mergerfs.func.symlink: epmfs
user.mergerfs.func.truncate: all
user.mergerfs.func.unlink: all
user.mergerfs.func.utimens: allAlso, I am running 3.0.13 for troubleshooting purposes.
Restart engined after defining a new environmental variable
I noticed that the create policies options are not fully up to date for MergerFS as it's missing "Existing path, least free space."
I added an issue on github to add this (and direct_io). Not sure if I can get to it but hopefully HK can.
My mergerfs pool is giving me errors of:ls: cannot access /media/cffcb52b-3582-4a96-bad3-b13481d70ebd: Transport endpoint is not connected
Per https://github.com/trapexit/mergerfs I need FUSE library 2.9.4 or greater to prevent this issue. What's the easiest way to upgrade that library on a fresh install of OMV 2.2.2?
Same probleme here. A restart of the server solves it for a certain time.
Syslog:
File System:
Have you tried installing newer packages as suggested in the mergerfs docs? It links to them.
No I didn't. I typically try to avoid installing things that are outside of the package-manager for that system. I didn't know if there was a clean/easy way to make the package manager get the new files? Is there a repo for Jessie that I could enable that would upgrade the fuse packages without upgrading the system. (though from reading it looks like the jessie fuse is only at 2.9.3) Or is it best to just download and install the packages from the debian sid repository?
The clean/easy way to upgrade those packages is to simply download the newer versions and dpkg -i them. They have no other dependencies and are backwards compatible.
Apparently the new versions of fuse are dependant on libc6 version being grater than 2.17. Current install is 2.13.
root@openmediavault:/# dpkg -i libfuse2_2.9.3-15+deb8u2_amd64.deb
(Reading database ... 36508 files and directories currently installed.)
Preparing to replace libfuse2:amd64 2.9.0-2+deb7u2 (using libfuse2_2.9.3-15+deb8u2_amd64.deb) ...
Unpacking replacement libfuse2:amd64 ...
dpkg: dependency problems prevent configuration of libfuse2:amd64:
libfuse2:amd64 depends on libc6 (>= 2.17); however:
Version of libc6:amd64 on system is 2.13-38+deb7u10.
dpkg: error processing libfuse2:amd64 (--install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libfuse2:amd64I tried upgrading libc6, but that too has dependencies that break something else.
root@openmediavault:/# dpkg -i libc6_2.19-18+deb8u4_amd64.deb
dpkg: regarding libc6_2.19-18+deb8u4_amd64.deb containing libc6:amd64:
libc6:amd64 breaks libtirpc1 (<< 0.2.3)
libtirpc1:amd64 (version 0.2.2-5) is present and installed.
dpkg: error processing libc6_2.19-18+deb8u4_amd64.deb (--install):
installing libc6:amd64 would break libtirpc1:amd64, and
deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
libc6_2.19-18+deb8u4_amd64.debThat's where I stopped. I can keep going down that path and likely resolve all of the dependencies, but I may break something in the process I don't know about. Do I keep trying to upgrade packages individually, or enable sid, or some other solution? Or is OMV 3.0 due out tomorrow and will resolve all of this? 
Installing a new libc is a very bad idea. And no, OMV 3 will not be out tomorrow.
So enabling sid and letting it upgrade libc, fuse and other dependencies may cause problems? Is there any other solution?
Using packages from a release two versions newer? Yep, that will cause problems.
I don't really have a solution. It works fine on Jessie/OMV 3 but OMV3 is not ready yet. Maybe use aufs or mhddfs until OMV 3.x?
I've been experiencing the same problem for several weeks, and it was since an upgrade. Searching around, it appears mhddfs had a bug introduced in 1.39 which causes these segfaults.
Zitatkernel: [344494.334022] mhddfs[8164]: segfault at 1 ip 000000000040443c sp 00007f5144ff89d0 error 4 in mhddfs[400000+a000]
Details are in this post, and its linked pages
http://nramkumar.org/tech/blog…-crash-with-ubuntu-14-04/
Short of rolling back to 1.38, or compiling your own fixed version as per that thread, the easiest fix is
fusermount -zu /media/mountpoint
mount /media/mountpointI've put these two lines in a bash script I can quickly run. I may look to automate it off the back of error logging, but right now it's a quick manual fix and it going down isn't super critical for me, I am more interested in just getting it working again without a reboot.
It would be awesome if we could get the fix detailed in that link built in to the OMV Plugins version.
Maybe use aufs or mhddfs until OMV 3.x?
Looks like MHDDFS is also segfaulting now. The house is on fire!
ZitatI may look to automate it off the back of error logging
If you do end up doing this could you post a quick n dirty tutorial? I am rebooting my server seemingly every day, its not the end of the world but its extremely annoying since I thought I just got everything stable again.
please consider to use mergerfs, have better support and works very fast and reliable.
Would love to switch over to MergerFS but I don't have the swing storage to cut everything over, unless there's a non destructive way to change over? Not super familiar with UFS as a whole, just follow the guides
post more info about how you configure and use your disk, and perhaps can guide to you.
I switch in the past from aufs to mergerfs and where really easy:
Delete aufs pool, recreate pool using same disks using mergerfs , and thats all, all works, and only need to delete some files that aufs use to know things.
To delete aufs pool , first you need that are not references to it on shares folders, so first you neeed to delete your samba shares ( delete your shares not your data on shares), and finally I can delete aufs pool.
once I create the mergerfs pool i need to recreate shares, and samba shares, but it's easy because folders and data exist in pool.
You don't have to delete the pool to change types. Select pool, click Edit, change the type, and reboot. Done. I have done it many times.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!