New issue
Advanced search Search tips

Issue 830474 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Zip Archiver: Generated archive file exceeds Drive quota

Project Member Reported by yamaguchi@chromium.org, Apr 9 2018

Issue description

Chrome Version: 67.0.3393.0

Steps To Reproduce:
(1) Fill Google Drive with any files until the available space becomes about 10MB.
(2) Create a ZIP file in My Drive that almost uses up the available space. (e.g. 9MB zip file)
(3) Select the ZIP file, choose "zip selection" command.

The intention of step(3) is create a new ZIP file that won't fit in the Drive quota (but local disk).
Note that it's usually difficult to estimate the size of archive file generated by zipping. Practically, zipping a ZIP archive file will result in the almost the same size of the archive as the original file.

Expected Result:
It doesn't leave a new ZIP file in the folder.
It shows error message telling the operation failed because there is not enough space.

Actual Result:
It creates a zip file on local cache directory of the Drive, then starts to sync it to Drive.
As a result,
- user sees the file in the Drive folder
- however the file is not uploaded to Drive.
- error message appears in the Files app until the file can be synced. (it continues to retry uploading, across sessions)
  "Syncing... 1 error."

  "Syncing Archive.zip..."
  "Copy operation failed. There is not enough space."

  or "Archive.zip" was not uploaded. There is not enough free space in your Google Drive.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
This issue is always reproducible by the steps above.

What is the impact to the user, and is there a workaround? If so, what is
it?
It causes repeated network communication.
As a workaround, user can delete the ZIP file to cancel operation, or remove other files on Drive to empty space and upload the ZIP file.

 
This is not specific to Zip Archiver.
Copy operation in the Files app also has the same issue.
For example, when duplicating a file in the same folder by Ctrl+C and then Ctrl+V.
Status: WontFix (was: Assigned)
I think this is WAI and consistent with other operations. Also, as mentioned, there is a message that alerts users files not uploaded.

Even when Zip Archiver checks Drive quota, the Drive space might be filled when the zip file is uploaded. So this will still happen.

Sign in to add a comment