CREATE TABLESPACE Statement When determining the path used for a data file,  NDB  does not expand the  ~  (tilde) character. When multiple data nodes are run on the same physical host, the following considerations apply: •You cannot specify an absolute path when creating a data file. •It is not possible to create tablespace data files outside the data node file system directory, unless each data node has a separate data directory. •If each data node has its own data directory, data files can be created anywhere within this directory. •If each data node has its own data directory, it may also be possible to create a data file outside the node’s data directory using a relative path, as long as this path resolves to a unique location on the host file system for each data node running on that host. • FILE_BLOCK_SIZE : This option—which is specific to  InnoDB  general tablespaces, and is ignored by  NDB —defines the block size for the tablespace data file. Values can be specified in bytes or kilobytes. For example, an 8 kilobyte file block size can be specified as 8192 or 8K. If you do not specify this option,  FILE_BLOCK_SIZE  defaults to the  innodb_page_size  value. FILE_BLOCK_SIZE  is required when you intend to use the tablespace for storing compressed  InnoDB tables ( ROW_FORMAT=COMPRESSED ). In this case, you must define the tablespace  FILE_BLOCK_SIZE when creating the tablespace. If  FILE_BLOCK_SIZE  is equal the  innodb_page_size  value, the tablespace can contain only tables having an uncompressed row format ( COMPACT ,  REDUNDANT , and  DYNAMIC ). Tables with a COMPRESSED  row format have a different physical page size than uncompressed tables. Therefore, compressed tables cannot coexist in the same tablespace as uncompressed tables. For a general tablespace to contain compressed tables,  FILE_BLOCK_SIZE  must be specified, and the FILE_BLOCK_SIZE  value must be a valid compressed page size in relation to the  innodb_page_size value. Also, the physical page size of the compressed table ( KEY_BLOCK_SIZE ) must be equal to FILE_BLOCK_SIZE/1024 . For example, if  innodb_page_size=16K , and  FILE_BLOCK_SIZE=8K , the  KEY_BLOCK_SIZE  of the table must be 8. For more information, see Section 15.6.3.3, “General Tablespaces” . • USE LOGFILE GROUP : Required for  NDB , this is the name of a log file group previously created using CREATE LOGFILE GROUP . Not supported for  InnoDB , where it fails with an error. • EXTENT_SIZE : This option is specific to NDB, and is not supported by InnoDB, where it fails with an error.  EXTENT_SIZE  sets the size, in bytes, of the extents used by any files belonging to the tablespace. The default value is 1M. The minimum size is 32K, and theoretical maximum is 2G, although the practical maximum size depends on a number of factors. In most cases, changing the extent size does not have any measurable effect on performance, and the default value is recommended for all but the most unusual situations. An  extent  is a unit of disk space allocation. One extent is filled with as much data as that extent can contain before another extent is used. In theory, up to 65,535 (64K) extents may used per data file; however, the recommended maximum is 32,768 (32K). The recommended maximum size for a single data file is 32G—that is, 32K extents × 1 MB per extent. In addition, once an extent is allocated to a given partition, it cannot be used to store data from a different partition; an extent cannot store data from more than one partition. This means, for example that a tablespace having a single datafile whose 2600 Note