E.4 Deleting a Slave Server

Under DFS, if there is a hardware error or similar reason, slave servers, development servers and collaboration servers can be deleted without stopping operation.

The slave server, development servers and collaboration server deletion procedure is described below using the following environment as an example:

Logical file system name:	pdfs1
Mount point:	/mnt/pdfs
File system ID:	1
Master server:	master1, master2
Existing Slave server, development server, collaboration server:	slave1, slave2, slave3, slave4, slave5, develop, collaborate
Deletion target slave server:	slave6

If the DFS is mounted at the slave servers, development servers and collaboration servers targeted for deletion, unmount the DFS.
```
# umount pdfs1 <Enter>
```
Delete the file system configuration information file at the slave server, development servers or collaboration server targeted for deletion.
```
# cd /etc/pdfs <Enter>
# rm ./client.conf.pdfs1 <Enter>
```
Delete the DFS description from the /etc/fstab of the slave server, development server or collaboration server targeted for deletion.

From the master server (primary) connection authorization list file, delete the CLIENT fields of the slave server, development server or collaboration server targeted for deletion.

# cat /etc/sfcfs/server.conf.1 <Enter>
#
# Copyright (c) 2012 FUJITSU LIMITED. All rights reserved.
#
#   /etc/pdfs/server.conf.<FSID>
#
# List of client hostnames of a file system.
#
# Notes:
#   Do not describe hostnames of management servers.
#
# example:
#CLIENT nodeac1
#CLIENT nodeac2
#CLIENT nodeac3
#CLIENT nodeac4
#CLIENT nodeac5
CLIENT slave1
CLIENT slave2
CLIENT slave3
CLIENT slave4
CLIENT slave5
CLIENT develop
CLIENT collaborate
CLIENT slave6     <-- Delete the row here.
CLIENT slave7
CLIENT slave8
CLIENT slave9
CLIENT slave10

Distribute the updated connection authorization list file to the master servers.
Example: If executing from the master server (primary) master1:
```
# cd /etc/pdfs <Enter>
# scp -p ./server.conf.pdfs1 root@master2:/etc/pdfs/server.conf.pdfs1 <Enter>
```

Note

If the connection authorization list file contents differ at different master servers, MDS down recovery might fail and file system inhibition or system panic might occur.