Currently, MediaWiki stores images size as a unsigned 32 bits information. That means a limit of 4 GB (2^32 = 4294967296 bytes).
If we need to allow MediaWiki to store larger files, we need to store this information as 64 bits integers.
The following fields are concerned:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dereckson | T191572 Please upload large file to Wikimedia Commons | |||
| Open | None | T191802 [Epic] Determine a strategy to store files between 5 and 100 Gb | |||
| Open | None | T191804 Allow to store files between 4 and 5 Gb | |||
| Open | None | T191805 Allow Mediawiki to store file size greater than 32 bits |
image.img_size oldimage.oi_size filearchive.fa_size uploadstash.us_size (to be confirmed, as this uses chunked uploads?)
No, all these are fine. A 32 bit field can store the number 2^32 fine. These fields should work fine as long as the file size is less than 2^(2^32), which we're in no danger of approaching :)
The fields are currently defined in tables.sql as int unsigned which is a 32-bit type with a range from 0 to 2^32 - 1 (one byte shy of 4 GiB). To record sizes of files of 4 GiB or higher, redefining them as bigint unsigned, a 64-bit type, would be required.
It will also be necessary to ensure that nothing else breaks when interpreting the large numbers as integers (PHP uses C long type for integers, which is 64 bits on Linux x86-64, so this should not be a problem in practice).