test

Solaris Common Messages and Troubleshooting Guide

"N"

Name not unique on network

Cause

Given log name not unique.

Technical Notes

The symbolic name for this error is ENOTUNIQ, errno=80.

named [pid]: hostname.domainname has CNAME and other data (illegal)

Cause

On the DNS server, the error message is displayed.

Action

This error indicates that an alias (CNAME) is associated with another type of DNS record.

The DNS system allow you to set up an alias to a system using the CNAME record. An example of this is: 


alias1		IN CNAME	host1.domain1.

The alias alias1 cannot appear in any other type of record. Only the actual name of the host may be used. So, if you wanted to use this host as a mail exhanger, the record: 


alias1		IN MX  10  host2.domain1.
would be illegal and would produce the error.

Instead, you should use 


host1		IN MX  10  host2.domain1.
This goes for all types of records, including HINFO and A records.

Also, it is possible to get this error without explicitly setting the left hand side of a record. The DNS system defaults the left hand side to the last given left hand side. So you might have the following in a named database file: 


host1	IN A	 123.124.125.126
        IN HINFO Sun Solaris
alias1  IN CNAME host1.domain1.
        IN MX 10 host2.domain1.
In this fragment, there is an implied alias1 in the left hand side of the MX record. If the alias was added after the database was in use for a while, the error would suddenly start showing up. Since the MX record was legal until the CNAME was added in front of it. This example could be fixed either by reversing the order of the MX and CNAME records, or explicitly giving the host1 in the lefthand side of the MX record.

/net/string: No such file or directory

Cause

A user tried to change directory (for example with cd(1)) to a network partition on the system specified after /net/, but this host either does not exist or has not shared (exported) any filesystem.

Action

To gain access to files on this system, try rlogin(1).

To export filesystems from the remote system, become superuser on that system and run the share(1M) command with the appropriate options. If that system is sharing filesystems for the first time, also run /etc/init.d/nfs.server start to begin NFS service.

Network dropped connection because of reset

Cause

The host you were connected to crashed and rebooted.

Technical Notes

The symbolic name for this error is ENETRESET, errno=129.

Network is down

Cause

A transport connection failed because it encountered a dead network.

Action

Report this error to the system administrator for the network. If you are the person responsible for this network, check to see why the network is dead and what repairs are necessary.

Technical Notes

This error results from status information delivered by the underlying communication interface.

The symbolic name for this error is ENETDOWN, errno=127.

Network is unreachable

Cause

An operational error occurred either because there was no route to the network or because negative status information was returned by intermediate gateways or switching nodes.

The returned status is not always sufficient to distinguish between a network that is down and a host that is down. See the "No route to host" message.

Action

Check the network routers and switches to see if they are disallowing these packet transfers. If they are allowing all packet transfers, check network cabling and connections.

Technical Notes

The symbolic name for this error is ENETUNREACH, errno=128.

NFS getattr failed for server string: RPC: Timed out

Cause

This message appears on an NFS client that requested a service from an NFS server whose hardware is failing. Often the message "NFS read failed" appears along with this message. If the server were merely down or slow to respond, the "NFS server not responding" message would appear instead. Data corruption on the server system is possible.

Action

Because this message usually indicates server hardware failure, initiate repair procedures as soon as possible. Check the memory modules, disk controllers, and CPU board.

See Also

For more information on NFS tuning, see chapter on monitoring network performance in the System Administration Guide, Volume II.

nfs mount: Couldn't bind to reserved port

Cause

This message appears when a client attempts to NFS mount a filesystem from a server that has more than one Ethernet interface configured on the same physical subnet.

Action

Always connect multiple Ethernet interfaces on one router system to different physical subnetworks.

NFS mounted callog file Unsupported.

Cause

After installing Solaris 2.6 on a system, when users try to bring up their calendars either with CDE's calendar manager (/usr/dt/bin/dtcm) or OpenWindow's calendar (/usr/openwin/bin/cm), they see the dialog box: 


Calendar :Informational - NFS mounted callog file Unsupported.
Your default startup Calendar file appears to be NFS mounted or
a symlink to the same.  This is Not Supported.
			Continue
The following error is displayed in the console window when the Continue button is clicked: 

date time host rpc.cmsd[pid]: rpc.cmsd : 
	NFS mounted callog file Not Supported - user@host
date time host rpc.cmsd[pid]: rpc.cmsd : 
	NFS mounted callog file Not Supported - user@host
The calendars would've worked under 2.5.1 or before however.

Action

It has long been known that NFS mounted calendars are not supported in Solaris. Of the calendar can be corrupted when more than one person uses the calendar at the same time. If two rpc.cmsd daemons write to the callog file at the same time, the file becomes corrupt. However, two rpc.cmsd daemons could be run simultaneously through Solaris 2.5.1 even though this isn't a supported configuration.

With Solaris 2.6, this is no longer an option. rpc.cmsd does not allow the user to bring up a calendar that is NFS mounted and produces the error message above.

nfs mount: mount: string: Device busy

Cause

This message appears when the superuser attempts to NFS mount on top of an active directory. The busy device is actually the working directory of a process.

Action

Determine which shell on the workstation is currently located below the mount point, and change out of that directory. Be wary of subshells (such as su(1M) shells) that could be in different working directories while the parents remain below the mount point.

NFS mount: /string mounted OK

Cause

While booting, the system failed to mount the directory specified after the first colon, probably because the NFS server involved was down or slow to respond. The mount ran in the background and successfully contacted the NFS server.

Action

This is a purely informative message to let you know that the mount process has completed.

NFS read failed for server string

Cause

This is generally a permissions problem. Perhaps a directory or file permission was changed while the client held the file open. Perhaps the filesystem's share or netgroup permissions changed. If the server were down or the network saturated, the "NFS server not responding" message would appear instead.

Action

Log in to the NFS server and check the permissions of directories leading to the file. Make certain that the filesystem is shared with (exported to) the client experiencing an NFS read failure.

See Also

For more information, see the chapter on NFS troubleshooting in the NFS Administration Guide.

nfs_server: bad getargs for int/int

Cause

This message comes from the NFS server when it recieves a request with unrecognized or incorrect arguments. Typically, it means the request could not be XDR decoded properly. This can result from corruption of the packet over the network, or from an implementation bug causing the NFS client to improperly encode its arguments.

Action

If this message originates from a single client, investigate that machine for NFS client software bugs. If this message appears throughout a network, especially accompanied by other networking errors, investigate the network cabling and connectors.

NFS server string not responding still trying

Cause

In most cases this very common message indicates that the system has requested a service from an NFS server that is either down or extremely slow to respond. In some cases this message indicates that the network link to this NFS server is broken, although usually that condition generates other error messages as well. In a few cases this message indicates NFS client set-up problems.

Action

Check the non-responding NFS server to see whether the machine needs repair or rebooting. Encourage your user community to report such problems quickly but only once.

Should this message appear when booting a diskless client, make sure that the client's /etc/hosts file and the network naming service (NIS, NIS+, or other /etc/hosts files on the network) have been updated.

See Also

For more information, see the chapter on NFS troubleshooting in the NFS Administration Guide.

NFS server string ok

Cause

This message is the follow-up to the "NFS server not responding" error. It indicates that the NFS server is back in operation.

Action

When an NFS server first comes up, it is busy fulfilling client requests for a while. Be patient and wait for your client system to respond. Making many extraneous requests only further slows the NFS server response time.

NFS string failed for server string: error int (string)

Cause

The failed NFS operation could be any one of the following: getattr, setattr, lookup, access, readlink, read, write, create, mkdir, symlink, mknod, remove, rmdir, rename, link, readdir, readdir+, fsstat, fsinfo, pathconf, or commit.

See Also

For more information on NFS, see the NFS Administration Guide.

nfs umount: string: is busy

Cause

This message appears when the superuser attempts to unmount an active NFS filesystem. The busy point is the working directory of a process.

Action

Determine which shell (or process) on the workstation is currently located in the remotely mounted filesystem, and change (cd(1)) out of that directory. Be wary of subshells (such as su(1M) shells) that could be in different directories while the parent shells remain in the NFS filesystem.

NFS write error on host string: No space left on device.

Cause

This console message indicates that an NFS-mounted partition has filled up and cannot accept writing of new data. Unfortunately, software that attempts to overwrite existing files will usually zero out all data in these files. This is particularly destructive on NFS-mounted /home partitions.

Action

Find the user or process that is filling up the filesystem, and stop the out-of-control process as soon as you can. Then delete files as necessary to create more space on the filesystem (large core(4) files are good candidates for deletion). Have users write any modified files to local disk if possible. If this error occurs often, redistribute directories to ease demand on this partition.

See Also

For more information on disk usage, see the System Administration Guide, Volume II. If you are using the AnswerBook, "managing disk use" is a good search string.

NFS write failed for server string: RPC: Timed out

Cause

This error can occur when a file system is soft-mounted, and server or network response time lags. Any data written to the server during this period could be corrupted.

Action

If you intend to write on a filesystem, never specify the soft mount option. Use the default hard mount for all the filesystems that are mounted read-write.

See Also

For more information, see the chapter on NFS troubleshooting in the NFS Administration Guide.

NIS+ authentication failure

Cause

This is a Federated Naming Service message. The operation could not be completed because the principal making the request could not be authenticated with the name service involved.

Action

Run the nisdefaults(1) command to verify that you are identified as the correct NIS+ principal. Also check that the system has specified the correct public key source.

See Also

For more information, see the authentication and authorization overview in the NIS+ and FNS Administration Guide.

nis_cachemgr: Error in reading NIS cold start file : '/var/nis/NIS_COLD_START'

Cause

After installing patches 104331-04 and 103612-33, nis_cachemgr(1M) failed to come up. The symptoms are as follows during the reboot: 


Sep 11 16:34:00 nis_cachemgr: Error in reading NIS cold start file : 
          '/var/nis/NIS_COLD_START'
and nis_cachemgr(1M) isn't there after logging in. Trussing nis_cachemgr(1M) showed that it is reading /var/nis/NIS_COLD_START and immediately reporting an error. Neither reinitializing the client nor copying NIS_COLD_START helps.

Action

This is a timing problem. Put a sleep(1) before the NIS+ initialization in /etc/init.d/rpc, after rpc.bind has been started. rpc.bind is slow about initializing and needs a few extra seconds to get going before nis_cachemgr(1M) starts bugging it.

No buffer space available

Cause

An operation on a transport endpoint or pipe was not performed because the system lacked sufficient buffer space or because a queue was full. The target system probably ran out of memory or swap space. Any data written during this condition will probably be lost.

Action

To add more swap area, use the swap -a command on the target system. Alternatively, reconfigure the target system to have more swap space. As a general rule, swap space should be two to three times as large as physical memory.

Technical Notes

The symbolic name for this error is ENOBUFS, errno=132.

No child processes

Cause

This message can appear when an application tries to communicate with cooperating process that do not exist.

Action

Restart the parent process so it can create the child processes again. If that doesn't help, this could be the result of a programming error; contact the vendor or author of the program for an update.

Technical Notes

A wait(2) system call was executed by a process that had no existing or unwaited-for child processes. The child processes could have exited prematurely, or might never have been created.

The symbolic name for this error is ECHILD, errno=10.

No default media available

Cause

The volume manager issues this message if a user makes an eject(1) request when the drives contain no diskette or CD-ROM to eject.

Action

Insert a diskette or CD-ROM. If the volume manager is confused and there actually is a diskette or CD-ROM in a drive, run volcheck(1) to update the volume manager. If the system remains confused, try booting with the -r option to reconfigure devices.

No directory! Logging in with home=/

Cause

The login(1) program could not find the home directory listed in the password file or NIS passwd(4) map, so it deposited the user in the root directory.

Action

Check that the user's home directory is mounted and is owned by and accessible to that user. Perhaps the automounter tried to mount the home directory, but the NFS server did not respond quickly enough. Try listing the files in /home/username. If the NFS server responds to this request, have the user log out and log in again.

It is possible that the automounter daemon is not running. Run the ps(1) command to see if automountd(1M) is present. If not, run the second command; if it appears to be wedged, run both these commands: 


# /etc/init.d/autofs stop
# /etc/init.d/autofs start
When the automounter daemon is running, verify that the /etc/auto_master file has a line like this: 

/home  auto_home
Verify that the /etc/auto_home file has a line like this: 

+auto_home
These entries depend on the NIS auto_home map.

It is also possible that the NFS server has not shared (exported) this /home directory, or that the NFS daemons on the server have disappeared.

See Also

For more information on NFS, see the NFS Administration Guide.

No message of desired type

Cause

An attempt was made to receive a message of a type that does not exist on the specified message queue. See the msgsnd(2) and msgrcv(2) man pages for details.

Action

This indicates an error in the System V IPC message facility. Generally the message queue is empty or devoid of the desired message type, while IPC_NOWAIT is set.

Technical Notes

The symbolic name for this error is ENOMSG, errno=35.

No recipients specified

Cause

This message comes from the mailx(1) command whenever a user doesn't provide an address in the To: field.

Action

See the message "Recipient names must be specified" for details.

No record locks available

Cause

No more record locks are available. The system lock table is full.

Technical Notes

The symbolic name for this error is ENOLCK, errno=46.

Perhaps a process called fcntl(2) with the F_SETLK or F_SETLKW option, and the system maximum was exceeded. The system contains several different locking subsystems, including fcntl(2), the NFS lock daemon, and mail locking, all of which can produce this error.

Action

Try again later, when more locks might be available.

No route to host

Cause

An operational error occurred because there was no route to the destination host, or because of status information returned by intermediate gateways or switching nodes.

The returned status is not always sufficient to distinguish between a host that is down and a network that is down. See the "Network is unreachable" message.

Action

Check the network routers and switches to see if they are disallowing these packet transfers. If they are allowing all packet transfers, check network cabling and connections.

Technical Notes

The symbolic name for this error is EHOSTUNREACH, errno=148.

No shell Connection closed

Cause

A user has attempted to a remote login to the system, and has a valid account name and password, but the shell specified for their account is not available on that system. For example, the seventh field could request the GNU Bourne-again shell /bin/bash, which does not exist on standard Solaris distributions.

Action

If you have a copy of the requested shell, become superuser and install the missing shell on that system. Otherwise, change the user's password file entry (perhaps only in the NIS+ or NIS passwd(4) map) to specify an available shell such as /bin/csh or /bin/ksh.

No space left on device

Cause

While writing an ordinary file or creating a directory entry, there was no free space left on the device. The disk, tape, or diskette is full of data. Any data written to that device during this condition will be lost.

Action

Remove unneeded files from the hard disk or diskette until there is space for all the data you are writing. It might be advisable to move some directories onto another filesystem and create symbolic links accordingly. When a tape is full, continue on another one, use a higher density setting, or obtain a higher-capacity tape.

To create multi-volume tapes or diskettes, use the pax(1) or cpio(1) command; tar(1) is still limited to a single volume.

Technical Notes

The symbolic name for this error is ENOSPC, errno=28.

No such device

Cause

An attempt was made to apply an operation to an inappropriate device, such as writing to a nonexistent device.

Action

Look in the /devices directory to see why this device does not exist, or why the program expects it to exist. The similar "No such device or address" message tends to indicate I/O problems with an existing device, whereas this message tends to indicate a device that does not exist at all.

Technical Notes

The symbolic name for this error is ENODEV, errno=19.

No such device or address

Cause

This error can occur when a tape drive is off-line or when a device has been powered off or removed from the system.

Action

For tape drives, make sure the device is connected, powered on, and toggled online (if applicable). For disk and CD-ROM drives, check that the device is connected and powered on.

With all SCSI devices, ensure that the target switch or dial is set to the number where the system originally mounted it. To inform the system of a change to the target device number, reboot using the -r (reconfigure) option.

Technical Notes

This message results from I/O to a special file's subdevice that either does not exist or that exists beyond the limit of the device.

The symbolic name for this error is ENXIO, errno=6.

No such file or directory

Cause

The specified file or directory does not exist. Either the file name or path name was entered incorrectly.

Action

Check the file name and path name for correctness and try again. If the specified file or directory is a symbolic link, it probably points to a nonexistent file or directory.

Technical Notes

The symbolic name for this error is ENOENT, errno=2.

no such map in server's domain

Cause

A user or an application tried to look up something using Network Information Services (NIS), but NIS has no corresponding database for this request.

Action

Make sure the NIS map name is spelled correctly. To see a list of nicknames for the various NIS maps, run the ypcat -x command. To see a full list of the various NIS maps (databases), run the ypwhich -m command. If the NIS service were not running on the current machine, these commands would result in a "can't communicate with ypbind" message.

No such process

Cause

This process cannot be found. The process could have finished execution and disappeared, or it might still be in the system under a different numeric ID.

Action

Use the ps(1) command to check that the process ID you're supplying is correct.

Technical Notes

No process corresponds to the specified process ID (PID), light-weight process ID, or thread_t.

The symbolic name for this error is ESRCH, errno=3.

No such user as string-- cron entries not created

Cause

A file exists in /var/spool/cron/crontabs for the specified user, but this user is not in /etc/passwd or the NIS passwd(4) map. The system cannot create cron(1M) entries for nonexistent users.

Action

To eliminate this message at boot time, remove the cron file for the nonexistent user, or rename it if the user's login name has changed. If this is a valid user, create an appropriate password entry for this name.

Not a data message

Cause

During a read(2), getmsg(2), or ioctl(2) I_RECVFD call to a STREAMS device, something has come to the head of the queue that can't be processed. That something depends on the call: 1. read(2): control information or passed file descriptor; 2. getmsg(2): passed file descriptor; 3. ioctl(2): control or data information.

Technical Notes

The symbolic name for this error is EBADMSG, errno=77.

Not a directory

Cause

A non-directory was specified where a directory is required, such as in a path prefix or as an argument to the chdir(2) call.

Action

Look at a listing of all the files in the current directory and try again, specifying a directory instead of a file.

Technical Notes

The symbolic name for this error is ENOTDIR, errno=20.

Not a stream device

Cause

A putmsg(2) or getmsg(2) system call was attempted on a file descriptor that is not a STREAMS device.

Technical Notes

The symbolic name for this error is ENOSTR, errno=60.

Not enough space

Cause

This message indicates that the system is running many large applications simultaneously, and has run out of swap space (virtual memory). It could also indicate that applications failed without freeing pages from the swap area. Swap space is an area of disk set aside to store portions of applications and data not immediately required in memory. Any data written during this condition will probably be lost.

Action

Reinstall or reconfigure the system to have more swap space. A general rule of thumb is that swap space should be two to three times as large as physical memory. Alternatively, use mkfile(1M) and swap(1M) to add more swap area. This example shows how to add 16 MB of virtual memory in the /usr/swap file (any filesystem with enough free space would work): 


# mkfile 16m /usr/swap
# swap -a /usr/swap
To make this automatic at boot time, add the following line to the /etc/vfstab file: 

/usr/swap   -   -   swap   -   no   -

Technical Notes

In calling the fork(2), exec(2), sbrk(2), or malloc(3C) routine, a program asked for more memory than the system could supply. This is not a temporary condition; swap space is a system parameter.

The symbolic name for this error is ENOMEM, errno=12.

not found

Cause

This message indicates that the Bourne shell could not find the program name given as a command.

Action

Check the form and spelling of the command line. If that looks correct, echo $PATH to see if the user's search path is correct. When communications are garbled, it is possible to unset a search path to such an extent that only built-in shell commands are available. Here is a command to reset a basic search path: 


$ PATH=/usr/bin:/usr/ccs/bin:/usr/openwin/bin:.
If the search path looks correct, check the directory contents along the search path to see if programs are missing or if directories are not mounted.

NOTICE: vxvm: unexpected status on close

Cause

Everytime system boots (or is shut down), the message is displayed on the console. Sometimes, the following message is also displayed on the console and in the /var/adm/messages file: 

	WARNING:
/iommu@0,10000000/sbus@0,10001000/SUNW,soc@2,0/SUNW,pln@a0000000,74127a/ssd@4,2
(ssd22):
	Error for Command: <undecoded cmd 0x35>       Error Level: Fatal
	Requested Block: 0      Error Block: 0
	Vendor: CONNER                  Serial Number: 93081LPT
	Sense Key: Aborted Command
	ASC: 0xb3 (<vendor unique code 0xb3>), ASCQ: 0x0, FRU: 0x0
	WARNING:
/iommu@0,10000000/sbus@0,10001000/SUNW,soc@2,0/SUNW,pln@a0000000,74127a/ssd@4,2
(ssd22): ssd_synchronize_cache failed (5)

Action

In a High Availability system with NVRAM, this would be caused by unprocessed data in a NVRAM cache of the active logical host that has been down and come up later. Because of this, NVRAM should not be used in an HA system. The problem can be solved in this case by getting rid of the NVRAM on the HA system.

In a non-HA system, this can also be caused by stale data in the NVRAM cache. (The example commands below assume the controller for the array is c1.) To fix for a non-HA system:

1. Turn off all fast writes on this array and sync any remaining pending writes. 


# ssaadm fast_write -d c1
# ssaadm sync_cache c1

2. When you sync the fast writes to the array, all pending writes are physically made to the disks. Anything that is left in the cache is stale, and thus, it is safe to purge it. Run the command: 


# ssaadm purge c1

3. Turn the fast writes for the disks back on. This command MAY be different on your system, depending on the disks on which you want fast writes enabled and the types of fast writes you want: 


# ssaadm fast_write -s -e c1

NOTICE: /string: out of inodes

Cause

The filesystem specified after the first colon probably contains many small files, exceeding the per-filesystem limit for inodes (file information nodes).

Action

If many small files were created unintentionally, removing them resolves the problem.

Otherwise, follow these steps to increase filesystem capacity for small files. Make several backup copies of the filesystem on different tapes (for safety), then bring the machine down to single-user mode. Use the newfs(1M) command with the -i option to increase inode density for this filesystem. Here is an example: 


# newfs -i 1024 /dev/rdsk/partition
Finally, restore the filesystem from a backup tape. Note that increasing the inode density slightly reduces total filesystem capacity.

Not login shell

Cause

This message results when a user tries to logout(1) from a shell other than the one started at login time.

Action

To quit a non-login shell, use the exit(1) command. Continue doing so until you have logged out.

See Also

For more general information on the login shell, see the section on customizing your work environment in the Solaris Advanced User's Guide.

Not on system console

Cause

A user tried to login(1) to a system as the superuser (uid=0, which is not necessarily root) from a terminal other than the console.

Action

Login to that system as a normal user, then run su(1M) to become superuser. To allow superuser logins from any terminal, comment out the CONSOLE line in /etc/default/login (this is not recommended for security reasons).

Not owner

Cause

Either an ordinary user tried to do something reserved for the superuser, or the user tried to modify a file in a way restricted to the file's owner or to the superuser.

Action

Switch user to root and try again.

Technical Notes

The symbolic name for this error is EPERM, errno=1.

Not supported

Cause

This version of the system does not support the feature requested, although future versions of the system might provide support.

Action

This is generally not a system message from the kernel, but an error returned by an application. Contact the vendor or author of the application for an update.

Technical Notes

The symbolic name for this error is ENOTSUP, errno=48.

No utmpx entry

Cause

During login file system full errors are seen and login fails with the message No utmpx entry.

This is caused by a full file system so that the system has no space to write its utmpx (login info) entry.

Action

To get around this condition the system must be booted into single user mode. Then clear (do not delete) the files: /var/adm/utmp and /var/adm/utmpx. This can be done by typing: 


#cat /dev/null > /var/adm/utmp
#cat /dev/null > /var/adm/utmpx
These commands zero out the files but keep it with the correct permissions.

In some cases after clearing these files the /var filesystem may still be full. In this case type: 


du -askd /var |sort -nr |more
This will give you a listing of the files from largest to smallest in the /var filesystem. To create space you can zero the files: /var/cron/log, /var/spool/lp/logs, and /var/adm/messages. You can also check /.wastebasket for large files to delete.

6/04/98 7:27:54 nsrck: SYSTEM error, more space needed to compress [client] index, 8.1 MB required

Cause

In networker, cannot use the Remove Oldest Cycle feature because the /nsr filesystem is too full to perform a remove. An error message appears in the console window indicating that the file system is full.

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.