Skip to content
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

[storagenode] Check whether we can drop support for v0 pieces #5781

Open
profclems opened this issue Apr 12, 2023 · 3 comments
Open

[storagenode] Check whether we can drop support for v0 pieces #5781

profclems opened this issue Apr 12, 2023 · 3 comments
Assignees
Labels
Enhancement New feature or request Needs Estimation Issue still needs story pointing Needs investigation The issue needs investigation to know what's the problem and the solution

Comments

@profclems
Copy link
Member

Currently we still have to deal with V0pieces. We only know they still exist because of a node a month or so ago that hit a bug dealing with a filesystem error on a v0 piece. It would be really nice to get rid of all the code. We don't have any metrics to track v0 pieces in the network.

We should figure out a way or maybe write something into Filewalker to check whether we can drop v0 support

@profclems profclems added Enhancement New feature or request Needs investigation The issue needs investigation to know what's the problem and the solution labels Apr 12, 2023
@revyte
Copy link

revyte commented Apr 14, 2023

Is this the topic you are referring to? https://forum.storj.io/t/your-node-is-disqualified-from-us-satellite-why-is-that-for/21539/13
If yes, it could be out of context, but it's also good to make sure they are or are not longer in existence.

I've seen a similar warnings in my log but, at least in my case, this should be another thing.

2023-04-13T18:47:32.156+0200	INFO	piecedeleter	delete piece sent to trash	{"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Piece ID": "WTFFJWB6KJVDFREF432YFOZCJ3VFDXTTQOQWO2GUIGH2U7K3LSOQ"}
2023-04-13T18:47:32.156+0200	WARN	pieces	failed to migrate v0 piece. Piece may not be recoverable
2023-04-13T18:47:32.156+0200	ERROR	piecedeleter	could not send delete piece to trash	{"Satellite ID": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", "Piece ID": "WTFFJWB6KJVDFREF432YFOZCJ3VFDXTTQOQWO2GUIGH2U7K3LSOQ", "error": "pieces error: filestore error: file does not exist", "errorVerbose": "pieces error: filestore error: file does not exist\n\tstorj.io/storj/storage/filestore.(*blobStore).Stat:105\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).pieceSizes:245\n\tstorj.io/storj/storagenode/pieces.(*BlobsUsageCache).Trash:290\n\tstorj.io/storj/storagenode/pieces.(*Store).Trash:388\n\tstorj.io/storj/storagenode/pieces.(*Deleter).deleteOrTrash:185\n\tstorj.io/storj/storagenode/pieces.(*Deleter).work:135\n\tstorj.io/storj/storagenode/pieces.(*Deleter).Run.func1:72\n\tgolang.org/x/sync/errgroup.(*Group).Go.func1:75"}

@profclems
Copy link
Member Author

This is really helpful @revyte!

@storjrobot
Copy link

This issue has been mentioned on Storj Community Forum (official). There might be relevant details there:

https://forum.storj.io/t/piecedeleter-could-not-send-delete-piece-to-trash-error-pieces-error-v0pieceinfodb-sql-no-rows-in-result-set/15708/15

@profclems profclems self-assigned this Apr 25, 2023
@iglesiasbrandon iglesiasbrandon added the Needs Estimation Issue still needs story pointing label Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Needs Estimation Issue still needs story pointing Needs investigation The issue needs investigation to know what's the problem and the solution
Projects
Status: Backlog
Development

No branches or pull requests

4 participants