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

Error while adding multiple files in the IPFS cluster based private network #1937

Closed
tkb2501 opened this issue Jun 12, 2023 · 1 comment
Closed
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@tkb2501
Copy link

tkb2501 commented Jun 12, 2023

Hi team,

I have setup a private IPFS cluster based network for decentralized files storage, and I'm using IPFS-Cluster-http client for adding files into the network. I have a setup of 3 cluster nodes and correspondingly 1 IPFS node against each of the Cluster node.

Now while adding multiple files using the /add API I'm getting the output of the stream data with multiple CIDs, but while I'm searching for those CIDs in my cluster node using:

ipfs-cluster-ctl pin ls | grep "[CID]"

I'm not able to fetch the details corresponding to passed CID, but while fetching the file using get API call by passing the given CID
I'm able to retrieve the file.

And, while I'm trying to pin the CID manually by using:

ipfs-cluster-ctl pin add [CID]

then I'm getting this error:

/data/ipfs/datastore/368613.log: no space left on device

Even I have checked for the disk space and it is not full, can someone please help me with the issue?

@tkb2501 tkb2501 added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Jun 12, 2023
@hsanjuan
Copy link
Collaborator

Even I have checked for the disk space and it is not full

The disk on which that file sits is full. Closing in favour of #1946

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

2 participants