[LU-9675] SLES 12 SP2 server build fails when ZFS and LDISKFS OSDs are both enabled

Related — Fri, 16 Jun 2017 10:48:07 +0000

The make rpms command will fail on SLES 12 SP2 when both LDISKFS and ZFS are enabled by configure (the default when ZFS is enabled).

OS: SLES 12 SP2
Kernel: 4.4.38-93-default (no Lustre patches)
Lustre: master @ 16/June/2017
(newest commit, 107b2cba7e4a05e2aa7318c20ad7142f88083c35)
ZFS: 0.7.0RC4

If LDISKFS is disabled, the make rpms command will complete and RPMs are created.

A complete transcript is attached, but the following excerpts show the symptom:

./configure --with-linux=/usr/src/linux-4.4.59-92.17 \
--with-linux-obj=/usr/src/linux-4.4.59-92.17-obj/x86_64/default \
--with-zfs

...
checking for /usr/src/linux-4.4.59-92.17/fs/ext4/dir.c... yes checking for /usr/src/linux-4.4.59-92.17/fs/ext4/file.c... yes checking for /usr/src/linux-4.4.59-92.17/fs/ext4/inode.c... yes checking for /usr/src/linux-4.4.59-92.17/fs/ext4/super.c... yes configure: Lustre kernel checks ... checking whether to build ldiskfs... yes checking whether to enable zfs... yes checking spl source directory... /usr/src/spl-0.7.0 checking spl build directory... /usr/src/spl-0.7.0/4.4.59-92.17-default checking spl source version... 0.7.0-rc4_4_gac48361 checking spl file name for module symbols... Module.symvers checking zfs source directory... /usr/src/zfs-0.7.0 checking zfs build directory... /usr/src/zfs-0.7.0/4.4.59-92.17-default checking zfs source version... 0.7.0-rc4_56_g419c80e6d checking zfs file name for module symbols... Module.symvers checking user provided zfs devel headers... checking zfs devel headers... -I/usr/include/libspl -I /usr/include/libzfs checking if zfs defines dsl_pool_config_enter/exit... yes checking if zfs defines dsl_sync_task_do_nowait... no checking if zfs defines sa_spill_alloc... no checking if zfs defines spa_maxblocksize... yes checking if zfs defines dmu_object_alloc_dnsize... yes checking if ZFS has 'dmu_prefetch' with 6 args... yes checking if zfs has native dnode accounting supported... yes checking if ZFS has 'zap_lookup_by_dnode'... yes checking if ZFS has 'zap_add_by_dnode'... yes checking if ZFS has 'zap_remove_by_dnode'... yes checking if ZFS has 'dmu_tx_hold_zap_by_dnode'... yes checking if ZFS has 'dmu_tx_hold_write_by_dnode'... yes checking if ZFS has 'dmu_write_by_dnode'... yes checking if ZFS has 'dmu_read_by_dnode'... yes checking whether to build Lustre server support... yes ...   make rpms ... make[1]: Entering directory '/home/vagrant/lustre-release' make[1]: Leaving directory '/home/vagrant/lustre-release' Installing lustre-2.9.59_15_g107b2cb-1.src.rpm /usr/src/linux-4.4.59-92.17/Makefile:691: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler /usr/src/linux-4.4.59-92.17/Makefile:691: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler /usr/src/linux-4.4.59-92.17/Makefile:691: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector not supported by compiler sh: -c: line 15: unexpected EOF while looking for matching `"' sh: -c: line 17: syntax error: unexpected end of file error: Summary field must be present in package: lustre-osd-zfs-kmp-default autoMakefile:1091: recipe for target 'rpms' failed make: *** [rpms] Error 1

Can flip the options, to create LDISKFS by disabling ZFS.

Looks like perhaps something in the SPEC file that doesn't work cleanly on SLES. Does not appear to happen with RHEL / CentOS.

Whamcloud Community JIRA

[LU-9675] SLES 12 SP2 server build fails when ZFS and LDISKFS OSDs are both enabled