title: conda env build fails with "[Errno 28] No space left on device"
body: <p>I'm trying to build a new conda environment in our Sagemaker ec2 environment in a terminal session.  Packages in the original copy of the environment were corrupted, and the environment became unusable. The issue couldn't be fixed by removing packages and re-installing or using <code>conda update</code>.</p>
  <p>I nuked the environment with <code>conda env remove -n python3-cn</code> and then attempted to recreate the environment with:</p>
  <pre><code>conda env create -p /home/ec2-user/SageMaker/anaconda3/envs/python3-cn --file=${HOME}/SageMaker/efs/.sagemaker/python3-cn_environment.yml --force
  </code></pre>
  <p>This environment has been created a number of times in several ec2 instances for individual Sagemaker users.</p>
  <p>Conda logs the following:</p>
  <pre><code>Collecting package metadata (repodata.json): done
  Solving environment: done
  
  Downloading and Extracting Packages
  pytest-arraydiff-0.2 | 14 KB     | ##################################################################################################### | 100% 
  partd-0.3.8          | 32 KB     | ##################################################################################################### | 100% 
  
  ... several progress bar lines later...
  
  psycopg2-2.7.5       | 507 KB    | ##################################################################################################### | 100% 
  Preparing transaction: done
  Verifying transaction: done
  Executing transaction: done
  ERROR conda.core.link:_execute(700): An error occurred while installing package 'defaults::mkl-2018.0.3-1'.
  Rolling back transaction: done
  
  [Errno 28] No space left on device
  ()
  </code></pre>
  <p>The <code>No space left on device</code> error is consistent. I've tried</p>
  <ul>
  <li><code>conda clean --all</code>, removing the environment, re-building the environment</li>
  <li>removing the caches, removing the environment, re-building the environment</li>
  <li>removing the environment, shutting down and restarting JuypiterLab (our Sagemaker is configured to create <code>python3-cn</code> if the environment doesn't exist when JupyterLab starts)</li>
  </ul>
  <p>In the first two, I get <code>Errno 28</code>.</p>
  <p>In the last one, the instance is not created, <code>conda env list</code> does not show the <code>python3-cn</code>, but I see there is a <code>python3-cn</code> directory in the <code>anaconda/envs/</code> directory. If I do <code>conda activate python3-cn</code>, I see the prompt change, but the environment is unusuable. If I try <code>conda update --all</code>, I get a notification that one of the package files has been corrupted.</p>
  <p>Not really sure what to do here. I'm looking for space hogs, but not really finding anything significant.</p>