-
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
[BUG] Piece Cid mismatch between deal proposal in Actor state and deal Piece added to Sector (online and offline deals) #7103
Comments
cc @jennijuju @jacobheun for tracking. @stuberman to fill out details. |
Some details: These are two deals that were received from Estuary (see Logging info above) |
Seeing this occur in the next batch of Estuary deals: 2021-08-17T12:09:42.881Z WARN sectors storage-sealing/states_sealing.go:194 invalid deals in sector 1508: piece 0 (of 7) of sector 1508 refers deal 2287254 with wrong PieceCID: baga6ea4seaqdsvqopmj2soyhujb72jza76t4wpq5fzifvm3ctz47iyytkewnubq != baga6ea4seaqdtuc2eyr47qcoj5yti5sn6vvns3tjmne647b3brxz3po7gutikka lotus-miner sectors status 1508 lotus-miner storage-deals list -v | grep 228725 Aug 16 23:12:51 true bafyreiemgm7jr3tx76utrng6ngwmaiasn5quqoud5vdy7k3q34weulllvm 2287254 StorageDealAwaitingPreCommit f3vnq2cmwig3qjisnx5hobxvsd4drn4f54xfxnv4tciw6vnjdsf5xipgafreprh5riwmgtcirpcdmi3urbg36a 512MiB 0 FIL 1494720 12D3KooWGBWx9gyUFTVQcKMTenQMSyE2ad9m7c9fpjS4NMjoDien-12D3KooWSsaFCtzDJUEhLQYDdwoFtdCMqqfk562UMvccFz12kYxU-1629155331192764681 Aug 17 02:50:53 true bafyreih5ybnawjvcrnt64ybh5srnbqn3kvx6f6gzha2gqiz57fhhaa54zq 2287256 StorageDealAwaitingPreCommit f3vnq2cmwig3qjisnx5hobxvsd4drn4f54xfxnv4tciw6vnjdsf5xipgafreprh5riwmgtcirpcdmi3urbg36a 4GiB 0 FIL 1494720 12D3KooWGBWx9gyUFTVQcKMTenQMSyE2ad9m7c9fpjS4NMjoDien-12D3KooWSsaFCtzDJUEhLQYDdwoFtdCMqqfk562UMvccFz12kYxU-1629155331192765192 Aug 17 02:51:36 true bafyreigf3awkkoo3hpsrgefnokx2ru56gqfv6h4j4g3f7jkqfb6egtqplu 2287255 StorageDealAwaitingPreCommit f3vnq2cmwig3qjisnx5hobxvsd4drn4f54xfxnv4tciw6vnjdsf5xipgafreprh5riwmgtcirpcdmi3urbg36a 512MiB 0 FIL 1494720 12D3KooWGBWx9gyUFTVQcKMTenQMSyE2ad9m7c9fpjS4NMjoDien-12D3KooWSsaFCtzDJUEhLQYDdwoFtdCMqqfk562UMvccFz12kYxU-1629155331192765197 |
Logs from f01278 markets and miner machines as requested |
@stuberman So you've now seen this problem with two separate batches of Estuary deals, right ? |
Yes, two of the most recent batches. A third batch just was published
|
@stuberman could you please use the |
I'm seeing this too on f019551. |
7 sectors and 63 deals stuck with RecoverDealIDs on f019551 (1.11.1-m1.3.5+mainnet+git.7be207bc5.dirty+api1.2.0). |
@raulk @jacobheun Looks like @magik6k has a fix for this in #7117. |
|
I am also seeing this on a single 32GiB deal from bidbot: 2021-08-20T00:33:37.689Z WARN sectors storage-sealing/states_failed.go:357 piece 0 (of 1) of sector 1522 refers deal 2303929 with wrong PieceCID: baga6ea4seaqp4q7ndvzeivdj3ouwa4lcgonnag4pols7m3y435c7ycnd22fucja != baga6ea4seaqdgp7rok7tz3quk44xqbyogq5bqil5ibtfbghusxo5qe57f5fuqbi |
Seeing these from another Slingshot participant as well tonight - using split market on dedicated machine
2021-08-23T02:48:47.069Z WARN sectors storage-sealing/states_sealing.go:201 invalid deals in sector 1536: piece 1 (of 4) of sector 1536 refers deal 2321237 with wrong PieceCID: baga6ea4seaqnqyicdbbfvnpjlmokmi45fgroiigxa2uw6nz6f6ojveoxlhizwai != baga6ea4seaqa62vdf2yo26kbrrhcvsy5hyddw66q2adaeokfquflsbu3rhgr6li |
f01278 Logs - market is too big to upload to GitHub |
Talked to @stuberman off band and he hasn't seen this after upgrading Markets to v1.11.2-rc1 which contains some fixes we made to the piece handover flow to Lotus. No other miners too reporting this after the upgrade. Closing this issue. |
Checklist
Lotus component
lotus miner/worker - sealing
Lotus Tag and Version
Describe the Bug
@stuberman reported an issue where the deal Piece CID stored in the Actor subsystem does not match the PieceCID of the same deal as known by the Sector being sealed.
Logging Information
Repo Steps
...
The text was updated successfully, but these errors were encountered: