-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Not enough disk space (Needed: Unknown size) when caching on a cluster #1785
Comments
Hi ! What do you mean by "disk_usage(".").free` can't compute on the cluster's shared disk" exactly ? |
Yes, that's right. It shows 0 free space even though there is. I suspect it might have to do with permissions on the shared disk. >>> disk_usage(".")
usage(total=999999, used=999999, free=0) |
That's an interesting behavior... |
I think its an issue on the clusters end (unclear exactly why -- maybe something with docker containers?), will close the issue |
Were you able to figure it out? |
@philippnoah I had fixed it with a small hack where I patched |
@olinguyen Thanks for the suggestion, it works but I had to to edit builder.py in the installed package. Can you please explain how were you able to do this using import? |
I was able to patch the builder code in my notebook before the load data call and it works.
|
import datasets |
I'm running some experiments where I'm caching datasets on a cluster and accessing it through multiple compute nodes. However, I get an error when loading the cached dataset from the shared disk.
The exact error thrown:
>>> load_dataset(dataset, cache_dir="/path/to/cluster/shared/path") OSError: Not enough disk space. Needed: Unknown size (download: Unknown size, generated: Unknown size, post-processed: Unknown size)
utils.has_sufficient_disk_space
fails on each job because of how the cluster system is designed (disk_usage(".").free
can't compute on the cluster's shared disk).This is exactly where the error gets thrown:
https://github.com/huggingface/datasets/blob/master/src/datasets/builder.py#L502
What would be a good way to circumvent this? my current fix is to manually comment out that part, but that is not ideal.
Would it be possible to pass a flag to skip this check on disk space?
The text was updated successfully, but these errors were encountered: