PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment)

F.2.1 sfcadd(1M) Adds file data partitions

[SYNOPSIS]

sfcadd -D raw_device_file[,raw_device_file,...] t_raw_device_file

sfcadd -M raw_device_file[,raw_device_file,...] t_raw_device_file

[DESCRIPTION]

sfcadd adds the file data partition, and the meta partition of the GFS Shared File System having the representative partition specified by operand t_raw_device_file, and separates an update log area. No data has to be saved or restored. The file data partition of the file system can be added even if the file system is mounted status or not used due to the file system is in unmounted status.

If the partition is not added due to a system failure, the target partition is correctly managed as being currently processed as the file system. Use sfcinfo(1M) to confirm whether the partition is being processed.

[OPTIONS]

The following options can be specified:

-D raw_device_file[,raw_device_file]

Uses a character special device to specify the partition to be added as the file data area. When adding multiple partitions, a comma must separate the character special devices specified.

-M raw_device_file[,raw_device_file]

Uses a character special device to specify the partition to be added as the meta data area. When adding multiple partitions, a comma must separate the character special devices specified.

[OPERAND]

The following operand can be specified:

t_raw_device_file

Specifies path name of a character-special device for the representative partition of the GFS Shared File System to target for the transaction.

[EXAMPLES]

Newly adding /dev/sfdsk/gfs/rdsk/volume2 and /dev/sfdsk/gfs/rdsk/volume3 as file data partitions into the existing GFS Shared File System whose representative partition is /dev/sfdsk/gfs/rdsk/volume1.

# sfcadd -D /dev/sfdsk/gfs/rdsk/volume2,/dev/sfdsk/gfs/rdsk/volume3 /dev/sfdsk/gfs/rdsk/volume1

Newly adding /dev/sfdsk/gfs/rdsk/volume2 as meta partitions into the existing GFS Shared File System whose representative partition is /dev/sfdsk/gfs/rdsk/volume1.

# sfcadd -M /dev/sfdsk/gfs/rdsk/volume2 /dev/sfdsk/gfs/rdsk/volume1

[SEE ALSO]

fsck_sfcfs(1M), mkfs_sfcfs(1M), sfcadm(1M), sfcinfo(1M), sfcnewfs(1M), sfcnode(1M), sfctune(1M).

dkio(7I) in the "Solaris X Reference Manual Collection."

[NOTES]

• To use sfcadd during the file system is mounted, the target file system must be one mounted as writable and readable by the command execution node.
• A file system can be added partitions only when all hosts that share the file system have started operation. The reason is that the information for these hosts is required.
• sfcadd can add partitions up to the maximum number of partitions (maxvol) specified by sfcnewfs(1M). If the maximum data size (maxdsz) specified by sfcnewfs(1M) is exceeded because of partition addition, a free area that cannot be used due to a management area shortage may be generated.
• To execute sfcadd for the unmounted file system in all nodes, the status of the file system must be normal. If the file system status is abnormal, sfcadd outputs the message
  "file system (partition-name) is corrupted.
  TO FIX: fsck -F sfcfs partition-name''
  Correct the file system status with fsck_sfcfs(1M), then reexecute sfcadd.
• Only the addition of new file data partitions or meta partitions can be made for the file system that is operating mounted file system. This function can be executed only in the node in which the target file system is in mounted mounted status.
• Assume that sfcadd terminates abnormally. In this case, if the target file system contains a partition being processed, reexecute the sfcadd to complete the processing. If to do not that, otherwise, the partition being processed cannot be applied elsewhere.
• A partition cannot be added in the file system associated by sfcproxyjoin(1M) as a acking up agency or a backup place. When adding a partition, it is necessary to cancel correlation.
• When adding a partition newly, a maxcontig value may be set up again automatically. Concretely, when the maximum continuation I/O length (dki_maxtransfer of dkio(7I)) obtained from the driver of an additional device is smaller than the maximum number of the continuation block by sfctune(1M) of the existing file system, it changes to the value of an additional device. When the maxcontig value is changed intentionally, please set up again if needed.