IMPORTANT NOTICE: This message and any attachments are solely for the
intended recipient and may contain confidential information which is, or
may be, legally privileged or otherwise protected by law from further
disclosure. If you are not the intended recipient, any disclosure,
copying, use, or distribution of the information included in this e-mail
and any attachments is prohibited. If you have received this
communication in error, please notify the sender by reply e-mail and
immediately and permanently delete this e-mail and any attachments.

Hi,
There are a few options.
1. Delete some files.
2. Add disk space to the file system.
3. Options 1 and 2 won't fix the problem. To remove the problem you will need to backup the file system. Remove the file system and recreate it with more Inodes.
Jim

Thank you very much for the responses to both Marcus and Jim. I did
the same and is fine now.

Thanks again for your time...

IMPORTANT NOTICE: This message and any attachments are solely for the
intended recipient and may contain confidential information which is, or
may be, legally privileged or otherwise protected by law from further
disclosure. If you are not the intended recipient, any disclosure,
copying, use, or distribution of the information included in this e-mail
and any attachments is prohibited. If you have received this
communication in error, please notify the sender by reply e-mail and
immediately and permanently delete this e-mail and any attachments.

Reorganizing a file system
This section provides steps for reorganizing a file system.

In the following example, a system has a separate logical volume and
file
system hd11 (mount point: /home/op). Because we decide that file system
hd11
needs to be reorganized, we do the following:

Back up the file system by file name. If you back up the file system by
i-node instead of by name, the restore command puts the files back in
their
original places, which would not solve the problem. Run the following
commands:
# cd /home/op
# find . -print | backup -ivf/tmp/op.backup
This command creates a backup file (in a different file system),
containing
all of the files in the file system that is to be reorganized. If disk
space
on the system is limited, you can use tape to back up the file system.

Run the following commands:
# cd /
# unmount /home/op
If any processes are using /home/op or any of its subdirectories, you
must
terminate those processes before the unmount command can complete
successfully.

Re-create the file system on the /home/op logical volume, as follows:
# mkfs /dev/hd11
You are prompted for confirmation before the old file system is
destroyed.
The name of the file system does not change.

To restore the original situation (except that /home/op is empty), run
the
following:
# mount /dev/hd11 /home/op
# cd /home/op
Restore the data, as follows:
# restore -xvf/tmp/op.backup >/dev/null
Standard output is redirected to /dev/null to avoid displaying the name
of
each of the files that were restored, which is time-consuming.

If you are using JFS you can't do anything else than erase some files.
JFS reserves a specific amount of space for inodes

Inodes are used on a file/directory assignment so if you have a lot of
files, inodes will be consumed quickly.

If you have JFS2, the inodes' space is dynamic, so it grows as it needs.
I think you can't do something, except define a new biggest filesystems
(maybe JFS2), and copy you filesystems data over the new one.

By deleting files as each file occupies 1 inode. Alternatevey you can increase the size of the filesystem which would give more inodes in JFS. If you are using JFS2 then dynamically they get created as and when required

Thank you very very much for the suggestions and guidance in inodes
matter. I really appreciate all your time personally to rbinkl, luis,
cdelgadop and priya...

Thanks again....

IMPORTANT NOTICE: This message and any attachments are solely for the
intended recipient and may contain confidential information which is, or
may be, legally privileged or otherwise protected by law from further
disclosure. If you are not the intended recipient, any disclosure,
copying, use, or distribution of the information included in this e-mail
and any attachments is prohibited. If you have received this
communication in error, please notify the sender by reply e-mail and
immediately and permanently delete this e-mail and any attachments.

Not necessarily, bot remember that inodes' space is taken from the same
space assigned for the filesystem, so if the filesystem is full, it also
can
take any space for creation of new inodes, but on the other hand with a
full
filesystem you can't create another file, so, why you should need more
inodes?.

It looks like you have the system filesystems setup to be jfs.
In this case you can delete files to get the inodes freed up.
You can increase the size of the filesystem by adding another logical part
ition which will give you more inodes.