Chrome Version: 59.0.3071.25
OS: ChromeOS

What steps will reproduce the problem?
(1) Determine how much space your system has (e.g. use the menu in the Files app).
(2) Find a file that is >50% of that size (in my case I had ~4GB free and chose a 3GB file).
(3) Ensure that you have enough Drive quota left for a file that size!
(4) Cut the file from Downloads, and Paste it into Drive.

What is the expected result?

Expect that the file is moved to Drive succesfully.

If the move fails (because Drive is technically a different file-system and we have to create a local copy, effectively doubling the local storage requirement until we delete the original...) then expect that the amount of free space in local storage returns to whatever it was before the Cut/Paste operation was started.

What happens instead?

1. The operation fails with an error indicating that there wasn't enough space. This is confusing for the user, since there *is* enough space in Drive; the issue is really a limitation of the implementation of the Drive integration in Files.

2. The local storage space estimate as reported by Files drops to a couple of megabytes, where before the Cut/Paste it had been ~1GB in my case. This suggests we're leaking the truncated file in the Drive cache. :(

3. The system gets jankier. This makes sense since the local storage is almost entirely full, so we're presumably thrashing the Flash storage trying to make space for anything else we write.