Arch Linux User Repository

@eblau, some work has been done on this in this branch: https://github.com/archzfs/archzfs/tree/extramodules Unfortunately, I have not had time to finish this yet. Thanks

The git packages have been updated to support kernel 4.11, but it looks like we're going to be waiting for another OpenZFS stable release for the archzfs stable packages: ==> Starting build()... autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I config autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'. libtoolize: copying file 'config/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'config'. libtoolize: copying file 'config/libtool.m4' libtoolize: copying file 'config/ltoptions.m4' libtoolize: copying file 'config/ltsugar.m4' libtoolize: copying file 'config/ltversion.m4' libtoolize: copying file 'config/lt~obsolete.m4' autoreconf: running: /usr/bin/autoconf --force autoreconf: running: /usr/bin/autoheader --force autoreconf: running: automake --add-missing --copy --force-missing configure.ac:43: installing 'config/compile' configure.ac:36: installing 'config/missing' cmd/Makefile.am: installing 'config/depcomp' autoreconf: Leaving directory `.' checking for gawk... gawk checking metadata... META file checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking whether to enable maintainer-specific portions of Makefiles... no checking whether make supports nested variables... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking whether make sets $(MAKE)... yes checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... no checking if : is a manifest tool... no checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking spl author... OpenZFS on Linux checking spl license... GPL checking linux distribution... arch checking default package type... tgz checking whether rpm is available... no checking whether rpmbuild is available... no checking whether spec files are available... yes (rpm/generic/*.spec.in) checking whether dpkg is available... no checking whether dpkg-buildpackage is available... no checking whether alien is available... no checking spl config... kernel checking kernel source directory... /usr/lib/modules/4.11.2-1-ARCH/build checking kernel build directory... /usr/lib/modules/4.11.2-1-ARCH/build checking kernel source version... 4.11.2-1-ARCH checking kernel file name for module symbols... Module.symvers checking whether debugging is enabled... no checking whether basic kmem accounting is enabled... no checking whether detailed kmem tracking is enabled... no checking whether modules can be built... yes checking whether atomic types use spinlocks... no checking whether kernel defines atomic64_t... yes checking whether old 2-argument shrinker exists... no checking whether old 3-argument shrinker exists... no checking whether new 2-argument shrinker exists... no checking whether ->count_objects callback exists... yes checking whether struct ctl_table has ctl_name... no checking whether CONFIG_TRIM_UNUSED_KSYM is disabled... yes checking whether PDE_DATA() is available... yes checking whether set_fs_pwd() requires const struct path *... yes checking whether vfs_unlink() wants 2 args... no checking whether vfs_unlink() wants 3 args... yes checking whether vfs_rename() wants 4 args... no checking whether vfs_rename() wants 5 args... no checking whether vfs_rename() wants 6 args... yes checking whether vfs_fsync() wants 2 args... yes checking whether truncate_range() inode operation is available... no checking whether struct fs_struct uses spinlock_t... yes checking whether kuid_t/kgid_t is available... yes; mandatory checking whether __put_task_struct() is available... no checking whether fops->fallocate() exists... yes checking whether iops->fallocate() exists... no checking whether fops->fallocate() exists... no checking whether CONFIG_ZLIB_INFLATE is defined... yes checking whether CONFIG_ZLIB_DEFLATE is defined... yes checking whether zlib_deflate_workspacesize() wants 2 args... yes checking whether struct shrink_control exists... yes checking whether struct rw_semaphore member wait_lock is raw... yes checking whether struct rw_semaphore has member activity... no checking whether struct rw_semaphore has atomic_long_t member count... yes checking whether header linux/sched/rt.h exists... yes checking whether vfs_getattr() wants... configure: error: unknown ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Build failed, check /opt/chroot/x86_64/demizer/build Thanks!

Is it possible to install the zfs-linux and zfs-linux-lts family of packages side-by-side? Does anyone have a suggestion on how to do so? Currently there are file conflicts so this can't be done easily. You must choose one or the other set of packages. I had to revert to linux-lts recently due to bugs in the 4.10.x "stable" series for i915 that cause complete system hangs with no plans to supply fixes to 4.10.x. See: https://bugs.freedesktop.org/show_bug.cgi?id=99295 It would be great if the ZFS packages could live together on the same system just like linux and linux-lts can. It seems that if the ZFS version is the same, the packages could be restructured in such a way that the modules don't conflict and any headers or supplementary files from ZFS could live in one place. Am I oversimplifying the problem? Any suggestions on an approach to try to help with this? Do I need to move to the dkms packages?

@ShaunPC thanks for the explanation. I reinstalled 23-1 and rebooted without any issue.

@gmtch you can allow mkinitcpio generate the image and reboot using 23-1. The module that couldn't be found does exist in the kernel already. A commit to mkinitcpio will check for built-in modules like this one in a later update. The check was missing and as a result the error was produced when there wasn't really an error. I did the update with 23-1 and rebooted after the error was produced on the screen. No issues to report. It seems to be a non-error due to 23-1 not checking for built-in modules.

I got the same error as ShaunPC at 2017-03-15 02:46 and downgraded to mkinitcpio-22-1 The initramfs built okay and box rebooted without problem.

When doing an update I got the following error: (21/21) upgrading zfs-linux [##########################################################################] 100% >>> Updating ZFS module dependencies >>> Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default' -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img ==> Starting build: 4.10.2-1-ARCH -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect] -> Running build hook: [modconf] -> Running build hook: [block] -> Running build hook: [keyboard] -> Running build hook: [zfs] ==> ERROR: module not found: `zlib_deflate' -> Running build hook: [filesystems] -> Running build hook: [shutdown] ==> Generating module dependencies ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img ==> WARNING: errors were encountered during the build. The image may not be complete. I'm not sure what I can do to fix this, if anything. Update: Found a related bug https://bugs.archlinux.org/task/53304 Module errors during build with mkinitcpio 23-1, however, it doesn't seem to break anything.

Thanks for the quick package update for linux-4.10.2_1-1!

Hi, everyone. Until now, I have waited at least 24 hours before updating ZFS, in order for you to be my guinea pigs. Starting today, that is no more. I'm moving to the front lines. Happy scrubbing.

@Lindhe I had the same problem. I found that I got the 4.9.11-1 update by doing 'pacman -Syyu' instead of 'pacman -Syu'. This will force a refresh of the available packages, even if pacman thinks it has the latest. Hope that helps.