Segmentation Fault - Mergerfs - File System Crash

  • I recently switched from AUFs to Mergerfs for Union File System. Over a week span, I had two instance where the file system shutdown. If I was to go to "Physical Disk" it would show all of the drives as N/A. None of the applications that used those UFS disk would work until I rebooted. After digging into the syslogs, I found the following.



    May 23 20:45:01 OMV /USR/SBIN/CRON[11560]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1)
    May 23 20:45:01 OMV rrdcached[2739]: Received FLUSHALL
    May 23 20:45:53 OMV kernel: [154612.471549] Plex Media Serv[11892]: segfault at 0 ip 00007fd3caaa82e0 sp 00007fd3bc3fe9d0 error 4 in libboost_system.so.1.59.0[7fd3caa96000+24000]
    May 23 20:45:59 OMV collectd[5259]: statvfs(/media/9c8471a3-0952-46d4-9e54-b644c0a471dd) failed: Transport endpoint is not connected
    May 23 20:46:09 OMV collectd[5259]: statvfs(/media/9c8471a3-0952-46d4-9e54-b644c0a471dd) failed: Transport endpoint is not connected
    May 23 20:46:19 OMV collectd[5259]: statvfs(/media/9c8471a3-0952-46d4-9e54-b644c0a471dd) failed: Transport endpoint is not connected


    All SMART test on HDDs are showing good health. Does anyone have any direction I could go with this one?


    Additional Info:
    https://github.com/vdudouyt/mhddfs-nosegfault
    http://nramkumar.org/tech/blog…-crash-with-ubuntu-14-04/


    Kind Regards,
    Cody

    • Offizieller Beitrag

    This is probably related to Debian Wheezy using Fuse 2.9.0. Mergerfs needs a newer version - read. Debian jessie has a newer version and it works fine. I would keep using aufs until OMV 3.x is ready.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Thank you for this trapexit. My libfuse is 2.9. I noticed an updated through OMV today to 2.9.3 which is not quite the 2.9.4 recommended on your page. Based upon ryecoaaron's post, I would assume the safe approach is to wait and only update through OMV vs manually updating to a newer libfuse.

    • Offizieller Beitrag

    I uploaded fuse 2.9.3. I have been using mergerfs on jessie for months which is the package I built from. So, I think it is safe to use and better than staying with 2.9.0.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Thanks for the help guys. I have updated fuse to 2.9.3 and went back to mergefs (Most Free Space) and have been crash free.

    Would you mind explain how do you install fuse 2.9.3 ? I'm on 2.x OMV branch.
    Tried with with wheezy-backport but with no luck.


    Thanks

  • I don't think 2.9.3 available on 2.0


    Sent from my phone

    omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
    SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
    PSU: Silencer 760 Watt ATX Power Supply
    IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
    OS on 2×120 SSD in RAID-1 |
    DATA: 3x3T| 4x2T | 2x1T

    • Offizieller Beitrag

    I built fuse 2.9.3 for wheezy and put it in the stoneburner backports repo. If you install the backports kernel from omv-extras using the button in omv-extras, it will enable this repo and the new version of fuse will show up in updates.

    omv 7.0-32 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.9 | compose 7.0.9 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Nice, I thought 2.9.3 was only on 3.0


    Sent from my phone

    omv 3.0.56 erasmus | 64 bit | 4.7 backport kernel
    SM-SC846(24 bay)| H8DME-2 |2x AMD Opteron Hex Core 2431 @ 2.4Ghz |49GB RAM
    PSU: Silencer 760 Watt ATX Power Supply
    IPMI |3xSAT2-MV8 PCI-X |4 NIC : 2x Realteck + 1 Intel Pro Dual port PCI-e card
    OS on 2×120 SSD in RAID-1 |
    DATA: 3x3T| 4x2T | 2x1T

Jetzt mitmachen!

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