Hp StorageWorks Scalable File Share Manual do Utilizador descarregar pdf (Página 127)

Deleting file systems 5–43

2. Stop all file systems, by entering the stop filesystem filesystem_name command for each

file system.

Do not proceed to the next step (defining the system nickname) until all file systems are stopped; a file

system is stopped when all of the file system services are in the stopped or down state. See

Section 3.7 for more information on the stop filesystem command.

3. Define the new system nickname by entering the command shown in the following example, where

the nickname attribute is created and its value is set to southfs:

sfs> set attribute nickname=southfs

4. Start the file system(s).

5. When file systems restart, client nodes can remount the file systems. If a client node fails to mount a

file system, reboot the client node.

When the file systems restart after they have been reconfigured, client nodes can mount the file systems

again. If a client node fails to mount a file system, reboot the client node.

5.10 Deleting file systems

To delete a file system, perform the following steps:

1. Back up the database, as follows:

# sfsmgr

sfs> create database_backup

2. Save the backup file to an external system, as shown in the following example, where the full name of

the backup file is /var/hpls.local/hplsdb_20040311-1041.tar.gz, the external system

host address is 16.123.123.1, and the account on the host is named fred:

# scp /var/hpls.local/hplsdb_200403011-1041.tar.gz \

3. Delete the file system by entering the command shown in the following example:

sfs> delete filesystem scratch

5.11 Managing space on OST services

When OST services run out of space, applications may get ENOSPC errors when they attempt to create or

write to files. Because OST services fill at different rates, an ENOSPC error may occur on an individual OST

service, even though the overall file system appears to have space available.

For this reason, the HP SFS system monitors the usage on OST services. You are warned in two ways when

an OST service is becoming full:

• The syscheck command prints messages when the usage on the OST service exceeds the warning

or critical level.

• An email alert is sent when the usage on the OST service exceeds the critical level.

In addition, there are log messages in the event log that record these events. No email alert is sent when

the usage on an OST service exceeds the warning level; however, you can create your own email alert for

this event; see Section 6.2 for information on creating email alerts.

When an OST service has been filled to a certain percentage, a warning or critical event occurs and a

message is sent to the event log. A default email alert is triggered when a critical out-of-space event occurs.

1 2 ... 122 123 124 125 126 127 128 129 130 131 132 ... 361 362

Sem comentários

Hp StorageWorks Scalable File Share Manual do Utilizador Página 127