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

IPFS Files root not avialable fix in 'ipfs repo fsck' #3934

Open
Kubuxu opened this issue May 20, 2017 · 3 comments · May be fixed by #4446
Open

IPFS Files root not avialable fix in 'ipfs repo fsck' #3934

Kubuxu opened this issue May 20, 2017 · 3 comments · May be fixed by #4446
Labels

Comments

@Kubuxu
Copy link
Member

Kubuxu commented May 20, 2017

Version information: 0.4.9

Type: Bug

Severity: High

Description:

I somehow managed to do this:

 ~  ipfs files rm -r /                                                                        ✘ 
Error: error loading filesroot from DAG: merkledag: not found
 ~  ipfs files stat /                                                                         ✘ 
Error: error loading filesroot from DAG: merkledag: not found
 ~  ipfs files rm /                                                                           ✘ 
Error: error loading filesroot from DAG: merkledag: not found

and this

 ipfs daemon       
Initializing daemon...
Adjusting current ulimit to 2048...
Successfully raised file descriptor limit to 2048.
^C
Received interrupt signal, shutting down...
(Hit ctrl-c again to force-shutdown the daemon.)
16:24:37.894 ERROR   cmd/ipfs: error from node construction: error loading filesroot from DAG: Failed to get block for QmP6wAYvriaFzQjWMb7CPJP6v8LvEuYRh32mEEn6b45WRK: context canceled daemon.go:337
Error: error loading filesroot from DAG: Failed to get block for QmP6wAYvriaFzQjWMb7CPJP6v8LvEuYRh32mEEn6b45WRK: context canceled

Having ipfs repo fsck check for this problem and fixing it under user confirmation (as it might lead to data loss as files root is best effort pinning would be nice).

@kevina kevina self-assigned this May 22, 2017
@kevina
Copy link
Contributor

kevina commented May 22, 2017

Should we prompt or output a warning and suggest the user rerun with a flag?

@whyrusleeping
Copy link
Member

I think asking the user to pass a special flag would be good.

@whyrusleeping whyrusleeping added the help wanted Seeking public contribution on this issue label Sep 2, 2017
kevina added a commit that referenced this issue Dec 1, 2017
Closes #3934.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>
@ghost ghost added the status/in-progress In progress label Dec 1, 2017
@kevina kevina removed the help wanted Seeking public contribution on this issue label Dec 1, 2017
@kevina
Copy link
Contributor

kevina commented Dec 1, 2017

#4446 will you allow you to remove the root. I did it a separate command as removing it (even if the hash no longer exists) could lead to data loss. The assumption is that someone who uses this command knows what they are doing.

kevina added a commit that referenced this issue May 30, 2018
Closes #3934.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>
kevina added a commit that referenced this issue May 30, 2018
Closes #3934.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>
kevina added a commit that referenced this issue Jun 4, 2018
Closes #3934.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>
Stebalien pushed a commit that referenced this issue Mar 2, 2019
Closes #3934.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>
Stebalien pushed a commit that referenced this issue Mar 2, 2019
Closes #3934.

License: MIT
Signed-off-by: Kevin Atkinson <k@kevina.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants