veeam / veeamsnap Goto Github PK
View Code? Open in Web Editor NEWVeeam Agent for Linux kernel module
License: GNU General Public License v2.0
veeamsnap's People
Contributors
Stargazers
Watchers
Forkers
codeimp shasthojoy myena hy37id xrzhao okatkov zombig elnino09 mosdev82 angustohrallegrinski intika-linux-kernel mike2307 xiaoquqi ale67uyes chunbee lbuchli lokibunny halianelf sergeishtepa alexpilotti aznashwan qwertiko gabriel-samfira joker234 jmpq qqshow reinhardvz nickchen-cpu mohankadali ows-hub kisun-bit cloudbase honor6 got99 dinghuaming gluka-cbsveeamsnap's Issues
Unable to install veeamsnap-5.0.0.4318 on Debian 10.8
Hello,
I have an error with latest veeamsnap package (official veeam repo) on my NAS :
- Kernel : 5.10.0-0.bpo.3-amd64
- OS : OpenMediaVault 5.6.2 (Debian 10.8)
- Package : veeamsnap-5.0.0.4318
Loading new veeamsnap-5.0.0.4318 DKMS files...
Building for 5.10.0-0.bpo.3-amd64
Building initial module for 5.10.0-0.bpo.3-amd64
Error! Bad return status for module build on kernel: 5.10.0-0.bpo.3-amd64 (x86_64)
Consult /var/lib/dkms/veeamsnap/5.0.0.4318/build/make.log for more information.
Here's the make.log :
DKMS make.log for veeamsnap-5.0.0.4318 for kernel 5.10.0-0.bpo.3-amd64 (x86_64)
dimanche 7 mars 2021, 13:03:17 (UTC+0100)
make : on entre dans le répertoire « /usr/src/linux-headers-5.10.0-0.bpo.3-amd64 »
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/log.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/container.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangelist_ex.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.o
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c: In function ‘blk_dev_open’:
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:17:15: error: implicit declaration of function ‘bdget’; did you mean ‘dget’? [-Werror=implicit-function-declaration]
blk_dev = bdget( dev_id );
^~~~~
dget
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:17:13: warning: assignment to ‘struct block_device *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
blk_dev = bdget( dev_id );
^
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:26:16: error: implicit declaration of function ‘blkdev_get’; did you mean ‘blkdev_put’? [-Werror=implicit-function-declaration]
refCount = blkdev_get( blk_dev, FMODE_READ | FMODE_WRITE, NULL );
^~~~~~~~~~
blkdev_put
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_direct.o
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-5.10.0-0.bpo.3-common/scripts/Makefile.build:284: /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.o] Error 1
make[2]: *** Attente des tâches non terminées....
make[1]: *** [/usr/src/linux-headers-5.10.0-0.bpo.3-common/Makefile:1817: /var/lib/dkms/veeamsnap/5.0.0.4318/build] Error 2
make: *** [/usr/src/linux-headers-5.10.0-0.bpo.3-common/Makefile:185: __sub-make] Error 2
make : on quitte le répertoire « /usr/src/linux-headers-5.10.0-0.bpo.3-amd64 »
Linux 5.6: failed to compile
Making all...
ccflags-y= -O2 -Wno-multichar -DDISTRIB_NAME_ARCH -DDISTRIB_VERSION_1=1
make -C /lib/modules/5.6.2-arch1-2/build M=/tmp/veeamsnap/source modules
make[1]: Entering directory '/usr/lib/modules/5.6.2-arch1-2/build'
CC [M] /tmp/veeamsnap/source/log.o
In file included from /tmp/veeamsnap/source/stdafx.h:39,
from /tmp/veeamsnap/source/log.c:1:
/tmp/veeamsnap/source/log.h:25:80: error: unknown type name ‘time_t’
25 | void log_s_sec(const char* section, const unsigned level, const char* s, const time_t totalsecs);
| ^~~~~~
/tmp/veeamsnap/source/log.c:43:21: error: field ‘m_time’ has incomplete type
43 | struct timespec m_time;
| ^~~~~~
/tmp/veeamsnap/source/log.c:68:21: error: field ‘m_modify_time’ has incomplete type
68 | struct timespec m_modify_time;
| ^~~~~~~~~~~~~
/tmp/veeamsnap/source/log.c: In function ‘_logging_filename_create’:
/tmp/veeamsnap/source/log.c:187:9: error: implicit declaration of function ‘getnstimeofday’ [-Werror=implicit-function-declaration]
187 | getnstimeofday(&logging->m_modify_time);
| ^~~~~~~~~~~~~~
/tmp/veeamsnap/source/log.c: In function ‘_logging_check_renew’:
/tmp/veeamsnap/source/log.c:224:21: error: storage size of ‘_time’ isn’t known
224 | struct timespec _time;
| ^~~~~
/tmp/veeamsnap/source/log.c:224:21: warning: unused variable ‘_time’ [-Wunused-variable]
/tmp/veeamsnap/source/log.c: In function ‘logging_init’:
/tmp/veeamsnap/source/log.c:454:49: error: invalid application of ‘sizeof’ to incomplete type ‘struct timespec’
454 | memset( &logging->m_modify_time, 0, sizeof( struct timespec ) );
| ^~~~~~
/tmp/veeamsnap/source/log.c: At top level:
/tmp/veeamsnap/source/log.c:692:80: error: unknown type name ‘time_t’
692 | void log_s_sec(const char* section, const unsigned level, const char* s, const time_t totalsecs)
| ^~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:268: /tmp/veeamsnap/source/log.o] Error 1
make[1]: *** [Makefile:1683: /tmp/veeamsnap/source] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.6.2-arch1-2/build'
make: *** [Makefile:77: all] Error 2Can veeamsnap be used alone?
Hello,
I want to know if my computer doesn't install the veeam agent for linux, this kernel module "veeamsnap" could be used alone for volume snapshot ?
Unable to patch Linux Kernel 5.10.24 on debian 10
Hello,
I'm trying to bypass the problematic encountered by veeam with Linux kernel > 5.8.
I downloaded Linux kernel sources on debian and when I want to patch the kernel by following your instructions, an error occurs with the patch v5-0003-block-add-blk_interposer.patch and genhd.c source file.
Below the log output from patch command :
root@debian-vm:~/linux/linux-source-5.10# patch -p1 <../v5-0002-block-add-blk_mq_is_queue_frozen.patch
patching file block/blk-mq.c
Hunk #1 succeeded at 159 (offset -2 lines).
patching file include/linux/blk-mq.h
Hunk #1 succeeded at 524 (offset -1 lines).
root@debian-vm:~/linux/linux-source-5.10# patch -p1 <../v5-0003-block-add-blk_interposer.patch
patching file block/bio.c
patching file block/blk-core.c
Hunk #1 succeeded at 1031 (offset -1 lines).
Hunk #2 succeeded at 1084 (offset -1 lines).
patching file block/genhd.c
Hunk #1 FAILED at 30.
Hunk #2 succeeded at 2367 (offset 218 lines).
1 out of 2 hunks FAILED -- saving rejects to file block/genhd.c.rej
patching file include/linux/blk_types.h
Hunk #1 succeeded at 207 (offset -20 lines).
Hunk #2 succeeded at 284 (offset -20 lines).
Hunk #3 succeeded at 304 (offset -20 lines).
patching file include/linux/genhd.h
Hunk #1 succeeded at 164 (offset 30 lines).
Hunk #2 succeeded at 195 (offset 30 lines).
Hunk #3 succeeded at 417 (offset 63 lines).
root@debian-vm:~/linux/linux-source-5.10#
I also tried with a mainstream kernel from kernel.org (5.11.16, latest stable) and it works fine.
Can you help me to debug and solve this issue ?
Thanks a lot for your help.
Change block tracking map is always zeroes on newer kernels (>5.11)
Every time we create new snapshots on machines that have kernel versions >=5.11, the CBT bitmap is always returned as a bunch of zeros, whereas on older kernels this works as expected (I.E. Ubuntu 20.04 with kernel 5.4).
This was first identified on Ubuntu 22.04 machines, that run kernel 5.15 by default. We tested Ubuntu 20.04 as well, works well by default. Once we upgrade Ubuntu 20.04's kernel from 5.4 to 5.15, the same behavior occurs. Every snapshot returns zeroed CBT map.
Have you encountered this so far?
veeamsnap has been built from master on all machines.
Veeamsnap not installing on Debian 11
Can't install veeamsnap-5.0.0.4318 after upgrading to Debian 11 Bullseye.
Error! Bad return status for module build on kernel: 5.10.0-8-amd64 (x86_64)
make: Entering directory '/usr/src/linux-headers-5.10.0-8-amd64'
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/log.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/container.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/container_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/queue_spinlocking.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/bitmap_sync.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/page_array.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangelist.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangelist_ex.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/rangevector.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_direct.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_redirect.o
CC [M] /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_deferred.o
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c: In function ‘blk_dev_open’:
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:17:15: error: implicit declaration of function ‘bdget’; did you mean ‘dget’? [-Werror=implicit-function-declaration]
17 | blk_dev = bdget( dev_id );
| ^~~~~
| dget
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:17:13: warning: assignment to ‘struct block_device *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
17 | blk_dev = bdget( dev_id );
| ^
/var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.c:26:16: error: implicit declaration of function ‘blkdev_get’; did you mean ‘blkdev_put’? [-Werror=implicit-function-declaration]
26 | refCount = blkdev_get( blk_dev, FMODE_READ | FMODE_WRITE, NULL );
| ^~~~~~~~~~
| blkdev_put
cc1: some warnings being treated as errors
make[2]: *** [/usr/src/linux-headers-5.10.0-8-common/scripts/Makefile.build:284: /var/lib/dkms/veeamsnap/5.0.0.4318/build/blk_util.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/src/linux-headers-5.10.0-8-common/Makefile:1845: /var/lib/dkms/veeamsnap/5.0.0.4318/build] Error 2
make: *** [/usr/src/linux-headers-5.10.0-8-common/Makefile:185: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-5.10.0-8-amd64'
Request for clarification on snapshot files
Do the snapshot files store destroyed blocks when intercepting writes for a volume or do they store pending block writes that will be flushed after the snapshot is destroyed?
Centos 8 Stream "make" error
On my Centos8 Steam happens ...
[root@localhost source]# uname -rv
4.18.0-259.el8.x86_64 #1 SMP Mon Dec 21 21:05:36 UTC 2020
[root@localhost source]# make all
Making all...
ccflags-y= -O2 -Wno-multichar -DDISTRIB_NAME_CENTOS -DDISTRIB_VERSION_1=8
make -C /lib/modules/4.18.0-259.el8.x86_64/build M=/opt/veeamsnap/source modules
make[1]: ingresso nella directory "/usr/src/kernels/4.18.0-259.el8.x86_64"
...
/opt/veeamsnap/source/snapimage.c: In function ‘snapimage_create’:
/opt/veeamsnap/source/snapimage.c:816:24: error: implicit declaration of function ‘blk_alloc_queue’; did you mean ‘blk_alloc_queue_rh’? [-Werror=implicit-function-declaration]
image->queue = blk_alloc_queue(GFP_KERNEL);
^~~~~~~~~~~~~~~
blk_alloc_queue_rh
/opt/veeamsnap/source/snapimage.c:816:22: warning: assignment to ‘struct request_queue *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
image->queue = blk_alloc_queue(GFP_KERNEL);
^
/opt/veeamsnap/source/snapimage.c:833:9: error: implicit declaration of function ‘blk_queue_make_request’; did you mean ‘blk_mq_make_request’? [-Werror=implicit-function-declaration]
blk_queue_make_request( image->queue, _snapimage_make_request );
^~~~~~~~~~~~~~~~~~~~~~
blk_mq_make_request
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:316: /opt/veeamsnap/source/snapimage.o] Error 1
make[1]: *** [Makefile:1545: _module_/opt/veeamsnap/source] Error 2
make[1]: uscita dalla directory "/usr/src/kernels/4.18.0-259.el8.x86_64"
make: *** [Makefile:77: all] Error 2
Support for Linux 6.1
The driver cannot be compiled under Linux 6.1. There are several problems that do not make a solution as simple as expected.
Are there any plans to support current stable kernels?
Doesn't build with kernel 5.7.2
Dear maintainer:
This package doesn't build with kernels 5.7.2-zen1-1 and 5.7.2-arch1-1.
Please find the result message below:
==> dkms install veeamsnap/4.0.0.1961 -k 5.7.2-arch1-1
Error! Bad return status for module build on kernel: 5.7.2-arch1-1 (x86_64)
==> dkms install veeamsnap/4.0.0.1961 -k 5.7.2-zen1-1-zen
Error! Bad return status for module build on kernel: 5.7.2-zen1-1-zen (x86_64)
Additionally, attached is the /var/lib/dkms/veeamsnap/4.0.0.1961/build/make.log: make.log
I appreaciate your help or pointing me in the right direction to sort this out, and get the veeam agent running again.
kernel 4.18.0-305.19.1.el8_4.x86_64 issue
On CentOS 8.4 (veeamsnap built from master)
4.18.0-305.19.1.el8_4.x86_64 #1 SMP Wed Sep 15 15:39:39 UTC 2021
Failed to create volume snapshot
Failed to take volume snapshot
Failed to perform backup
Invalid argument
Failed to execute IOCTL_TRACKING_ADD
[75451.576541] veeamsnap:main ================================================================================
[75451.576777] veeamsnap:cbt_prst | WRN | Persistent CBT parameters are not set
[75451.577125] veeamsnap:main Loading
[75451.578677] veeamsnap:main Version: 5.0.0.4318
[75451.579229] veeamsnap:main Author: Veeam Software Group GmbH
[75451.579760] veeamsnap:main licence: GPL
[75451.580256] veeamsnap:main description: Veeam Snapshot Kernel Module
[75451.580815] veeamsnap:main zerosnapdata: 0
[75451.581357] veeamsnap:main debuglogging: 0
[75451.581898] veeamsnap:main snapstore_block_size_pow: 14
[75451.582704] veeamsnap:main change_tracking_block_size_pow: 18
[75451.583374] veeamsnap:main logdir: (null)
[75451.583940] veeamsnap:main logmaxsize: 15728640
[75451.584567] veeamsnap:main cbtdata: (null)
[75451.585135] veeamsnap:main fixflags: 0x0
[75451.585706] veeamsnap:main Compile for distributive: CentOS 8
[75451.586273] veeamsnap:ctrl_pipe Ctrl pipes initialization
[75451.586842] veeamsnap:main Registering reboot notification
[75451.587443] veeamsnap:main Module major [239]
[75451.587986] veeamsnap:snapimage Snapshot image block device major 252 was registered
[75451.588598] veeamsnap:ctrl_sysfs Create 'major' sysfs attribute
[75451.589158] veeamsnap:ctrl_sysfs Create 'blkdev_notify' sysfs attribute
[75514.231209] veeamsnap:ctrl_fops Collecting tracking devices:
[75514.232096] veeamsnap:tracking There are no devices under tracking
[75514.232547] veeamsnap:tracking Adding device [8:17] under tracking
[75514.232962] veeamsnap:tracker Create tracker for device [8:17]. Start 0x800 sector, capacity 0x2744b17df sectors
[75514.233384] veeamsnap:cbt_map CBT map create
[75514.233796] veeamsnap:cbt_map Allocate CBT map of 20587915
[75514.244558] veeamsnap:cbt_map New CBT generation ID: [7456c87b-ad8f-4269-9802-dcee4169472d]
[75514.326096] veeamsnap:tracker | ERR | Cannot make hook. make_request_fn is NULL
[75514.326118] veeamsnap:blk Device [8:17] was frozen
[75514.327497] veeamsnap:tracker | ERR | Failed to create tracker for device [8:17]
[75514.327501] veeamsnap:blk Device [8:17] was unfrozen
[75514.328903] veeamsnap:tracking | ERR | Failed to create tracker. errno=-22
[75514.328997] veeamsnap:blk Device [8:17] was frozen
[75514.330360] veeamsnap:blk Device [8:17] was unfrozen
Error in FC32 kernel 5.8.4
Veeam backup fails with:
Waiting for backup infrastructure resources availability 00:00:02
[error] Failed to create volume snapshot 00:00:01
[error] Failed to take volume snapshot
[error] Failed to perform backup
[error] Invalid argument
[error] Failed to execute IOCTL_TRACKING_ADD
[error] Processing finished with errors at 2020-09-08 17:46:15 GMT
dmesg:
veeamsnap:tracking Adding device [8:1] under tracking
Create tracker for device [8:1]. Start 0x800 sector, capacity 0x12c000 sectors
veeamsnap:cbt_map CBT map create
veeamsnap:cbt_map Allocate CBT map of 2400
veeamsnap:tracker | ERR | Cannot make hook. make_request_fn is NULL.
veeamsnap:tracker | ERR | Failed to create tracker for device [8:1]
veeamsnap:tracking | ERR | Failed to create tracker. errno=-22
veeamsnap:blk Device [8:1] was frozen
veeamsnap:blk Device [8:1] was unfrozen
veeamsnap:blk Device [8:1] was frozen
veeamsnap:blk Device [8:1] was unfrozen
Best regards,
Raul
Migration to organization
It is possible to migrate the personal account to organization?
Converting:
It is possible to rename this account and create the organization and move/transfer the repository to the organization.
Rename account:
Create an organization:
Transfer a repository:
Like:
Unable to load veeamsnap
Linux 4.18.0-240.10.1.el8_3.x86_64 #1 SMP Mon Jan 18 17:05:51 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
[ 1257.348113] veeamsnap: disagrees about version of symbol device_unregister
[ 1257.348143] veeamsnap: Unknown symbol device_unregister (err -22)
[ 1257.348230] veeamsnap: disagrees about version of symbol device_create
[ 1257.348248] veeamsnap: Unknown symbol device_create (err -22)
CentOS 8.3
kmod-veeamsnap.x86_64 4.0.1.2365-1.el8 @veeam
The veeamsnap project will be deprecated.
Veeam Agent for Linux 6.0 will contain blksnap. It is already available in VAL 6.0 TP and is recommended for lk 5.10 - 5.17.
On older kernels with a version up to 5.10, veeamsnap can still be used. Therefore, both modules will be used for a long time. But support for new kernel versions in the veeamsnap module is not expected.
Any feedback is welcome.
compilation aborts with 2.6.34 kernel
The module does not compile in the next distribution:
ubuntu 10.04
custom linux 2.6.34 kernel
make: Entering directory `/PACKAGES/XENOMAI/UBUNTU_LUCID/V2.4.10/V2.5.3/linux-2.6.34'
LD /var/lib/dkms/veeamsnap/3.0.0.865/build/built-in.o
CC [M] /var/lib/dkms/veeamsnap/3.0.0.865/build/log.o
CC [M] /var/lib/dkms/veeamsnap/3.0.0.865/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/3.0.0.865/build/sparse_bitmap.o
/var/lib/dkms/veeamsnap/3.0.0.865/build/sparse_bitmap.c: In function ‘log_tr_format’:
/var/lib/dkms/veeamsnap/3.0.0.865/build/log_format.h:1: sorry, unimplemented: function ‘log_tr_format’ can never be inlined because it uses variable argument lists
make[1]: *** [/var/lib/dkms/veeamsnap/3.0.0.865/build/sparse_bitmap.o] Error 1
make: *** [module/var/lib/dkms/veeamsnap/3.0.0.865/build] Error 2
Support for Linux Kernel 6.8
Hi
Is the next version of veeamsnap or in particular: Veeam Agent for Linux >6.1.0.1498 amd64 // veeam-release-deb/stable > 1.0.9 amd64 supporting Linux Kernel 6.8 already in work or planed? Maybe there is already a release date known?
best regards
santo
Syscall to `IOCTL_TRACKING_ADD` fails, raising `function not implemented`
This call runs fine on most of the distros we had tested on. Only ones with issues are Red Hat Enterprise Linux 8 (and others based on it, like CentOS 8, Oracle Linux 8), when running their latest kernel version - 4.18.0-348.7.1.el8_5.x86_64
This call is successful when running on older kernel versions, like the ones that come preinstalled with the OS ISOs (for releases up to 8.3)
Here is the exact call we're trying to run: https://github.com/cloudbase/coriolis-snapshot-agent/blob/main/internal/ioctl/ioctl.go#L175
Kernel versions that this successfully runs on:
- 4.18.0-147.el8.x86_64
- 4.18.0-193.el8.x86_64
- 4.18.0-240.el8.x86_64
Kernel versions that this call fails:
- 4.18.0-305
- 4.18.0-348.el8.x86_64
- 4.18.0-372.26.1.el8_6.x86_64
veeamsnap module is always built from source, master branch.
is there any tech spec for veeamsnap?
As a kernel module which need to install on the product env, I want to know how it works. is there any technical white paper? as a character device driver, how it intercept block I/O? how it sense the file name? thank you!
kernel 5.8 is supported in the experimental branch.
/build/snapstore_mem.c:76:23: error: too many arguments to function "__vmalloc"
buffer_el->buff = __vmalloc( SNAPSTORE_BLK_SIZE * SECTOR_SIZE, GFP_NOIO, PAGE_KERNEL );
There is documentation or examples ？
make install but unknow how to use to snap my disk /dev/sda
Linux 5.7.0-3: failed to compile
Same issue as Linux 5.6: failed to compile would be my guess
`Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.7.0-3-MANJARO -C /usr/lib/modules/5.7.0-3-MANJARO/build M=/var/lib/dkms/veeamsnap/4.0.0.1961/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.7.0-3-MANJARO (x86_64)
Error while configuring
Consult /var/lib/dkms/veeamsnap/4.0.0.1961/build/make.log for more information.
.
.
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Install DKMS modules
==> dkms install veeamsnap/4.0.0.1961 -k 5.6.15-1-MANJARO
==> dkms install veeamsnap/4.0.0.1961 -k 5.7.0-3-MANJARO
Error! Bad return status for module build on kernel: 5.7.0-3-MANJARO (x86_64)
Error while configuring
Consult /var/lib/dkms/veeamsnap/4.0.0.1961/build/make.log for more information.
==> Warning, dkms install veeamsnap/4.0.0.1961 -k 5.7.0-3-MANJARO' returned 10 Transaction successfully finished. [make.log](https://github.com/veeam/veeamsnap/files/4748123/make.log)
linux kernel 5.18 update possible?
I see that the supported kernels close at 5.16 rc6, but it doesn't hurt asking
Is there a chance that veaamsnap will be updated for 5.18?
If this kernel is going to be a default, OMV 6 debian would not be possible to make snapshot backups, rolling back kernel is not gonna solve it if I reinstall an OS or do another machine
5.16 worked perfectly with dkms build
dkms build exits with a missing file error:
DKMS make.log for veeamsnap-5.0.2.4567 for kernel 5.18.0-0.bpo.1-amd64 (x86_64)
Wed 22 Jun 12:06:04 CEST 2022
make: Entering directory '/usr/src/linux-headers-5.18.0-0.bpo.1-amd64'
CC [M] /var/lib/dkms/veeamsnap/5.0.2.4567/build/log.o
CC [M] /var/lib/dkms/veeamsnap/5.0.2.4567/build/mem_alloc.o
CC [M] /var/lib/dkms/veeamsnap/5.0.2.4567/build/sparse_bitmap.o
CC [M] /var/lib/dkms/veeamsnap/5.0.2.4567/build/container.o
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/log.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
77 | #include <linux/genhd.h> // For basic block driver framework
| ^~~~~~~~~~~~~~~
compilation terminated.
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/sparse_bitmap.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
77 | #include <linux/genhd.h> // For basic block driver framework
| ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/scripts/Makefile.build:293: /var/lib/dkms/veeamsnap/5.0.2.4567/build/log.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/scripts/Makefile.build:293: /var/lib/dkms/veeamsnap/5.0.2.4567/build/sparse_bitmap.o] Error 1
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/container.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
77 | #include <linux/genhd.h> // For basic block driver framework
| ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/scripts/Makefile.build:293: /var/lib/dkms/veeamsnap/5.0.2.4567/build/container.o] Error 1
In file included from /var/lib/dkms/veeamsnap/5.0.2.4567/build/mem_alloc.c:3:
/var/lib/dkms/veeamsnap/5.0.2.4567/build/stdafx.h:77:10: fatal error: linux/genhd.h: No such file or directory
77 | #include <linux/genhd.h> // For basic block driver framework
| ^~~~~~~~~~~~~~~
compilation terminated.
make[1]: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/scripts/Makefile.build:293: /var/lib/dkms/veeamsnap/5.0.2.4567/build/mem_alloc.o] Error 1
make: *** [/usr/src/linux-headers-5.18.0-0.bpo.1-common/Makefile:1858: /var/lib/dkms/veeamsnap/5.0.2.4567/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.18.0-0.bpo.1-amd64'
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.