Action

1. Stop the networker daemons so that some of the indices can be moved. In SunOS 5, use /etc/init.d/networker stop. In SunOS 4, use ps -ef | grep nsr and kill(1) the processes.

2. Find a filesystem with enough space to move one of the client's indices. Only one of the client's indices should be moved, not the networker server's index. To find the size of a client's index, go to /nsr/index/client name/db and list the contents using ls -l. The data base file can be very large (possibly over 500 MB).

3. Move the contents of a client's index to the other filesystem and check that /nsr has freed the space to use. It may be necessary to unmount and remount /nsr, or even to reboot to designate the space freed by the move as available.

4. Once the space is available, restart the daemons.

5. Go into nwadmin. Under Clients--Indexes, select a client and use Remove Oldest Cycle to free more space.

Use Reclaim Space to reclaim the space from the removed cycles. After a few of the old cycles have been removed, there should be enough space in the filesystem to move the removed client's index back.

6. Stop the daemons, and move the client's index back to /nsr/index/clientname.

7. Restart the daemons. Remove oldest cycles for the client that was just moved.

Tweaking of the browse policy and retention policy may be necessary to prevent this situation from happening in the future.

Other, long term solutions are to add more hard disk and run growfs or move /nsr to a drive with more space on it.