As the title suggests - is this an ERROR I should ignore or investigate further?

So the 8TB and 16TB finally finished meaning whatever it is I did to kickstart it (I’ll explain at bottom) worked. The 8TB used space graph matches the OS reported usage. The issue remains with the 16TB: [image] The filewalkers seem done successfully but there is still a large discrepancy: [im…

I checked my logs, but there is no error messages for my DB - or do you mean to go through the steps anyways on my DB?

[image] Alexey: Yes, it’s a known issue: Okay got it, I’ll let lazy finish to see if it fixes things (probably will) and the leave lazy off for future runs

I would suggest to do the reverse. To fix the issue with a discrepancy I would suggest to disable a lazy mode, set allocation below the usage and enable scan on startup. When the stat on the dashboard would be updated (you shouldn’t see a 100% disk activity - unfortunately without log messages I wou…

So after two days of it not finishing I dug in the logs and realised I missed errors. Everytime it tries to start I see the following: 2024-06-18T08:06:18-04:00 INFO lazyfilewalker.used-space-filewalker subprocess exited with status {"satelliteID": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tG…

Not sure what I’m doing wrong: [image] And trying to run it manually I get: [image] P.S. While doing this, I realised that none of my DB’s are actually on my SSD, and instead are on the same drive as the node data. So now I want to move them out… but can’t find a good windows guide on it? @Al…

[image] thelastspark: but can’t find a good windows guide on it? [image] Storagenode: allow configuring database path independently (v1.4.2 and above only) FAQ Hello, So from the 1.4.2 Changelog we can at least move the database to an SSD ! Sound great but the docu…

Thanks for that, the DB’s got moved, everything is running smoothly. HOWEVER - my 2 big nodes still cannot start the filewalker (so that remains unchanged) (error pasted above). Checking the DB’s individually all seem ok - but I didn’t do all of them as that’s crazy tedious

[image] thelastspark: my 2 big nodes still cannot start the filewalker context canceled usually denotes slower disks. Can you confirm if the disks are not SMR ? You could check their model number.

Maybe a smarter person can double-check for me please? 20TB: ST16000NM001G-2KK103 (I’m 99% sure it’s cmr) 8TB: ST8000VN004-2M2101 (Not 100% sure which one it is) @nerdatwork

[image] thelastspark: ST16000NM001G [image] I am not sure about this as all Exos drives are CMR. You can check the list here [image] thelastspark: ST8000VN004 [image] As per the above list Ironwolf series is CMR too

ERROR filewalker failed to get progress from database

Node Operators troubleshooting

nerdatwork June 18, 2024, 1:00pm 11