| Skip Navigation Links | |
| Exit Print View | |
|
Sun QFS File System 5.3 Configuration and Administration Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Sun QFS File System 5.3 Configuration and Administration Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
2. About the Master Configuration File
Configuration Examples for Local File Systems
Simple File System Configuration Example
How to Configure a Simple File System
Round-Robin Configuration Example
How to Configure the System for Round-Robin Allocation
Local Striping Configuration Example
How to Configure the System for Local Striping
Striped Group Configuration Example
How to Configure the System for Striped Groups
Configuration Example for a Shared File System on an Oracle Solaris OS Platform
How to Configure the Shared File System
Configuration Examples for Highly Available File Systems
How to Create an mcf File for a Highly Available File System
Configuration Example for a Shared File System on an Oracle Solaris Cluster Platform
How to Create an mcf File for a Shared File System in an Oracle Solaris Cluster Environment
4. Configuring the File System
5. Configuring a Shared File System
6. Administering File System Quotas
7. Advanced File System Topics
9. Configuring WORM-FS File Systems
11. Using QFS File Systems with SANergy (SAN-QFS)
In this example, ash and elm are nodes in an Oracle Solaris Cluster environment. Host ash is the metadata server. The keyword shared in this example's mcf file indicates to the system that this is a shared file system. .
You must create the mcf file on the node that you want to designate as the metadata server.
The scdidadm command administers the device identifier (DID) devices. The -L option lists all the DID device paths, including those on all nodes in the Oracle Solaris Cluster environment.
The following code example uses StorageTek T3 arrays in a RAID-5 configuration. The output shows that you can use devices 4 through 9 for configuring the disk cache for a shared file system.
ash# scdidadm -L 1 ash:/dev/rdsk/c0t6d0 /dev/did/rdsk/d1 2 ash:/dev/rdsk/c1t1d0 /dev/did/rdsk/d2 3 ash:/dev/rdsk/c1t0d0 /dev/did/rdsk/d3 4 elm:/dev/rdsk/c6t50020F2300004921d1 /dev/did/rdsk/d4 4 ash:/dev/rdsk/c5t50020F2300004921d1 /dev/did/rdsk/d4 5 elm:/dev/rdsk/c6t50020F2300004921d0 /dev/did/rdsk/d5 5 ash:/dev/rdsk/c5t50020F2300004921d0 /dev/did/rdsk/d5 6 elm:/dev/rdsk/c6t50020F23000049CBd1 /dev/did/rdsk/d6 6 ash:/dev/rdsk/c5t50020F23000049CBd1 /dev/did/rdsk/d6 7 elm:/dev/rdsk/c6t50020F23000049CBd0 /dev/did/rdsk/d7 7 ash:/dev/rdsk/c5t50020F23000049CBd0 /dev/did/rdsk/d7 8 elm:/dev/rdsk/c6t50020F23000055A8d0 /dev/did/rdsk/d8 8 ash:/dev/rdsk/c5t50020F23000055A8d0 /dev/did/rdsk/d8 9 elm:/dev/rdsk/c6t50020F23000078F1d0 /dev/did/rdsk/d9 9 ash:/dev/rdsk/c5t50020F23000078F1d0 /dev/did/rdsk/d9 10 elm:/dev/rdsk/c0t6d0 /dev/did/rdsk/d10 11 elm:/dev/rdsk/c1t1d0 /dev/did/rdsk/d11 12 elm:/dev/rdsk/c1t0d0 /dev/did/rdsk/d12
The following code example shows the format command output from all the /dev/did devices. You will need this information when you build the mcf file.
ash# format /dev/did/rdsk/d4s2 selecting /dev/did/rdsk/d4s2 Primary label contents: Volume name = < > ascii name = <SUN-T300-0118 cyl 34530 alt 2 hd 64 sec 32> pcyl = 34532 ncyl = 34530 acyl = 2 nhead = 64 nsect = 32 Part Tag Flag Cylinders Size Blocks 0 usr wm 0 - 17264 16.86GB (17265/0/0) 35358720 1 usr wm 17265 - 34529 16.86GB (17265/0/0) 35358720 2 backup wu 0 - 34529 33.72GB (34530/0/0) 70717440 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 0 0 (0/0/0) 0 6 unassigned wu 0 0 (0/0/0) 0 7 unassigned wu 0 0 (0/0/0) 0 ash# format /dev/did/rdsk/d5s2 selecting /dev/did/rdsk/d5s2 Volume name = < > ascii name = <SUN-T300-0118 cyl 34530 alt 2 hd 192 sec 64> pcyl = 34532 ncyl = 34530 acyl = 2 nhead = 192 nsect = 64 Part Tag Flag Cylinders Size Blocks 0 usr wm 0 - 17264 101.16GB (17265/0/0) 212152320 1 usr wm 17265 - 34529 101.16GB (17265/0/0) 212152320 2 backup wu 0 - 34529 202.32GB (34530/0/0) 424304640 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 0 0 (0/0/0) 0 6 unassigned wu 0 0 (0/0/0) 0 7 unassigned wu 0 0 (0/0/0) 0 ash# format /dev/did/rdsk/d6s2 selecting /dev/did/rdsk/d6s2 Volume name = < > ascii name = <SUN-T300-0118 cyl 34530 alt 2 hd 64 sec 32> pcyl = 34532 ncyl = 34530 acyl = 2 nhead = 64 nsect = 32 Part Tag Flag Cylinders Size Blocks 0 usr wm 0 - 17264 16.86GB (17265/0/0) 35358720 1 usr wm 17265 - 34529 16.86GB (17265/0/0) 35358720 2 backup wu 0 - 34529 33.72GB (34530/0/0) 70717440 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 0 0 (0/0/0) 0 6 unassigned wu 0 0 (0/0/0) 0 7 unassigned wu 0 0 (0/0/0) 0 ash# format /dev/did/rdsk/d7s2 selecting /dev/did/rdsk/d7s2 Volume name = < > ascii name = <SUN-T300-0118 cyl 34530 alt 2 hd 192 sec 64> pcyl = 34532 ncyl = 34530 acyl = 2 nhead = 192 nsect = 64 Part Tag Flag Cylinders Size Blocks 0 usr wm 0 - 17264 101.16GB (17265/0/0) 212152320 1 usr wm 17265 - 34529 101.16GB (17265/0/0) 212152320 2 backup wu 0 - 34529 202.32GB (34530/0/0) 424304640 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 0 0 (0/0/0) 0 6 unassigned wu 0 0 (0/0/0) 0 7 unassigned wu 0 0 (0/0/0) 0 ash# format /dev/did/rdsk/d8s2 selecting /dev/did/rdsk/d8s2 Volume name = < > ascii name = <SUN-T300-0118 cyl 34530 alt 2 hd 128 sec 128> pcyl = 34532 ncyl = 34530 acyl = 2 nhead = 128 nsect = 128 Part Tag Flag Cylinders Size Blocks 0 usr wm 0 - 17264 134.88GB (17265/0/0) 282869760 1 usr wm 17265 - 34529 134.88GB (17265/0/0) 282869760 2 backup wm 0 - 34529 269.77GB (34530/0/0) 565739520 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 0 0 (0/0/0) 0 6 unassigned wu 0 0 (0/0/0) 0 7 unassigned wu 0 0 (0/0/0) 0 ash# format /dev/did/rdsk/d9s2 selecting /dev/did/rdsk/d9s2 Volume name = < > ascii name = <SUN-T300-0118 cyl 34530 alt 2 hd 128 sec 128> pcyl = 34532 ncyl = 34530 acyl = 2 nhead = 128 nsect = 128 Part Tag Flag Cylinders Size Blocks 0 usr wm 0 - 17264 134.88GB (17265/0/0) 282869760 1 usr wm 17265 - 34529 134.88GB (17265/0/0) 282869760 2 backup wu 0 - 34529 269.77GB (34530/0/0) 565739520 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 0 0 (0/0/0) 0 6 unassigned wu 0 0 (0/0/0) 0 7 unassigned wu 0 0 (0/0/0) 0
The format command displays the space available on a device, but it does not indicate whether a disk is mirrored or striped. This code example's format command output reveals the following information that is used during creation of the mcf file shown in the next code example:
Output for devices d4s0 and d6s0 shows 16.86 Gbytes each. These devices are assigned equipment numbers 501 and 502, respectively, in the mcf file. They are the appropriate size to use for metadata slices.
Output for devices d8s0 and d9s0 shows 134.88 Gbytes each. These devices are assigned equipment number 503 and 504, respectively, in the mcf file. They are the appropriate size to be used for storing data.
Include the shared keyword in the Additional Parameters field.
Put the file system's mm devices on mirrored (RAID-1) disks. The mm devices should constitute about 10% of the space allocated for the entire file system.
The following code example shows the resulting mcf file.
#Equipment Eq Eq Family Additional #Identifier Ord Type Set Parameters #-------------------- --- ---- ------ ---------- # # Family Set sqfs1 (shared FS for SunCluster) # sqfs1 500 ma sqfs1 shared sqfs1 500 ma sqfs1 shared /dev/did/dsk/d4s0 501 mm sqfs1 - /dev/did/dsk/d6s0 502 mm sqfs1 - /dev/did/dsk/d8s0 503 mr sqfs1 - /dev/did/dsk/d9s0 504 mr sqfs1 -
|