New issue
Advanced search Search tips

Issue 835109 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

Download error message "Disk full" incorrectly reported when downloading > 4 GB files to FAT32

Reported by jasongro...@gmail.com, Apr 20 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Plug in a flash drive formatted to FAT32
2. In chrome://settings, ensure that "Ask where to save each file before downloading" is enabled
3. Find a file that has size >= 4 GB (e.g., the .mbox file for a Google data export of a full gmail, or (untested) http://www.engineerhammad.com/2015/04/Download-Test-Files.html)
4. Download the file to the flash drive
5. Wait until the file fails to download and look at the error message

What is the expected behavior?
I expect to see something like "Failed - File too big for FAT32" or "Failed - File too big for filesystem format".  Ideally, Chrome would warn me before it even tried to download the file that the filesystem wouldn't support files that large.  Even better, Chrome would offer me an option to put the file into a multipart .zip or .tar.gz archive on-the-fly as it was downloading it.

What went wrong?
I see "Failed - Disk full" which made me think that maybe Chrome was trying to store temporary files on a different local disk and sent me on a bit of a goose chase.

Did this work before? N/A 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: 10.0
Flash Version: 29.0.0.140
 
Components: -Internals>Network UI>Browser>Downloads
Labels: Needs-Triage-M65
Labels: Triaged-ET TE-NeedsTriageFromHYD
The issue require a USB flash drive to be formatted to FAT32. As ET-team doesn't have the set up to test the issue. Hence, forwarding the issue to inhouse team for further triaging of the issue.

Thanks...!!
Cc: kkaluri@chromium.org
Labels: -TE-NeedsTriageFromHYD TE-Hardware-Dependency
Unable to test this issue because of non-availability of external hard disk from TE end, hence adding TE-Hardware-Dependency label for further triage
Labels: -Pri-2 Pri-3
Status: Available (was: Unconfirmed)
I think updating the error message is a good first step if we can detect it.  Marking as P3 and making available to the team.

Sign in to add a comment