ndb_desc — Describe NDB Tables For more information about these table properties, see Section 13.1.20.11, “Setting NDB_TABLE Options” . The  Extent_space  and  Free extent_space  columns are applicable only to  NDB  tables having columns on disk; for tables having only in-memory columns, these columns always contain the value  0 . To illustrate their use, we modify the previous example. First, we must create the necessary Disk Data objects, as shown here: (For more information on the statements just shown and the objects created by them, see Section 23.5.10.1, “NDB Cluster Disk Data Objects” , as well as Section 13.1.16, “CREATE LOGFILE GROUP Statement” , and Section 13.1.21, “CREATE TABLESPACE Statement” .) Now we can create and populate a version of the  fish  table that stores 2 of its columns on disk (deleting the previous version of the table first, if it already exists): shell>  ./ndb_desc -c localhost fish -d test -p -- fish -- Version: 1 Fragment type: HashMapPartition K Value: 6 Min load factor: 78 Max load factor: 80 Temporary table: no When run against this version of the table,  ndb_desc  displays the following output: 4301 CREATE LOGFILE GROUP lg_1 ADD UNDOFILE ’undo_1.log’ INITIAL_SIZE 16M UNDO_BUFFER_SIZE 2M ENGINE NDB; ALTER LOGFILE GROUP lg_1 ADD UNDOFILE ’undo_2.log’ INITIAL_SIZE 12M ENGINE NDB; CREATE TABLESPACE ts_1 ADD DATAFILE ’data_1.dat’ USE LOGFILE GROUP lg_1 INITIAL_SIZE 32M ENGINE NDB; ALTER TABLESPACE ts_1 ADD DATAFILE ’data_2.dat’ INITIAL_SIZE 48M ENGINE NDB; DROP TABLE IF EXISTS fish; CREATE TABLE fish ( id INT NOT NULL AUTO_INCREMENT, name VARCHAR(20) NOT NULL, length_mm INT NOT NULL, weight_gm INT NOT NULL, PRIMARY KEY pk (id), UNIQUE KEY uk (name) ) TABLESPACE ts_1 STORAGE DISK ENGINE=NDB; INSERT INTO fish VALUES (NULL, ’guppy’, 35, 2), (NULL, ’tuna’, 2500, 150000), (NULL, ’shark’, 3000, 110000), (NULL, ’manta ray’, 1500, 50000), (NULL, ’grouper’, 900, 125000), (NULL ,’puffer’, 250, 2500);