-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mine is taking removed/faulty/inactive sectors for computing winning post proof #4027
Comments
Seems like it is also picking up terminated sectors, which is unexpected from our discussion(we said that if we add termination option to remove, then this should be resolved naturally). For example, miner f010399 has removed a lot of sectors due to
However,
For a smaller miner that has a lot of removed sectors, this is effect their block winning chance severely. The miner mentioned that almost everyday, such a sector will be picked for winning post.
|
my miner Computing WinningPoSt selected these removed sectors everyday,please help me! thanks! |
Low effort, but maybe needs a FIP. |
Team decided no FIP required |
Closed by #4770 |
lotus version This problem not resolved on v1.2.0, 2020-11-20T05:48:28.696+0800 INFO storageminer storage/miner.go:249 Computing WinningPoSt ;[{SealProof:3 SectorNumber:476 SealedCID:bagboea4b5abcbyfnohy5ezjqb7khrqnjzgzoj3elpzn4gbxwq4q3oczgr2cx5hbb}]; [181 49 175 84 243 229 101 58 59 234 54 117 230 117 218 132 253 206 12 132 148 234 46 246 5 149 162 145 107 217 73 248] SectorID: 476 |
Seems like since our
sector remove
is not declaring the sector has been removed on chain(partially related #3841), mine is still picking those sectors up for computing winning post proof which triggers the following errorThe text was updated successfully, but these errors were encountered: