Skip to content

Restart the lotus market subsystem will mess up the raw data  #7577

Description

@Araquiel

Edited by @jennijuju

Restart the lotus market subsystem will mess up the raw data that has been transferred, which will create a mismatch in commP and leads to publishing, precommiting and provecommiting to fail.


Checklist

  • This is not a security-related bug/issue. If it is, please follow please follow the security policy.
  • This is not a question or a support request. If you have any lotus related questions, please ask in the lotus forum.
  • This is not a new feature request. If it is, please file a feature request instead.
  • This is not an enhancement request. If it is, please file a improvement suggestion instead.
  • I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
  • I am running the Latest release, or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
  • I did not make any code changes to lotus.

Lotus component

  • lotus daemon - chain sync
  • lotus miner - mining and block production
  • lotus miner/worker - sealing
  • lotus miner - proving(WindowPoSt)
  • lotus miner/market - storage deal
  • lotus miner/market - retrieval deal
  • lotus miner/market - data transfer
  • lotus client
  • lotus JSON-RPC API
  • lotus message management (mpool)
  • Other

Lotus Version

miner/worker 1.13.0

Describe the Bug

after ever restart the lotus-miner have a problem with sealing deals in sectors
got unexpected deal CID
all data-transfers close and disable deals before resart.
happaned every restart.

Logging Information

0.      2021-10-28 11:05:31 +0500 +05:  [event;sealing.SectorStart]     {"User":{"ID":1101,"SectorType":8}}
1.      2021-10-28 11:05:31 +0500 +05:  [event;sealing.SectorAddPiece]  {"User":{}}
2.      2021-10-28 11:06:04 +0500 +05:  [event;sealing.SectorAddPiece]  {"User":{}}
3.      2021-10-28 11:06:04 +0500 +05:  [event;sealing.SectorAddPiece]  {"User":{}}
4.      2021-10-28 11:06:04 +0500 +05:  [event;sealing.SectorAddPieceFailed]    {"User":{}}
        got unexpected piece CID: expected:baga6ea4seaqcq7npercyqcob2d3efqzxfhcyrxeabirli7xjwwphpxeoobqamcq, got:baga6ea4seaqnqyicdbbfvnpjlmokmi45fgroiigxa2uw6nz6f6ojveoxlhizwai
5.      2021-10-28 11:06:04 +0500 +05:  [event;sealing.SectorRetryWaitDeals]    {"User":{}}
6.      2021-10-28 12:33:51 +0500 +05:  [event;sealing.SectorAddPiece]  {"User":{}}
7.      2021-10-28 12:38:48 +0500 +05:  [event;sealing.SectorAddPiece]  {"User":{}}
8.      2021-10-28 12:38:48 +0500 +05:  [event;sealing.SectorAddPieceFailed]    {"User":{}}
        got unexpected piece CID: expected:baga6ea4seaqc44hh3zdirdxjavtmt7plfkuxg6pa23op3yafoooblfayi33fokq, got:baga6ea4seaqg2nsld34emra2ljfgrbrdcswmbjdpaftrpzjuipudt3w7qpbikpa
9.      2021-10-28 12:38:48 +0500 +05:  [event;sealing.SectorRetryWaitDeals]    {"User":{}}
10.     2021-10-28 12:38:48 +0500 +05:  [event;sealing.SectorAddPiece]  {"User":{}}
11.     2021-10-28 12:40:16 +0500 +05:  [event;sealing.SectorAddPieceFailed]    {"User":{}}
        got unexpected piece CID: expected:baga6ea4seaqihialc3c42ydcbqkxau25gmbv4olkwafhv3m7x3fbyo7rr343cba, got:baga6ea4seaqg2nsld34emra2ljfgrbrdcswmbjdpaftrpzjuipudt3w7qpbikpa
12.     2021-10-28 12:40:16 +0500 +05:  [event;sealing.SectorRetryWaitDeals]    {"User":{}}

Repo Steps

  1. take a deal and wait to publish
  2. wait when lotus create sector
  3. deal can't work and sectors going to state "wait deals" when have a lot of deals in system

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions