RE: re-enabling wcc / inaccurate wcc data

[Marcin Gondek <drixter%e-utp.net@localhost>]

Hi,

Probably it is, any chance to make it optional into code?
Should I submit the bug?

Thanks,


--
Marcin Gondek / Drixter
http://fido.e-utp.net/
AS56662

-----Original Message-----
From: netbsd-users-owner%NetBSD.org@localhost <netbsd-users-owner%NetBSD.org@localhost> On Behalf Of Michael van Elst
Sent: Saturday, April 26, 2025 9:56 AM
To: netbsd-users%netbsd.org@localhost
Subject: Re: re-enabling wcc / inaccurate wcc data 

drixter%e-utp.net@localhost (Marcin Gondek) writes:

>Hi All,

>Is there any chance to disable such errors in dmesg without changing 
>the co= de?

>[ 921603.144137] diskstation6.e-utp.net:/volume1/homes/drixter: 
>re-enabling=  wcc [ 921603.234137] 
>diskstation6.e-utp.net:/volume1/homes/drixter: inaccurate = wcc data 
>(ctime) detected, disabling wcc (ctime 1745490611.495561103 174549= 
>0611.495561103, mtime 1745490611.495561103 1745490611.495561103)


The message is a hard printf(), you have to change the code to avoid it.

The problem comes from not using accurate timestamps on the server. I don't think it happens when you export an ext4 filesystem and btrfs got a fix last year. Of course your Synology firmware might be older.