Files remain in `.stversions` past max age

So I googled it and found a recent similar complaint on Reddit: https://www.reddit.com/r/Syncthing/comments/w0ctkx/files_remain_in_stversions_past_max_age/ but of course on reddit the details are a little lacking.

Only one of my systems seems to be experiencing the problem, it’s running v1.19.0, Linux (32-bit Intel/AMD) and yes, I’ll probably be upgrading to the current release a little later…

I have two directories ‘sharing’ the same .stversions directory but using different versioning parameters. Could this be the source of my problem? My other systems seem [I think, can’t see all 7 right now] to be using the same versioning parameters on the two folders.

Dir1:
        <versioning type="staggered">
            <param key="cleanInterval" val="3600"></param>
            <param key="maxAge" val="604800"></param>
            <cleanupIntervalS>90000</cleanupIntervalS>
            <fsPath>/home/myhome/.stversions</fsPath>
            <fsType>basic</fsType>
        </versioning>
Dir2:
        <versioning type="simple">
            <param key="cleanoutDays" val="6"></param>
            <param key="keep" val="2"></param>
            <cleanupIntervalS>9000</cleanupIntervalS>
            <fsPath>/home/myhome/.stversions</fsPath>
            <fsType>basic</fsType>
        </versioning>

The versioning configuration is setup separately on each folder, so my leap to conclusion was that they didn’t need to be the same. Or is there a limited compatibility issue caused by my using a common .stversion directory?

regards,

/dave

1 post - 1 participant

Read full topic