You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Steve Rowe (JIRA)" <ji...@apache.org> on 2016/04/25 22:08:12 UTC

[jira] [Created] (INFRA-11743) Increase disk space allocated for Jenkins workspaces on lucene1-us-west

Steve Rowe created INFRA-11743:
----------------------------------

             Summary: Increase disk space allocated for Jenkins workspaces on lucene1-us-west
                 Key: INFRA-11743
                 URL: https://issues.apache.org/jira/browse/INFRA-11743
             Project: Infrastructure
          Issue Type: Task
          Components: Jenkins, Zones/Jails
            Reporter: Steve Rowe


The Lucene project requests that the disk space available for Jenkins workspaces on lucene1-us-west be increased, by at least 50%: 79GB -> 120GB.

The Lucene project runs Jenkins builds on lucene1-us-west.apache.org (see INFRA-9096), but we've run out of disk space a couple times in recent history, because the number of branches we build against is increasing.

Here's the situation on /x1, where Jenkins workspaces are:

  $ df -k /home/jenkins/jenkins-slave/workspace/
  Filesystem     1K-blocks     Used Available Use% Mounted on
  /dev/sdb1       82437808 66355440  11871732  85% /x1

Right now when we run out of disk space, we can wipe the workspaces for branches that don't have a pending release (I did that today), but I expect this strategy to fail in the near term, as we'll very likely have more simultaneously active release branches to test (along with the stable and unstable branches we always build against).

Probably the strategy that would cause the least downtime would be to resize the underlaying VM virtual disk and then resize the file system afterwards.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)