Limitations

Edit online

A number of limitations apply to this procedure.

  • Maximum individual file size limit is 1 TB.
  • A maximum of 100 shares per file system is supported.
  • A maximum of 1000 File Systems is permitted.
  • A file system cannot expose two shares of the same name.
  • The system does not support simultaneous writing to the same file from multiple clients. This action can cause data corruption in those files.
  • The system supports File Accesser devices that are defined at two sites. This restriction is not enforced.
  • Native File Interface does not support netgroups or integration with LDAP/NIS+ servers.
  • Changing the IP of seed nodes, removing seed nodes, reimaging seed nodes, and turning off seed nodes results in undesired behavior.
  • Host names and IPs of devices must not be changed.
  • File Accesser devices should never be left offline for periods of time over 4 hours.
  • HA recovery is triggered by outages at 10 seconds.
  • A user cannot write an object via S3 and read by using NFS.
  • The HA Virtual IP table on the Monitor File Server Pool page is only as recent as existing polling cycles allow.
  • Native File Interface supports the failure of only a single device.
  • All devices in a File Server Pool must be located in the same site.
  • A device that is in a File Server Pool cannot have its site changed unless it is removed from the File Server Pool.
  • The Cloud Object Storage Manager Database should be backed up after every Native File Interface-related configuration change. It includes but is not limited to file system or share creation and modification.