mysql gfs2_读gfs2官方文档

Red Hat does not support using GFS2 for cluster file system deployments greater than 16 nodes.

However, the current supported maximum size of a GFS2 file system for 64-bit hardware is 100TB.

The current supported maximum size of a GFS2 file system for 32-bit hardware is 16TB

Asymmetric cluster configurations in which some nodes have access to the shared storage and others do not are not supported.

The rule of thumb with GFS2 is that smaller is better: it is better to have 10 1TB file systems than one 10TB file system.

With GFS2, you can add journals on the fly.

While there is no defragmentation tool for GFS2 on Red Hat Enterprise Linux, you can defragment individual files by identifying them with the filefrag tool, copying them to temporary files, and renaming the temporary files to replace the originals.

Newer versions of GFS2 include the fallocate(1) system call, which you can use to preallocate blocks of data

Red Hat recommends that you allow a period of around 8-12 weeks of testing on new installations in order to test the system and ensure that it is working at the required performance level.

Mount Options: noatime and nodiratime

Security Enhanced Linux (SELinux) is highly recommended for security reasons in most situations, but it is not supported for use with GFS2.

Setting Up NFS Over GFS2

Samba (SMB or Windows) File Serving Over GFS2

Red Hat performs most quality, sanity, and performance tests on SAN storage with Fibre Channel interconnect

Suspending Activity on a File System

reltime