[JENKINS-20193] disk usage plugin seems to scan /

Type: Bug
Resolution: Unresolved
Priority: Minor
Component/s: disk-usage-plugin
Labels:
None

Similar Issues:
Powered by SuggestiMate

Show

I would expect this plugin to only be looking at workspaces, not the root file system

Oct 22, 2013 12:24:08 PM hudson.plugins.disk_usage.DiskUsageUtil calculateWorkspaceDiskUsageForPath
WARNING: Disk usage fails to calculate workspace for file path / through channel hudson.remoting.LocalChannel@13f83e3b
java.util.concurrent.TimeoutException
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:258)
        at java.util.concurrent.FutureTask.get(FutureTask.java:119)
        at hudson.remoting.LocalChannel$2.get(LocalChannel.java:81)
        at hudson.plugins.disk_usage.DiskUsageUtil.calculateWorkspaceDiskUsageForPath(DiskUsageUtil.java:294)
        at hudson.plugins.disk_usage.DiskUsageUtil.calculateWorkspaceDiskUsage(DiskUsageUtil.java:349)
        at hudson.plugins.disk_usage.WorkspaceDiskUsageCalculationThread.execute(WorkspaceDiskUsageCalculationThread.java:46)
        at hudson.model.AsyncAperiodicWork$1.run(AsyncAperiodicWork.java:76)
        at java.lang.Thread.run(Thread.java:722)

INFO: Failed to list files in /proc/tty/driver - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/task/1/fd - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/task/1/fdinfo - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/fd - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/fdinfo - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/tty/driver - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/task/1/fd - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/task/1/fdinfo - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/tty/driver - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/fd - ignoring
Oct 22, 2013 1:20:26 PM hudson.plugins.disk_usage.DiskUsageUtil getFileSize
INFO: Failed to list files in /proc/1/fdinfo - ignoring

Lucie Votypkova added a comment - 2013-10-23 07:54

Hi, yes it should. But it really does not seem like a workspace of slave or workspace of job. I had disku usage on our test jenkins for 1 month and this was not happen to me. Is there any info about workspace in log? Maybe I will add the posibility of extended log. There must be something wrong .... it controls the workspaces which is in JobProperty (in for cycle). After each build the buildListener add into JobProperty information about path to the workspace and slave name (if there is duplicity it rewrites old information). So there should not be workspace with path / if this path was not set for some build (with custom workspace). To be sure - can you check if no build has workspace with path /? or better do you have installed Job config history plugin? There should be information about setting of custom workspace.

Lucie Votypkova added a comment - 2013-10-23 07:54 Hi, yes it should. But it really does not seem like a workspace of slave or workspace of job. I had disku usage on our test jenkins for 1 month and this was not happen to me. Is there any info about workspace in log? Maybe I will add the posibility of extended log. There must be something wrong .... it controls the workspaces which is in JobProperty (in for cycle). After each build the buildListener add into JobProperty information about path to the workspace and slave name (if there is duplicity it rewrites old information). So there should not be workspace with path / if this path was not set for some build (with custom workspace). To be sure - can you check if no build has workspace with path /? or better do you have installed Job config history plugin? There should be information about setting of custom workspace.

Lucie Votypkova added a comment - 2013-10-28 18:43

*should not - sorry I rewrote the sentence.

Lucie Votypkova added a comment - 2013-10-28 18:43 *should not - sorry I rewrote the sentence.

Croesus Kall added a comment - 2013-11-22 09:56

I am encountering this problem also.

Searching through job config files, I see that a great many of them have "/" set as the path. But this only applies to "modules" i.e. the config.xml files that apply to module builds.

In addition, this also only applies to very old jobs, that used to run on a slave that no longer exists.

Croesus Kall added a comment - 2013-11-22 09:56 I am encountering this problem also. Searching through job config files, I see that a great many of them have "/" set as the path. But this only applies to "modules" i.e. the config.xml files that apply to module builds. In addition, this also only applies to very old jobs, that used to run on a slave that no longer exists.

Lucie Votypkova added a comment - 2013-11-25 08:45

Disk usage controls the modules too, so it could be this reason, please can send me all build.xml files on my e-mail lvotypko@redhat.com?. I can clearly check what is wrong. I think that it was really caused by custom workspace. I think that disk usage should separate custom workspaces from ordinary workspaces.

Lucie Votypkova added a comment - 2013-11-25 08:45 Disk usage controls the modules too, so it could be this reason, please can send me all build.xml files on my e-mail lvotypko@redhat.com?. I can clearly check what is wrong. I think that it was really caused by custom workspace. I think that disk usage should separate custom workspaces from ordinary workspaces.

Jenkins

Details

Description

Attachments

Activity

Collapse comment: Lucie Votypkova added a comment - 2013-10-23 07:54

Expand comment: Lucie Votypkova added a comment - 2013-10-23 07:54

Collapse comment: Lucie Votypkova added a comment - 2013-10-28 18:43

Expand comment: Lucie Votypkova added a comment - 2013-10-28 18:43

Collapse comment: Croesus Kall added a comment - 2013-11-22 09:56

Expand comment: Croesus Kall added a comment - 2013-11-22 09:56

Collapse comment: Lucie Votypkova added a comment - 2013-11-25 08:45

Expand comment: Lucie Votypkova added a comment - 2013-11-25 08:45

People

Dates