-
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
feat: sealing: storage redeclare/detach #9032
Conversation
Codecov Report
@@ Coverage Diff @@
## master #9032 +/- ##
==========================================
- Coverage 40.73% 40.61% -0.13%
==========================================
Files 707 707
Lines 78875 79093 +218
==========================================
- Hits 32132 32120 -12
- Misses 41265 41478 +213
- Partials 5478 5495 +17
|
6990226
to
459c5f0
Compare
Tests need fixing, likely due to changes in itests ensemble: import presealed sector metadata - a bunch of itests are likely calling Easiest fix for those is likely adding a helper method |
Been testing this PR, and after fixing the typo in
Before move:
Moving sectors:
Redeclare & check sectors find:
Before detaching
Detaching and checking paths:
Before move
Moving files:
Redeclare and check paths:
I moved all the files and redeclaring+drop-missing on the |
Okay, so one strange thing happened during my testing of the I first detached the
But when I check the
So repro steps to get some errors (This is also mostly caused when mixing attaching a path on both
|
459c5f0
to
1ee82dd
Compare
65292dc
to
82f9221
Compare
82f9221
to
8294e03
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two quickly fixed comments.
If @rjan90 can confirm the fix you made, this should be good to go.
Dropped the args check in the redeclare command as it doesn't use those args. |
I re-ran the detach shared paths issue, and where able to successfully detach the storage on both worker and miner now 👍 So I can confirm that it´s fixed. |
@magik6k conflicts on docs - then merge? we want this in v1.17.1!! |
This issue has not been resolved yet Many nodes are stuck in the "New sector" log line When I modify storage.json and change the Path to a new value (/mnt/lotus/mainData/), this Path is executed by re executing the lotus miner storage attach -- init -- store/mnt/lotus/mainData/, which can be started successfully Next, I execute the lotus miner attach/mnt/netdisk/mainData command. The program is stuck, and the path/mnt/netdisk/mainData is the old value. "I have to start using 1.17.0 first. If it succeeds, it must be started using 1.17.0. If it is 1.17.2, the program still cannot be started." |
Related Issues
Based on #9013
Closes #9019
Closes #3716
Proposed Changes
storage detach/redeclare
commands to lotus-miner/lotus-workerlotus-miner storage detach
lotus-miner storage redeclare
Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, INTERFACE BREAKING CHANGE, CONSENSUS BREAKING, build, chore, ci, docs,perf, refactor, revert, style, testarea
: api, chain, state, vm, data transfer, market, mempool, message, block production, multisig, networking, paychan, proving, sealing, wallet, deps