PRIMECLUSTER Global File Services Configuration and Administration Guide 4.2 (Solaris(TM) Operating Environment) |
Contents Index |
Part 3 Global File Services Shared File System | > Chapter 22 File System Operations (Command) | > 22.5 Change (partition configuration) |
A new file data partition can be added to an existing mounted GFS Shared File System as a file data area without backing-up and restoring data.
The partition in which the GFS Shared File System is created and operated must be on a shared disk recognized by PRIMECLUSTER. To use a GDS logical volume as a target device, it must be active.
Check that the disk is set up as shared for simultaneous access.
If a partition has set up the disk as shared by automatic detection of shared disks, it is already set as a shared disk for simultaneous access and no further action is needed.
When registering a GDS logical volume with a class, set the disk type as shared and the scope to include all the nodes that share the GFS Shared File System.
For GDS disk class operations, see the applicable items under "Operation using Global Disk Services Management View" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
For GDS logical volume operations, see the applicable items under "Operation using Global Disk Services Management View" in the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
The following procedures describe how to add a new file data or meta-data partition to an existing GFS Shared File System.
A new file data partition can be added to an existing mounted GFS Shared File System, use sfcadd(1M).
How to add a file data partition (/dev/sfdsk/gfs/rdsk/volume2) to an existing file system (/dev/sfdsk/gfs/rdsk/volume1) using sfcadd(1M) is shown below.
For details on the sfcadd(1M) option, see Appendix F.2.1, "sfcadd(1M)." Notes are the same for mounted and unmounted file systems. See Notes in Section 22.5.1.3.1, "Adding a file data partition."
1. Check the configuration of the current file system.
# sfcinfo /dev/sfdsk/gfs/dsk/volume1 /dev/sfdsk/gfs/dsk/volume1: FSID special size Type mount 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 407144 META ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 3761416 DATA ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 5120 LOG -----
2. Add a file data partition as file data area.
# sfcadd -D /dev/sfdsk/gfs/rdsk/volume2 /dev/sfdsk/gfs/rdsk/volume1
3. Confirm that the file data partition has been added.
# sfcinfo /dev/sfdsk/gfs/dsk/volume1 /dev/sfdsk/gfs/dsk/volume1: FSID special size Type mount 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 407144 META ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 3761416 DATA ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 5120 LOG ----- 1 /dev/sfdsk/gfs/dsk/volume2(3fa00c1) 65512 DATA -----
Use sfcadd(1M) to add partitions to the meta-data area while the file system is mounted.
The procedures for adding a meta partition (/dev/sfdsk/gfs/rdsk/volume2) to an existing file system (/dev/sfdsk/gfs/rdsk/volume1) are shown below.
For details on the sfcadd(1M) options, see Appendix F.2.1, "sfcadd(1M)."
1. Check the current file system configuration.
# sfcinfo /dev/sfdsk/gfs/dsk/volume1 /dev/sfdsk/gfs/dsk/volume1: FSID special size Type mount 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 407144 META ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 3761416 DATA ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 5120 LOG -----
2. Add a meta-partition
# sfcadd -M /dev/sfdsk/gfs/rdsk/volume2 /dev/sfdsk/gfs/rdsk/volume1
3. Check that a meta-data partition has been added.
# sfcinfo /dev/sfdsk/gfs/dsk/volume1 /dev/sfdsk/gfs/dsk/volume1: FSID special size Type mount 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 407144 META ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 3761416 DATA ----- 1 /dev/sfdsk/gfs/dsk/volume1(3fa0081) 5120 LOG ----- 1 /dev/sfdsk/gfs/dsk/volume2(3fa008c) 65512 META -----
Note the following restriction for meta-data partition addition.
A meta-data partition addition is not possible if doing so would exceed the maximum number of partitions (-l maxvol) for the file system, as specified by sfcnewfs(1M).
Contents Index |