Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-8881

After Log Rolling, Pervious, Uncompressed Log File is Deleted But _Not_ Closed and its Disk Space Not Freed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • core
    • None
    • Linux, CentOS 5.5, kernel 2.6.18-194.el5; x86_64; Java 1.6.0_10-b33

      When Jenkins performs log-rolling, it compresses the completed log file leaving a date-stamped, ".gz"-suffixed equivalent while moving on to a new "jenkins.log" file. It also unlinks the old plain-text (non-compressed) log file. However, it does not close its descriptor to that log file and thus its disk space is not freed until Jenkins itself is restarted.

      On a Linux system, such ghost files can be discovered via entries in /proc/NNN/fd/*:

      1. ll /proc/[0-9][0-9]/fd |egrep '/var.(deleted)'

          [JENKINS-8881] After Log Rolling, Pervious, Uncompressed Log File is Deleted But _Not_ Closed and its Disk Space Not Freed

            abayer Andrew Bayer
            randallschulz Randall Schulz
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: