DKMS make.log for veeamsnap-1.0.1.364 for kernel 4.12.5-300.fc26.x86_64 (x86_64)
mar 15 ago 2017, 12.05.42, CEST
make: ingresso nella directory "/usr/src/kernels/4.12.5-300.fc26.x86_64"
Makefile:940: "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
LD /var/lib/dkms/veeamsnap/1.0.1.364/build/built-in.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_array_1lv.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/log.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangeset.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/cbt_map.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/tracker.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/tracker_queue.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapshotdata.o
/var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.c:244:3: error: ‘struct block_device_operations’ has no member named ‘direct_access’
.direct_access = NULL,
^~~~~~~~~~~~~
make[1]: *** [scripts/Makefile.build:302: /var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.o] Error 1
make[1]: *** Attesa per i processi non terminati....
make: *** [Makefile:1519: _module_/var/lib/dkms/veeamsnap/1.0.1.364/build] Error 2
make: uscita dalla directory "/usr/src/kernels/4.12.5-300.fc26.x86_64"
[zakhaif@K-Dell ~] $ cat /var/lib/dkms/veeamsnap/1.0.1.364/build/make.log
DKMS make.log for veeamsnap-1.0.1.364 for kernel 4.12.5-300.fc26.x86_64 (x86_64)
Tue Aug 15 22:36:41 PKT 2017
make: Entering directory '/usr/src/kernels/4.12.5-300.fc26.x86_64'
LD /var/lib/dkms/veeamsnap/1.0.1.364/build/built-in.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_array_1lv.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/log.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangeset.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/cbt_map.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/tracker.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/tracker_queue.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapshotdata.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapdata_collect.o
/var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.c:244:3: error: ‘struct block_device_operations’ has no member named ‘direct_access’
.direct_access = NULL,
^~~~~~~~~~~~~
make[1]: *** [scripts/Makefile.build:302: /var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1519: _module_/var/lib/dkms/veeamsnap/1.0.1.364/build] Error 2
make: Leaving directory '/usr/src/kernels/4.12.5-300.fc26.x86_64'
That's a workaround, not a proper fix, hence it won't be added to the source code. Once our development team get to fix that, the code will be updated accordingly. Also, AFAIK kernel 4.12 is for Debian 9 which is not supported for the current version of VAL.
PTide wrote: Also, AFAIK kernel 4.12 is for Debian 9 which is not supported for the current version of VAL.
No, 4.12 in Debian is for Unstable/Testing (which is not supported officially, I know). Debian 9 has 4.9 which works with the current 1.0.1.364 without problems.
DKMS make.log for veeamsnap-1.0.1.364 for kernel 4.12.9-300.fc26.x86_64 (x86_64)
Wed Sep 6 12:15:33 EDT 2017
make: Entering directory '/usr/src/kernels/4.12.9-300.fc26.x86_64'
Makefile:940: "Cannot use CONFIG_STACK_VALIDATION, please install libelf-dev, libelf-devel or elfutils-libelf-devel"
LD /var/lib/dkms/veeamsnap/1.0.1.364/build/built-in.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_array_1lv.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/log.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/blk_dev_utile.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/dio_request.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangeset.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/defer_io.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/cbt_map.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/tracker.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/tracker_queue.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapshotdata.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/snapdata_collect.o
/var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.c:244:3: error: ‘struct block_device_operations’ has no member named ‘direct_access’
.direct_access = NULL,
^~~~~~~~~~~~~
make[1]: *** [scripts/Makefile.build:302: /var/lib/dkms/veeamsnap/1.0.1.364/build/snapimage.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1519: _module_/var/lib/dkms/veeamsnap/1.0.1.364/build] Error 2
make: Leaving directory '/usr/src/kernels/4.12.9-300.fc26.x86_64'
John F. Roberts
Managed IT Services
Sr.Systems.Engineer
www.bluegrass.net
502.589.INET (4638)
johnr@bluegrass.net
I'm not sure what is the reason the workaround in the previuos posts cannot be posted here, but I can tell you MY PERSONAL workaround that works for me for the last 3 kernels updates...
Please consider it "AS IS" and "WITHOUT WARRANTY"...
1) comment out line 244 in /usr/src/veeamsnap-1.0.1.364/snapimage.c
BEFORE THE COMMENT:
.direct_access = NULL,
AFTER THE COMMENT:
//.direct_access = NULL,
2) recompile and install with dkms:
# dkms build -m veeamsnap -v 1.0.1.364
# dkms install -m veeamsnap -v 1.0.1.364
3) load the module
# modprobe veeamsnap
4) revert changes in /usr/src/veeamsnap-1.0.1.364/snapimage.c
LINE 244:
.direct_access = NULL,
5) backup your disk with veeam!
NOTE: point 4) is for reverting to the original file shipped with veeamsnap package... If you leave ".direct_access" commented out dkms will compile automatically on next kernel update!
# dkms build -m veeamsnap -v 1.0.1.364
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=4.13.5-200.fc26.x86_64 -C /lib/modules/4.13.5-200.fc26.x86_64/build M=/var/lib/dkms/veeamsnap/1.0.1.364/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.13.5-200.fc26.x86_64 (x86_64)
Consult /var/lib/dkms/veeamsnap/1.0.1.364/build/make.log for more information.
DKMS make.log for veeamsnap-1.0.1.364 for kernel 4.13.5-200.fc26.x86_64 (x86_64)
Fri Oct 20 16:49:26 PDT 2017
make: Entering directory '/usr/src/kernels/4.13.5-200.fc26.x86_64'
AR /var/lib/dkms/veeamsnap/1.0.1.364/build/built-in.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_array_1lv.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/1.0.1.364/build/log.o
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c: In function ‘dbg_kmalloc_huge’:
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c:138:55: error: ‘__GFP_REPEAT’ undeclared (first use in this function); did you mean ‘__GFP_RECLAIM’?
ptr = dbg_kmalloc( max_size, flags | __GFP_NOWARN | __GFP_REPEAT);
^~~~~~~~~~~~
__GFP_RECLAIM
/var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.c:138:55: note: each undeclared identifier is reported only once for each function it appears in
make[1]: *** [scripts/Makefile.build:302: /var/lib/dkms/veeamsnap/1.0.1.364/build/mem_alloc.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [Makefile:1516: _module_/var/lib/dkms/veeamsnap/1.0.1.364/build] Error 2
make: Leaving directory '/usr/src/kernels/4.13.5-200.fc26.x86_64'
Well, that is strange. The problem with dkms module not building on 4.12.5 has been fixed long ago and the fix has been included in 2.0.1.665 release. There actually something you could check - please make sure that kernel headers version matches your current booted kernel version. If it does then you should contact our support team directly so they can investigate the logs. Please also post your case ID once you have one.
[spawny@fedora29 ~]$ sudo dkms build -m veeamsnap -v 2.0.1.665
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j4 KERNELRELEASE=4.19.10-300.fc29.x86_64 -C /lib/modules/4.19.10-300.fc29.x86_64/build M=/var/lib/dkms/veeamsnap/2.0.1.665/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.19.10-300.fc29.x86_64 (x86_64)
Consult /var/lib/dkms/veeamsnap/2.0.1.665/build/make.log for more information.
[spawny@fedora29 ~]$ cat /var/lib/dkms/veeamsnap/2.0.1.665/build/make.log
DKMS make.log for veeamsnap-2.0.1.665 for kernel 4.19.10-300.fc29.x86_64 (x86_64)
pon, 31 gru 2018, 12:34:25 CET
make: Wejście do katalogu '/usr/src/kernels/4.19.10-300.fc29.x86_64'
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/log.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/sparse_array_1lv.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/container.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.o
In file included from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.c:4:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h: In function ‘blk_bioset_create’:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: error: implicit declaration of function ‘bioset_create’; did you mean ‘blk_bioset_create’? [-Werror=implicit-function-declaration]
return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
^~~~~~~~~~~~~
blk_bioset_create
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: warning: returning ‘int’ from a function with return type ‘struct bio_set *’ makes pointer from integer without a cast [-Wint-conversion]
return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.o
CC [M] /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_redirect.o
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:303: /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.o] Błąd 1
make[1]: *** Oczekiwanie na niezakończone zadania....
In file included from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_redirect.c:2:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h: In function ‘blk_bioset_create’:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: error: implicit declaration of function ‘bioset_create’; did you mean ‘blk_bioset_create’? [-Werror=implicit-function-declaration]
return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
^~~~~~~~~~~~~
blk_bioset_create
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: warning: returning ‘int’ from a function with return type ‘struct bio_set *’ makes pointer from integer without a cast [-Wint-conversion]
return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.h:2,
from /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.c:2:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h: In function ‘blk_bioset_create’:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: error: implicit declaration of function ‘bioset_create’; did you mean ‘blk_bioset_create’? [-Werror=implicit-function-declaration]
return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
^~~~~~~~~~~~~
blk_bioset_create
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_util.h:121:9: warning: returning ‘int’ from a function with return type ‘struct bio_set *’ makes pointer from integer without a cast [-Wint-conversion]
return bioset_create(64, front_pad, BIOSET_NEED_BVECS | BIOSET_NEED_RESCUER);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_redirect.c: In function ‘blk_redirect_bioset_free’:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_redirect.c:23:3: error: implicit declaration of function ‘bioset_free’; did you mean ‘bvec_free’? [-Werror=implicit-function-declaration]
bioset_free( BlkRedirectBioset );
^~~~~~~~~~~
bvec_free
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.c: In function ‘blk_direct_bioset_free’:
/var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.c:26:3: error: implicit declaration of function ‘bioset_free’; did you mean ‘bvec_free’? [-Werror=implicit-function-declaration]
bioset_free( BlkDirectBioset );
^~~~~~~~~~~
bvec_free
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:303: /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_direct.o] Błąd 1
cc1: some warnings being treated as errors
make[1]: *** [scripts/Makefile.build:303: /var/lib/dkms/veeamsnap/2.0.1.665/build/blk_redirect.o] Błąd 1
make: *** [Makefile:1521: _module_/var/lib/dkms/veeamsnap/2.0.1.665/build] Błąd 2
make: Opuszczenie katalogu '/usr/src/kernels/4.19.10-300.fc29.x86_64'