fuse-exfat-1.3.0_1 won't mount drives with udevil

[Gigahawk]

System

• xuname:
  Void 4.18.7_2 GenuineIntel notuptodate rrrmFFFFFF
• package:
  fuse-exfat

Expected behavior

udevil will mount an exfat drive in /media/, creating that folder if it is not already there.

Actual behavior

If the folder doesn't exist, fuse-exfat will error out with

FUSE exfat 1.3.0
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option

Steps to reproduce the behavior

udevil mount /dev/<drive>

I'm guessing there's some issue with the way the new version of fuse-exfat handles (or doesn't handle) nonempty, since that option is set by default with udevil. Passing it in manually doesn't seem to do anything either.

Regular mounting by creating a folder and using sudo mount still works fine, and provided the folder you create remains, udevil will also work, but it won't delete the folder after you unmount.

[ghost]

Solved on my end installing kernel driver
exfat-dkms-1.2.8_5 Exfat kernel driver (nofuse) <---
exfat-utils-1.3.0_1 Utilities for exFAT file system
fuse-exfat-1.3.0_1 Free exFAT file system implementation

[Gigahawk]

Tried this, I can't seem to get it to build on install or using dkms autoinstall.

make.log shows this:

DKMS make.log for exfat-1.2.8 for kernel 4.18.19_1 (x86_64)
Sat Nov 17 03:01:59 PST 2018
make -C /lib/modules/4.18.19_1/build M=/var/lib/dkms/exfat/1.2.8/build modules
make[1]: Entering directory '/usr/src/kernel-headers-4.18.19_1'
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_core.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_core.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_core.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_core.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_super.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_super.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_super.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_super.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_api.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_api.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_api.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_api.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_blkdev.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_blkdev.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_blkdev.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_blkdev.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_cache.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_cache.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_cache.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_cache.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_data.o
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_bitmap.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_bitmap.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_bitmap.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_bitmap.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_nls.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_nls.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_nls.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_nls.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_oal.o
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_oal.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_oal.o: unable to initialize decompress status for section .debug_info
objdump: /var/lib/dkms/exfat/1.2.8/build/.tmp_exfat_oal.o: File format not recognized
  CC [M]  /var/lib/dkms/exfat/1.2.8/build/exfat_upcase.o
  LD [M]  /var/lib/dkms/exfat/1.2.8/build/exfat.o
ld: /var/lib/dkms/exfat/1.2.8/build/exfat_core.o: unable to initialize decompress status for section .debug_info
ld: /var/lib/dkms/exfat/1.2.8/build/exfat_core.o: unable to initialize decompress status for section .debug_info
ld: /var/lib/dkms/exfat/1.2.8/build/exfat_core.o: unable to initialize decompress status for section .debug_info
ld: /var/lib/dkms/exfat/1.2.8/build/exfat_core.o: unable to initialize decompress status for section .debug_info
/var/lib/dkms/exfat/1.2.8/build/exfat_core.o: file not recognized: File format not recognized
make[2]: *** [scripts/Makefile.build:530: /var/lib/dkms/exfat/1.2.8/build/exfat.o] Error 1
make[1]: *** [Makefile:1505: _module_/var/lib/dkms/exfat/1.2.8/build] Error 2
make[1]: Leaving directory '/usr/src/kernel-headers-4.18.19_1'
make: *** [Makefile:35: all] Error 2

[Johnnynator]

@Gigahawk Is your system up to date? The compile time error of exfat-dkms with linux4.18 should be fixed in the current exfat-dkms package. Maybe you also have to clean the build directory manually.

[Gigahawk]

I installed it after running xbps-install -Su and then rebooting. Navigating to the folder and running make clean and make results in the same error.

I don't think it's an issue with exfat-dkms since tp_smapi wasn't recompiling properly either during xbps-install -Su

[Johnnynator]

Mh... I don't have a Clue what could cause unable to initialize decompress status for section .debug_info. I also can't reproduce it locally..

[pullmoll]

I see this error after updating a laptop. It now fails to build e.g. dkms module rtl8812au-dkms giving me exactly this error. I booted into 4.18.18 to have the previously built module for WIFI.

xuname: Void 4.18.18_1 x86_64 AuthenticAMD uptodate F

Which dependency of the dkms build process did recently change?

Here's an example compiler and tools/objtool/objtool call which then make objdump print the error:

  gcc -Wp,-MD,/usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/.HalHWImg8821A_MAC.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-unknown-linux-gnu/8.2.0/include -I./arch/x86/include -I./arch/x86/include/generated  -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -Werror-implicit-function-declaration -Wno-format-security -std=gnu89 -fno-PIE -DCC_HAVE_ASM_GOTO -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 -DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 -DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 -DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -DRETPOLINE -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-int-in-bool-context -O2 --param=allow-store-data-races=0 -Wframe-larger-than=1024 -fstack-protector-strong -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mfentry -DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=./= -Wno-packed-not-aligned -mrecord-mcount -O1 -Wall -Werror -Wframe-larger-than=1536 -Wno-unused-parameter -I/usr/src/rtl8812au-4.3.14/include -I/usr/src/rtl8812au-4.3.14/platform -DCONFIG_RTL8812A -DCONFIG_RTL8821A -DCONFIG_MP_INCLUDED -DCONFIG_POWER_SAVING -DCONFIG_TRAFFIC_PROTECT -DCONFIG_LOAD_PHY_PARA_FROM_FILE -DREALTEK_CONFIG_PATH=\"\" -DCONFIG_RTW_ADAPTIVITY_EN=0 -DCONFIG_RTW_ADAPTIVITY_MODE=0 -DCONFIG_BR_EXT '-DCONFIG_BR_EXT_BRNAME="'br0'"' -DCONFIG_LITTLE_ENDIAN -DCONFIG_IOCTL_CFG80211 -DRTW_USE_CFG80211_STA_EVENT  -DMODULE  -DKBUILD_BASENAME='"HalHWImg8821A_MAC"' -DKBUILD_MODNAME='"rtl8812au"' -c -o /usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/.tmp_HalHWImg8821A_MAC.o /usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/HalHWImg8821A_MAC.c
   ./tools/objtool/objtool orc generate  --module --no-fp  --retpoline "/usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/.tmp_HalHWImg8821A_MAC.o";
objdump: /usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/.tmp_HalHWImg8821A_MAC.o: unable to initialize decompress status for section .debug_info
objdump: /usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/.tmp_HalHWImg8821A_MAC.o: unable to initialize decompress status for section .debug_info
objdump: /usr/src/rtl8812au-4.3.14/hal/OUTSRC/rtl8821a/.tmp_HalHWImg8821A_MAC.o: File format not recognized

FWIW with binutils-2.31.1 from #4312 I can build rtl8812au-dkms on my other box.

[pullmoll]

This seems to be the bug in binutils-2.29.1:
https://lists.gnu.org/archive/html/bug-binutils/2015-07/msg00038.html

Installing binutils-2.31.1 on the laptop where the build fails does not solve the problem.

[pullmoll]

Uh, so it was elfutils-0.175 ...

[Gigahawk]

@biopsin seems to install correctly now (at least on the kernel I'm running) but the same error still persists.

I'm not entirely sure that the kernel module is being loaded properly though, lsmod | grep exfat shows nothing and manually loading with modprobe exfat still results in the same error.

[ghost]

Think you should head over to https://github.com/dorimanx/exfat-nofuse , I see folks are having issues with newer kernels, as I'm still on 4.9

Also see pull request dorimanx/exfat-nofuse#137

edit: but I too had switch to the the kernel driver as fuse-exfat is broken with udevil
edit: just did a switch back to fuse-exfat after removing the exfat-dkms and udevil mounts the drive without issue. So there was something broken..