fedora 29 kernel 4.20.5-200.fc29.x86_64 veeamsnap-3.0.0.865

[erpguy]

first backup test successful

--- usr/src/veeamsnap-3.0.0.865/log.c 2018-12-21 18:40:59.000000000 -0500
+++ /usr/src/veeamsnap-3.0.0.865/log.c 2019-02-05 20:30:24.505806585 -0500
@@ -177,7 +177,7 @@
{
struct tm modify_time;
getnstimeofday( &logging->m_modify_time );
- time_to_tm( logging->m_modify_time.tv_sec, 0, &modify_time );
+ time64_to_tm( logging->m_modify_time.tv_sec, 0, &modify_time );

snprintf( filepath, filepath_size, "%s/%s-%04ld%02d%02d.log",
logging->m_logdir,
@@ -225,8 +225,8 @@
log_tr_lld( "Log file size: ", sz );

getnstimeofday( &_time );
- time_to_tm( _time.tv_sec, 0, &current_time );
- time_to_tm( logging->m_modify_time.tv_sec, 0, &modify_time );
+ time64_to_tm( _time.tv_sec, 0, &current_time );
+ time64_to_tm( logging->m_modify_time.tv_sec, 0, &modify_time );

if (
(modify_time.tm_mday == current_time.tm_mday) &&
@@ -327,7 +327,7 @@

struct tm _time;
char timebuff[256];
- time_to_tm( rq->m_time.tv_sec, 0, &_time );
+ time64_to_tm( rq->m_time.tv_sec, 0, &_time );

_log_prefix( timebuff, sizeof( timebuff ), &_time, rq, _log_level_to_text( rq->m_level ) );

[PTide]

Hi,

Would elaborate please? Is that what you got on your console output?

Thanks!

[erpguy]

this is the patch to make it work with distribution / kernel specified

[PTide]

We've been working for 4.20 support for a while, it would be interesting to compare both solutions : ) Thank you for sharing that

Cheers!

P.S. BTW, there is a 'veeamsnap' project on github

[cloggy]

this is the patch to make it work with distribution / kernel specified

Where is that patch? I'd like to get VAL working too with the 4.20.5-200.fc29.x86_64 kernel....

TIA

[cloggy]

No need for it anymore...got VAL working on Manjaro with kernel 4.20.11-1.

[CatSpirent]

Just wondering if a patch still exists?
I have kernel 4.20.13-200.fc29.x86_64 and any attempt to backup gives me a snapshot error.
I deleted everything, but if you need logs I can certainly reinstall.

[PTide]

Caterine,

You might want to try this fork. Please keep in mind that Veeam cannot provide support on forks.

Thanks

[sdet00]

Does anyone know if 5.0 support is around the corner? I happen to be running the latest kernel at the moment but looks like I'll need to downgrade for the meantime.

[nielsengelen]

Currently no ETA on support for 5.0 however we'll look into it to support it as soon as possible.

[sdet00]

No trouble. 4.15 is working fine, just not as great as 5.0+ for AMD graphics on mobile devices at the moment. I'll survive. Thanks for your work.