MySQL Bugs: #18051: DD: No ability to get information on correct free space usage

Bug #18051	DD: No ability to get information on correct free space usage
Submitted:	7 Mar 2006 22:15	Modified:	21 Apr 2006 7:54
Reporter:	Omer Barnir (OCA)	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Cluster: Cluster (NDB) storage engine	Severity:	S2 (Serious)
Version:	5.1.8	OS:	Linux (Linux 32 Bit OS)
Assigned to:		CPU Architecture:	Any

Description:
*** This bug is opened as a clarification of bug 17844 ***
Bug 17844 was intended to report a prblems in the implementation of reporting available free space (as listed in WL3087). 
As a result of wrong information stated in the implementation of WL3087, 17844 is presenting this problem as a problem in INFORMATION_SCHEMA.FILES and it is not.

WL 3087 was opened to track implementation of the ability to report free available space in DD (part of functionality mentioned in WL 1359.

The functionality was not implemented properly and the only information currently available is about free extents using INFORMATION_SCHEMA.FILES.

Initially this information is scewed by granularity (only reporting free space in free extents), but as time goes by and data is being removed from tabes, this information becomes completly inacurate since all extents are likly to have free space in them but none will be completely free.

How to repeat:
See example of loading data in bug 17844

Suggested fix:
Implement WL3087 correctly

I reopeen the WL (some weeks ago), and made some suggestions to what you might do.
Jeb looked at the at thought they seemed ok.

Once someone decides that this WL should be implemented, you're free to reopen this bug.