Allocated PE 0
PV UUID PRCPkx-3Tan-IHgr-0ZLh-iTGt-XWzY-pBkUpM
7. Create the volume group. Keep the physical volumes in the same volume group.
nid00006#
vgcreate fs1 /dev/disk/by-id/dm-uuid-
mpath-360080e50002ff41a0000040b517a2609
/dev/disk/by-id/dm-uuid-mpath-360080e50002ff41a0000040e517a261e
Volume group "fs1" successfully created
8. Create logical volumes.
nid00006#
lvcreate --stripes 2 --stripesize 512k --extents 100%FREE --name fs1 fs1
Logical volume "fs1" created
9. Create the XFS file system using
mkfs
.
nid0006#
mkfs -t xfs /dev/fs1/fs1
10. Mount the XFS file system and verify its availability.
a. Mount the XFS file system to the service node.
nid0006#
mount -t xfs /dev/fs1/fs1 /mnt
b. Display the mount to verify that the file system is available.
nid00006#
df -h --type xfs
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/fs1-fs1 15T 34M 15T 1% /mnt
11. Edit the
/etc/fstab
file on the DVS server node to add the following:
/dev/mapper/fs1-fs1 /scratch xfs defaults 1 0
If there is a secondary XFS/DVS node used as a high-availability manual backup and failover device for the
primary XFS/DVS node, do not add the mount definition entry to that node configuration. XFS is neither a
clustered nor a shared file system and can be natively mounted on only one node at any given time. If the file
system is mounted on more than one node, there is a great risk of data corruption.
6.1.8.4 Configure DVS Using
modeprobe.d
About this task
Most DVS parameters are typically changed by adding lines to a
modprobe.d
configuration file or echoing values
to a
/proc
file. Changes to a
modprobe.d
file are made prior to booting the affected nodes, and the changes
take effect at boot.
The
dvs.conf
file is one of many files that are generated automatically and controlled by the Cray Configuration
Management Framework (CMF). Such files can be identified by the warning statement in the file header.
In the following example, DVS request logging is enabled on a node with a node ID of
nid00023
.
Cray DVS
S3016
162
