-
Notifications
You must be signed in to change notification settings - Fork 28
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
Could not find enough space to create new chunk. Try clearing a few gigabytes of space, or defragging. #70
Comments
It needs contiguous space Edit: Disregard that, I was getting confused. Have you got a lot of compressed files? |
No, the drive isn't compressed at all... It contains a lot of Steam Games, and some Windows Apps that I really don't care about... |
Were you able to resolve this? I ran into the same issue on a 4 TB drive with over 500 GB of free space, I think that should be enough to convert the drive, no? |
See also: https://bugzilla.redhat.com/show_bug.cgi?id=2238054. |
There's really no point in logging it with Red Hat, all they're going to do is send it back to me... |
Thank you, new issue created: #72 |
To all interested parties: to me 4% free space was enough to complete the conversion. |
Yes it's a 2TB drive that's 91% full, but is 174G not enough space to do an "in place" conversion in??
/dev/sdc2 1.9T 1.7T 174G 91% /media/ssd1
And could it not throw this error before it sits there for almost an hour calculating checksums?
The text was updated successfully, but these errors were encountered: