Running out of diskspace on boot drive(s)
I have a problem that I have not been able to find reported on any previous posts. I have Nexentastor community ed. v3.0.5 running on a machine that uses 2 x 60GB SSDs (mirrored) to run the OS and appliance software and then 10 x 1.5 TB Sata drives for the shared storage space. All was going well for a few months, then suddenly the system froze and when I rebooted, I get an "insufficient space on drive" (not exact text) that essentially is telling me that there is not enough space on the 60 GB OS drive for any of the Nexenta software components (nmv etc) and indeed, many of the OS services to start. I was able to log in as root (after telling it to start as the 32bit version and waiting for all the error messages to stop) and look around the drive. It seems that in a directory /var/lib/xapian-omega/data/BigNAS01-Data (BigNAS01 is the name of one of my shared appliance volumes) there are some enormous files. One is called position.DB, it is 38 GB in size and another is postlist.DB. there are other .DB files which are in the 1- 9B size range. Thats what filled up my drive. What are these files for, indexing? It looks to me as I will have to delete them, but I am worried as to what might happen to appliance function if I do that. I do not want to lose the stored data on the shared volumes. Thanks for any insight you can provide.
I have sent this question back to engineering to see if these files are coming from the appliance software.
So i got the response.
Yes, these files are for the Indexer feature. If they are filling up syspool completely, indexer needs to be disabled and the files removed.
If it is a feature the customer doesn’t use often, best solution is probably to not turn it on.
Thanks. I will try this today. I will have to delete the files first before I reboot the machine, then when the Nexenta appliance manager comes back on I will turn off indexing. Let you know what happens.