Alfresco Community 201606 Errors - help

g_rathod

I already check my community version and OS space, it is suffice but, still alfresco says below message

2016-11-30 04:32:02,532 INFO [management.subsystems.ChildApplicationContextFactory] [localhost-startStop-1] Startup of 'thirdparty' subsystem, ID: [thirdparty, default] complete
2016-11-30 04:32:02,532 INFO [management.subsystems.ChildApplicationContextFactory] [localhost-startStop-1] Starting 'OOoDirect' subsystem, ID: [OOoDirect, default]
2016-11-30 04:32:03,088 ERROR [alfresco.util.SocketOpenOfficeConnection] [MessageDispatcher] disconnected unexpectedly
2016-11-30 04:34:54,730 ERROR [solr.component.AsyncBuildSuggestComponent] [Suggestor-alfresco-1] Exception in reloading suggester index for: shingleBasedSuggestions
java.io.IOException: No space left on device
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:326)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.DataOutputStream.flush(DataOutputStream.java:123)
at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
at org.apache.lucene.util.OfflineSorter$ByteSequencesWriter.close(OfflineSorter.java:491)
at org.apache.lucene.util.IOUtils.close(IOUtils.java:77)

Here is my ALF node space proof  ( installed under /opt/alfresco) , solr is under /solr1_data  and  contentStore is under /GOA_Content

Here is my DB node space proof

Both of node having suffice space.  still alfresco throws error that "No space left on device"

Also transformation not working at all it stops after below line 

alfresco.util.SocketOpenOfficeConnection] [MessageDispatcher] disconnected unexpectedly

can't find any logs or reason why this happens.

Your help appreciated

afaust

Unfortunately the incorrect message is provided by the operating system / file system. When using SOLR4 in Alfresco 5 there is an issue with the amount of inodes being used in the file system. Basically SOLR 4 is causing large amounts of inodes to be used due to the new content caching functionality. If your file system is not configure for unlimited or large inode counts, you may run into the limit. At that point the operating system will report the device to be full, because no new files can be created due to lack of available inodes.

The solution to this is to either use file systems without inodes or configure your file system for small block sizes. Content cache files are compressed and take from a couple of hundred bytes to a few kilobytes only. So setting up a block size of 512 bytes may be the most efficient option.