| Bug #29097 | fsp_get_available_space_in_free_extents() is capped at 4TB | ||
|---|---|---|---|
| Submitted: | 14 Jun 2007 7:40 | Modified: | 25 Aug 2007 16:30 |
| Reporter: | Domas Mituzas | ||
| Status: | Closed | ||
| Category: | Server: InnoDB | Severity: | S3 (Non-critical) |
| Version: | 5.0, 5.1, 32bit | OS: | Any |
| Assigned to: | Vasil Dimov | Target Version: | |
[15 Jun 2007 18:15]
Heikki Tuuri
Assigning this to Vasil.
[25 Jul 2007 3:36]
Timothy Smith
Queued to 5.1-maint
[2 Aug 2007 21:12]
Bugs System
Pushed into 5.1.21-beta
[3 Aug 2007 3:58]
Paul DuBois
Noted in 5.1.21 changelog. A maximum of 4TB InnoDB free space was reported by SHOW TABLE STATUS, which is incorrect on systems with more than 4TB space.
[16 Aug 2007 2:56]
Timothy Smith
Queued to 5.0-maint
[20 Aug 2007 12:05]
Bugs System
Pushed into 5.0.48
[20 Aug 2007 12:20]
Bugs System
Pushed into 5.1.22-beta
[25 Aug 2007 16:30]
Paul DuBois
Noted in 5.0.48 changelog.
Description: fsp_get_available_space_in_free_extents(), used for InnoDB free space report, is ulint, hence the output capped at 4TB. At systems with more free space in tablespaces that produces wrong reports. fprintf(srv_dict_tmpfile, "InnoDB free: %lu kB", (ulong) fsp_get_available_space_in_free_extents( prebuilt->table->space)); How to repeat: 'SHOW TABLE STATUS' Suggested fix: use real values!