Follow

About this task

This task creates a filesystem on an InfiniBox system.

Prerequisites

Before you begin

There are two options to create a filesystem on the GUI. One option is from the Pools screen. The other is from the Volumes & FS screen.

  • Click the Pools icon and place the cursor on the pool in which you will create the filesystem
  • Click the Volumes & FS icon on the toolbar on the left

Acceptable filesystem size

InfiniBox rounds up filesystem with a size that is not a multiplication of 64KiB.

  • A filesystem with a size that is not a multiplication of 512B is rejected with an error. 

Determining the filesystem size

  • When determining the physical size of the filesystem, it is recommended to leave some room for the filesystem metadata (several megabytes per filesystem)

Small file capacity accounting

  • InfiniBox optimizes data layout per file size:
    • Very small files (below 128 Bytes) are stored inside the metadata structure (Btree) and do not consume additional space at all
    • Small files (below 64KB) 
      • Allocated with a 64KB space, and the empty space (within the 64KB) is filled with zeroes, which our compression removes
      • The files are stored in 4KB increments, so, for example, a 7KB file will be either:
        • 4KB if it was able to compress to <4KB
        • 8KB if it was not able to compress at all, or compressed to >4KB
    • Large files (above 64KB) are compressed and their compressed-size is rounded up to 4KB increments
  • Since the compression affects the "Allocated", and "Snapshots" capacity, but does not reduce the "Used" capacity counters, small files are still reported back to the client as consuming 64KB
    • Filesystems that are provisioned with a size that is a multiplication of 4KB will have their "Used" counter identical to "Allocated"
  • The best practice is to this provision the filesystem and increase its size to compensate for the virtually inflated files

Symbolic links capacity accounting

As symbolic links are small enough to be stored within the filesystem metadata structure, they do not require an actual file. The symbolic link capacity is accounted for as follows:

  • 1 iNode
  • 0 capacity

Instructions

  1. On the GUI, either:
    • On the Pools screen: Click the Actions button and select Create a filesystem from the pop-up menu.
    • On the Volumes & FS screen: Click Create and select Filesystem from the list.
    The Create Filesystem screen opens.
  2. Enter a name for the filesystem. You can provision several filesystems at once. In such a case, the name will serve as a prefix for the created series of filesystems.
    Enter a size for the filesystem, select whether the filesystem is thin provisioned, and select a pool.
    Click Advanced to set the number of filesystems that will be created, and select whether to allow the filesystem to use the system's SSD drives.
    Watch the pool capacity gauges at the right pane of the screen. The capacity gauges provide an idea of the impact of the created filesystem on the pool capacity.
    Click Create.
  3. The filesystem is created. In the example on the screenshot, 10 filesystems are created, numbered 101 to 110.

Related tasks

This task, and all other filesystem tasks are available both on the GUI and InfiniShell.

Related InfiniShell commands

  • fs.cache - enabling the filesystem to use InfiniBox flash cache
  • fs.create - creating a new filesystem
  • fs.delete - deleting a filesystem
  • fs.move - moving the filesystem between pools
  • fs.query - listing the filesystems and their properties
  • fs.reclaimable - calculating the reclaimed capacity in case of filesystem deletion
  • fs.rename - renaming the filesystem
  • fs.resize - resizing the filesystem
  • fs.restore - restore data state of a filesystem from a previous snapshot
  • fs.set_thin - setting the filesystem provisioning type
  • fs.tree - displaying the hierarchy of the filesystem along with its snapshots
  • fs.write_enable - enabling write access to a filesystem
  • fs.write_protect - protecting a filesystem from writes



Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Comments