Kernel 5.4.1 unsupported?

[marcwa19197]

Hello,

i recently upgraded my non-production system running with ubuntu 16.04.5 to the latest stable Kernel version 5.4.1. Im using the latest Veeam-Release 3.0.2.1185.

Unfortanly im not able to activate the veeamsnap kernel-module via DKMS.

I also tried to compile it manually using "dkms build -m veeamsnap -v 3.0.2.1185", but im getting an error.
Is there maybe an patch available for using Veeam Agent for Linux with Kernel 5.4.1? This can also be an experimental patch.

Do you need more information?

Thank you and best regards

[PTide]

Hi,

What error do you get?

As to experimental patch, you might try this one. Although it says 5.2, it might actually work on 5.4 as well.

If that still does not work, you will need to wait for the upcoming (soon) release of the next version that will support 5.4

Thanks!

[marcwa19197]

Running dkms build -m veeamsnap -v 3.0.2.1185:
make KERNELRELEASE=5.4.1-050401-generic -C /lib/modules/5.4.1-050401-generic/build M=/var/lib/dkms/veeamsnap/3.0.2.1185/build....(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.4.1-050401-generic (x86_64)
Consult /var/lib/dkms/veeamsnap/3.0.2.1185/build/make.log for more information.

make.log is available here: https://pastebin.com/MeNziuZq

Thank you for the fast reply. I will try this patch tomorrow.

[marcwa19197]

i tried it but without success. Any other idea? Or do you know when the new release is coming?

[PTide]

There is no exact date, but the new version of VAL is anticipated in the beginning of 2020.

Thanks!

[marcwa19197]

Okay and the next release will fully support Kernel 5.4.1?

[PTide]

Okay and the next release will fully support Kernel 5.4.1?

@marcwa19197 ,

There is a good chance that it will, however I can't say for sure right now. So far it works fine on 5.3, and developers have been reporting that after introduction of mq-bio in 5.0 kernel things got way more stable.

Would you tell me you gcc version please?

UPDATE: It has been reported by the main developer of the module that the version from github can be built on Ubuntu 19.04 with 5.4 kernel using gcc 8.3. That is, they suspect that the issue might be related to the gcc vrsion that you are using.

Thanks!

[marcwa19197]

Hi,

thank you for the support!
Im running gcc (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609.

so you mean compiling https://github.com/veeam/veeamsnap with gcc 8.3 will work well?

Thank you and best regards

[PTide]

It can be compiled with gcc 8.3, and should work fine on a basic level, however we haven't finished all the tests yet. That is, at this point I cannot promise anything. Should you choose to try experimenting with it, any feedback will be very appreciated.

Thanks!

[marcwa19197]

Hi,
as long as it does not crash my server, i will give it a try!

Will report here later this day!
Thank you

[marcwa19197]

Seems to work! Backup is running again without errors! (till now

I installed gcc-8 and compiled the GitHub source via make CC=gcc-8 all after that an make CC=gcc-8 load will load the compiled kernel module.

[marcwa19197]

Okay, i got so far, but since 19 hours nothing was backed up, progress bar still is at 0% and nothing else is displayed:
https://i.ibb.co/D5D73mH/Greenshot-2019 ... -50-21.png

Any idea what to do?

[PTide]

I PMed you a script that will gather some info from your system, please run it (check the second example of usage in the header) during the job run. It will produce .txt file.

Also please run veeamjobman Snap --print_state. This one will save veeamsnap state info in dmesg, and also will send output to veeamjobman.log

Kindly collect all three files, and send them over.

Thanks!

[marcwa19197]

Hi,

thank you for the support!
I think the backup is running now, but really slowly. (Slower than ever before.)

https://i.ibb.co/C7L3kZ7/veeam.png

[marcwa19197]

The Backup Job is running for 90 hours, which exceeded every time needed for backups before....
I executed your scripts and commands and shared the output via PM.

Please reply me, if you found something.
In the meantime i will just let it run, maybe it will finish before Christmas
After that i will do a full system-reboot, maybe this solves the low speed.

Thank you very much!!

[marcwa19197]

I did a system reboot, but this was not helpful :/ any other ideas?

[PTide]

No, not really.

P.S. I shot you a PM

[marcwa19197]

Hi,

Backup is still running..
Its now at 98% but its suddenly really really slow (930 KB/s).

One additional note:
Because of an other problem i had in the past (im not sure if this is maybe fixed with the recent version im using) i have the following veeam.ini settings active / modified:

[snapshot]
# Free percent of storage. Used for calculate optimal snapshot data size and determinate snapshot data location, not for stretch snapshot
freepercent= 99

# Maximum possible snapshot data size, not for stretch snapshot
maxsize= 211280723968

# Minimal possible snapshot data size, not for stretch snapshot
minsize= 211280723968

# Snapshot data type, can be 'stretch' (default) or 'common'
type= common

# Used percent of storage. Used for calculate optimal snapshot data size and determinate snapshot data location, not for stretch snapshot
usedpercent= 99


[stretchsnapshot]
# Stretch snapshot data portion
portionsize= 8589934592

# Free percent of storage. Used for determinate snapshot data location. Only for stretch snapshot
storagefreepercent= 50


i wish you an happy new year! And again, thanks for your support!