# “No space left on device” when using Robust Speech Challenge + AzureML

**URL:** <https://discuss.huggingface.co/t/no-space-left-on-device-when-using-robust-speech-challenge-azureml/18898>\
**Category:** Beginners\
**Created:** [June 9, 2022, 7:37am UTC](https://discuss.huggingface.co/t/no-space-left-on-device-when-using-robust-speech-challenge-azureml/18898 "2022-06-09T07:37:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![neelan-elucidate-ai](https://avatars.discourse-cdn.com/v4/letter/n/e9bcb4/32.png) [@neelan-elucidate-ai](https://discuss.huggingface.co/u/neelan-elucidate-ai)\
**Post date:** [June 9, 2022, 7:37am UTC](https://discuss.huggingface.co/t/no-space-left-on-device-when-using-robust-speech-challenge-azureml/18898/1 "2022-06-09T07:37:11Z")

</div>

Hi there

I have been trying to train a model as per the `[Robust Speech Event](https://github.com/neelan-elucidate-ai/transformers/tree/main/examples/research_projects/robust-speech-event)`

Training begins but seems to fill up `/dev/sdb1` location which has a total of 119 GB. This happens even when i force the cache to be on a different drive as suggested [here](https://discuss.huggingface.co/t/no-space-left-on-device-when-using-huggingface-sagemaker/5406/3) : both manually in the functions and via env var.

This happens regardless of the dataset used (at fist I thought it was an issue with `"load_dataset("mozilla-foundation/common_voice_7_0", "en")`

I suspect the very large model and data need a very big tmp location but it should be clearing the tmp not filling it up.

Any ideas @patrickvonplaten@osanseviero @anton-l ?

---

<div class="post-metadata">

**Author:** ![neelan-elucidate-ai](https://avatars.discourse-cdn.com/v4/letter/n/e9bcb4/32.png) [@neelan-elucidate-ai](https://discuss.huggingface.co/u/neelan-elucidate-ai)\
**Post date:** [June 9, 2022, 5:48pm UTC](https://discuss.huggingface.co/t/no-space-left-on-device-when-using-robust-speech-challenge-azureml/18898/2 "2022-06-09T17:48:42Z")

</div>

seems it was the `output dir` not the `cache_dir` causing the issue. seem to be running now after changing `output dir`
