![]() In my opinion, there should be one entry there “scan: on/off” and a way to manually (UI) triggering that rescan. It is just kicking the can toward the end-user to avoid coding a more flexible solution. When you (I mean, chia code - program) load those folders, you know what speed you are going with, so that refresh should be dynamic, based on the folder/plots count and loading times. So, setting it to that 30-60 minutes is really not that big of a deal.Īlso, I don’t understand why that section is so rigid, or is there in the first place. Otherwise, I think you may even disable it, if there is such possibility (on startup, that harvester will rescan your folders, whether you have that timeout or not - at least i think so). If you are still adding new plots, maybe it is better to wait that 30-60 minutes to pick those plots up, than have the software start barfing again.īy the way, that rescan is needed only when you are adding new plots to the harvesters. So, add that section, make that entry be like 30-60 minutes or so, and see whether it helps. It looks like it is still under development, i.e., there is no clear understanding how to handle a big amount of folders/plots, as such you may be affected by that bug.Īnd as that link indicates, that change was added in v1.2.5, so exactly when you started having those problems - new, badly tested code. Here is the link that talks about those new entries. How many drives you have sitting on that harvester? ![]() If you have a lot of folders/plots (don’t know what “a lot” means), it may be that the scanning process is just too slow, and the code is starting to chase its own tail (e.g., getting new data, when the old is not being processed, and then being confused about missing that new data, …). You may want to disable/enable one folder, and check whether log file will have some interesting info.Īlthough, there may be one more possibility. I don’t see that “being scanned” lines there anymore (maybe after updating to v1.2.6), and have not added new plots recently. Since for you (or me) that section is not in config file, it is hard to guess what to do, unless you are pointed to it.įrom what you described, you are hitting either some OS limit, or Chia code is confused with that number of folders, and goes bonkers.īy the way, it used to be that when that timeout happened, there were INFO entries in the log file about which folders are being scanned, and plots added. Looks like you have a big load on your harvester, so they recommend to increase (by a lot, e.g., 10x) that “interval_seconds” field. With that new change, during the update, they don’t read the value you may have in your config file, but use a new section (that is not inserted in the old config.files): plots_refresh_parameter Plot_loading_frequency_seconds: 120 // 120 seconds In the old (pre v1.2.6 or 1.2.7) rescan timeout was controlled by I just installed 1.2.7 and crossed my fingers. I did not have this issue, when running version 1.1.7īut I eventually jumped to version 1.2.5 and that is when the false positives began. But when I have config.yaml set to farm all of my drives, then Chia rejects over 1,000 plots.ĭoes the Chia program track what it had once identified as a duplicate, and retains that finding, even when there is no longer a duplicate filename? If so, how do I tell Chia to reset its findings? However, if I set-up config.yaml to farm only one of those drives at a time, then all of the plots get loaded. Each of the 8 drives has a mix of valid plots and supposedly duplicate plots. Please also note that the so-called duplicates are all located on 8 of my USB drives. ![]() It found no duplicates.Īnd there is no way that anyone could possibly duplicate over 1,000 files, and not know that they did so. I also run NirSoft’s “SearchMyFiles.exe”, as it has a feature specific for identifying duplicate filenames. I have manually searched, everywhere, for several of the supposedly duplicate filenames. The above repeats over 1,000 times (for different plots), and would seem to be the reason for Chia under-reporting my plot count. T09:09:48.051 harvester : WARNING Have multiple copies of the plot (and the rest of the line simply spells out the name of the plot and its location) The debug log contains over 1,000 lines that read: ![]() The GUI, and the “chia farm summary” command are under-reporting my plot count, by over 1,000 plots.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |