That is the reason why I report this situation. I am trying to investigate
whether this may caused by ES or not. We come across this situation twice in
our production ES cluster. ES gave an exception about disk space previously.
When we checked file system we saw that df and du give different values. We
restarted servers and our data is corrupted because of this. We restarted
them and repopulated whole data again and after nearly two months later same
situation appeared again. We use ES version 0.15.2. When I searched about
this problem, I saw that other lucene based products face with same problem
if any IndexReader is not closed. may this be a problem in ES too?
On Mon, Apr 25, 2011 at 7:48 PM, Joaquin Cuenca Abela <
df shows disk space usage on your volume, du disk used by the list
that it can access. The remaining 30% is in files that du is not
seeing. Assuming there are no obvious mistakes, this usually comes
from big files that have been deleted from the file system but that
are still mapped by some process. For instance, maybe you deleted a
big log file, but forgot to restart / reload the server that created
this log file.
On Mon, Apr 25, 2011 at 5:24 PM, Mustafa Sener firstname.lastname@example.org
In one of our production clusters we saw that there is a big difference
between df and du disk size reports. df shows 100% and du shows as 70%.
remains as it is while cluster is running. Do you have any ideas about
reason of this problem?
Joaquin Cuenca Abela -- presspeople.com: Fuentes de prensa y comunicados