2 Replies Latest reply on Sep 22, 2014 12:57 PM by familyofcrowes

    diskusage stats

    familyofcrowes

      Why does disk usage stats say only 50% for Logs/Data (via diskusage command) but it is not retaining the logs older then 2 months?

       

      Am I missing something?

      Partition Disk Usage:

              LEM:             43% (1.2G/3.0G)

              OS:              39% (1.1G/3.0G)

              Logs/Data:       50% (232G/492G)

              Temp:             5% (230M/5.9G)

      Database Queue(s): 12K (No alerts queued, 21937 alerts waiting in memory)

      Rules Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)

      Console Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)

      DataCenter Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)

      EPIC Rules Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)

      Logs: 26G

        • Re: diskusage stats
          nicole pauls

          Very interesting. That's a big gap.

           

          There is some reserved space (5% of disk I think, to the OS) so the numbers don't always match up exactly, but 40% off is way off. Does it differ depending on what time of day you run it by chance?

           

          A debug should have in it information about partition rotation and related checks in the manager.log. It should log when it's checking and whether it's found something to chop off. (I believe this is all at default levels, so you should see it without us increasing the debug level.) That info might tell us what's triggering.

           

          We did for a little while also have some partition drops mis-firing - but usually it was NOT firing, not firing extra. That was resolved sometime around 6.0, so it might have been added in to mainline in 6.0.1. I'd have to check, but hopefully the logs can provide more insight.

          1 of 1 people found this helpful