Hp StorageWorks Scalable File Share Uživatelský manuál stáhnout pdf (Strana 254)

Troubleshooting9–30

9.26.8 Rebalancing file system services

Sometimes, file system services do not run on their preferred server. This happens after a temporary failure

of a server or storage component. During the initial failure, the service fails over to the backup server. When

you reboot the failed server, the services sometimes remain on the backup server; they do not automatically

relocate back to their usual (preferred) server. You can see this by examining the output from the show

server and show filesystem commands.

The following example shows one server (south4) running many OST services while the second server in

the server pair (south3) is idle:

sfs> show server

Name State Power Services

---------- -------------- -------- ----------

south1 running on admin

south2 running on mds1

south3 running on none

south4 running on ost1 ost2 ost3 ost4

You can use the show filesystem filesystem_name command to confirm this information, as shown

in the following example:

sfs> show filesystem data

Name LUN Array Controller Size(GB) Used Service State Running on

----- --- ----- ---------- -------- ---- ------------- ----------

ost1 31 2 scsi-1/1 1050 30% running south4!

ost2 32 2 scsi-1/2 1050 31% running south4

ost3 33 3 scsi-2/1 1050 29% running south4!

ost4 34 3 scsi-2/2 1050 30% running south4

(servers marked ! are not preferred server)

As you can see, the ost1 and ost3 services are not running on their preferred server—this is indicated by

an exclamation mark (!) beside the server name.

Use the show server server_name command to determine the peer server for server south4, and

then rebalance the OST services by performing the steps shown in the following example. In this example,

the ost1 and ost3 services are forced to run on the south3 server, which is the peer server for south4:

1. Shut down the south3 and south4 servers, as shown in the following example:

sfs> shutdown server south[3-4]

2. Boot the south3 and south4 servers, as shown in the following example:

sfs> boot server south[3-4]

To rebalance an MDS service (where the MDS service is running on the administration server), perform the

following steps. You do not need to stop the file system:

1. If the MDS server is not already running, boot the MDS server.

2. Shut down the administration server, as described in Section 3.6. The MDS service will fail over to

(that is, start running on) the MDS server. The administration service will also fail over to the MDS

server, so that there will be a delay before you can examine the state of the MDS services.

3. Boot the administration server, as shown in the following example:

sfs> boot server south1

1 2 ... 249 250 251 252 253 254 255 256 257 258 259 ... 361 362

Komentáře k této Příručce

Žádné komentáře

Hp StorageWorks Scalable File Share Uživatelský manuál Strana 254

Komentáře k této Příručce

Související produkty a manuály pro Úložný prostor Hp StorageWorks Scalable File Share