question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error "No space left on device" observed while running warp run I/O

See original GitHub issue

Environment info

Noobaa version

[root@hpo-app1 ~]# noobaa version
INFO[0000] CLI version: 5.11.0
INFO[0000] noobaa-image: noobaa/noobaa-core:5.10.0-20220120
INFO[0000] operator-image: noobaa/noobaa-operator:5.11.0

OC version

[root@hpo-app1 ~]# oc version
Client Version: 4.11.0
Kustomize Version: v4.5.4
Server Version: 4.11.0
Kubernetes Version: v1.24.0+9546431

ODF version

[root@hpo-app1 ~]# oc get csv
NAME                                   DISPLAY                       VERSION               REPLACES                          PHASE
mcg-operator.v4.11.1                   NooBaa Operator               4.11.1                mcg-operator.v4.11.0              Succeeded
metallb-operator.4.11.0-202208300306   MetalLB Operator              4.11.0-202208300306                                     Succeeded
ocs-operator.v4.11.1                   OpenShift Container Storage   4.11.1                ocs-operator.v4.11.0              Succeeded
odf-csi-addons-operator.v4.11.1        CSI Addons                    4.11.1                odf-csi-addons-operator.v4.11.0   Succeeded
odf-operator.v4.11.1                   OpenShift Data Foundation     4.11.1                odf-operator.v4.11.0              Succeeded

When running warp consecutively on 3 IP’s, the run fails due to error “warp: <ERROR> upload error: We encountered an internal error. Please try again”. On checking end-points logs, found that error i.e "upload_stream had error: [Error: No space left on device] { code: 'ENOSPC' } is returned for all runs.

Actual behavior

  1. Warp run is failing

Expected behavior

1.Warp run should execute with any error.

Steps to reproduce

  1. Setup BM with CNSA/CSI RC4, ODF 4.11.1, latest DAS operator.
  2. Run warp on all three metallb IPs with 3 different users.

More information - Screenshots / Logs / Other output

noobaa_diagnostics_1663759506.tar.gz

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:23 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
rkomanducommented, Sep 21, 2022

This is the current status on the hpofvt1 machine (neesha m/c) atm

for i in `oc get pods  |grep noobaa-endpoint | awk ' {print $1}'`; do oc rsh $i ulimit -n; oc rsh $i lsof |wc -l; echo $i is done; done
1048576
505
noobaa-endpoint-5c77fc9bd5-2g5zc is done
1048576
494
noobaa-endpoint-5c77fc9bd5-8tc4f is done
1048576
516
noobaa-endpoint-5c77fc9bd5-brx4w is done
1048576
483
noobaa-endpoint-5c77fc9bd5-ckhwd is done
1048576
494
noobaa-endpoint-5c77fc9bd5-hq2j8 is done
1048576
483
noobaa-endpoint-5c77fc9bd5-l7wrl is done
1048576
494
noobaa-endpoint-5c77fc9bd5-nlkp7 is done
1048576
483
noobaa-endpoint-5c77fc9bd5-pkrwm is done
1048576
483
noobaa-endpoint-5c77fc9bd5-zv7ld is done

0reactions
romayaloncommented, Sep 28, 2022

closing it per @rkomandu last comment

Read more comments on GitHub >

github_iconTop Results From Across the Web

Top 3 Ways to Fix “No Space Left on Device” Error in Linux
Fix 1: Restart Processes Using Deleted Files ... The most probable cause of the “No space left on device” error is a process...
Read more >
Why did my execution fail with the error 'No space left on ...
Why did my execution fail with the error 'No space left on device'? · 1) Try a new hardware tier. · 2) Reduce...
Read more >
How to fix No space left on device error
You are running out of disk space ; You are using a disk over a channel (such as iSCSI) that is no longer...
Read more >
Filesystem - No space left error, but there is space - Ask Ubuntu
The ext4 file system Ubuntu uses has only a limited number of so-called "inodes", which is determined when you format a partition.
Read more >
npm ERR! No Space left on device · Issue #1131 - GitHub
I got this problem on a build agent machine, where I had two build agents running, each with a bunch of project temp...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found