Environment
Novell eDirectory 8.7.3.7 for Solaris
Solaris
Solaris 8
Situation
The ndsd process had crashed.
When restarting ndsd, the error -153 Disk full was reported.
The partition on which the DIB resides has plently of space.
ulimit -f is set to "unlimited".
When restarting ndsd, the error -153 Disk full was reported.
The partition on which the DIB resides has plently of space.
ulimit -f is set to "unlimited".
Resolution
Looking a little more closely at the size of the NDS.01 (2147483647
bytes) file it was EXACTLY at the 2GB limit, since 2147483647
bytes == 0x7FFFFFFF, where 2GB == 0x800000000.
Investigating the Solaris configuration more closely, Solaris 8 requires the "largefiles" option be set on the mount point in order to create or access files >= 2GB, even when ulimit -f is set to"unlimited". This "largefiles" option was not currently set: on the /var/nds partition:
The root cause of the crash was therefore that the NDS dib file had reached the underlying 2GB limit imposed by the OS, and NDS was therefore unable to write further information into the database.
Customer added the largefiles option and remounted. The database could then be opened.
Investigating the Solaris configuration more closely, Solaris 8 requires the "largefiles" option be set on the mount point in order to create or access files >= 2GB, even when ulimit -f is set to"unlimited". This "largefiles" option was not currently set: on the /var/nds partition:
The root cause of the crash was therefore that the NDS dib file had reached the underlying 2GB limit imposed by the OS, and NDS was therefore unable to write further information into the database.
Customer added the largefiles option and remounted. The database could then be opened.