Unable to start the deployment manager due to (No space left on device).

The above error is seen in particular in the following two formats:

SystemErrR java.io.FileNotFoundException:  /websphere/profiles/Dmgr01/wstemp/common/XmlLocale.class (No space left on device)

SystemErr     R java.io.FileNotFoundException: /websphere/profiles/Dmgr01/wstemp/778788/prefs.xml (No such file or directory)

For the above two errors, You need to do the following preliminary check:

Step 1: df -kh /webspehre (or the filesystem on which the wstemp is mounted)

To check the filesystem usage. If the filesystem is 100%, Then clear the unwanted files and try restarting the server.

If, The file system is free and you still see the error, Move to the following step.

Step 2: Try creating a directory in the wstemp folder with any name and see if you are able to create a directory. Most probably you would be getting the following error.

[root@ wstemp]# mkdir test

mkdir: cannot create directory `test': No space left on device

Step 3: df -i /websphere

This must be listing 100% usage of inodes.

Filesystem             Inodes   IUsed    IFree IUse% Mounted on

/filesystem

                      2293760 2293757        3  100% /websphere

It is very rear to run out of inodes before the disk space is full.

For this you need to do a little manual work. Use the following command to check the number of files and directories for the particular file system.

for i in /*; do echo $i; find $i |wc -l; done

The directory with the highest number of files will probably the culprit. Move to that directory and execute the command again. Keep doing that until you are able to figure out the folder with max files and delete the ones that are not in use.

This will temporarily solve the issue. However, The permanent solution would be to check why the files are piling up. The inodes can be increased only during the filesystem creation, It can not be changed dynamically.