JobDiskFreeLimited while pushing package on AIX

system · October 2, 2011, 6:40am

(imported topic written by SebRaby)

Hi all

I have created a package using the “AIX Fileset Deployment Wizard” but I keep getting the JobDiskFreeLimited in the agent log as detailed during the download phase.

DownloadsAvailable: checking for ‘http://BIGFIX.novipro-mtl.local:52311/bfmirror/downloads/101/0’

DownloadsAvailable: true (action id 101)

ActionLogMessage: (action 101 ) Non-Distributed - DownloadsAvailable

ActionLogMessage: (action 101 ) JobDiskFreeLimited - try again in 10 minutes

The package is 1597mb, at first it would stop at around 63mb but after growing various filesystems it stops at 1073. The ulimit is unlimited as default and there is no user with a specific value.

df -m

Filesystem MB blocks Free %Used Iused %Iused Mounted on

/dev/hd4 512.00 309.93 40% 13833 17% /

/dev/hd2 5568.00 3533.61 37% 40374 5% /usr

/dev/hd9var 10112.00 8211.47 19% 7958 1% /var

/dev/hd3 1024.00 991.58 4% 57 1% /tmp

/dev/hd1 64.00 63.63 1% 7 1% /home

/dev/hd11admin 128.00 127.64 1% 5 1% /admin

/proc - - - - - /proc

/dev/hd10opt 3456.00 3029.11 13% 8861 2% /opt

/dev/livedump 256.00 255.64 1% 4 1% /var/adm/ras/livedump

Any hint would be appreciated, thanks

Sebastien Raby

system · October 5, 2011, 2:13am

(imported comment written by SystemAdmin)

Part of this could be based on limits for the user the agent is running as or on your file system.

To set this limit from the Korn shell, run the following command:

ulimit -f unlimited

To set this value permanently for a specific user, use the chuser command, as shown in the following example:

chuser fsize_hard = -1 root

The maximum size of a file is ultimately a characteristic of the file system itself, not just the file size limit or the environment, as follows:

For the JFS, the maximum file size is determined by the parameters used at the time the file system was made. For JFS file systems that are enabled for large files, the maximum file size is slightly less than 64 gigabytes (0xff8400000). For all other JFS file systems, the maximum file size is 2Gb-1 (0x7fffffff). Attempts to write a file in excess of the maximum file size in any file system format will fail, and errno will be set to EFBIG.

For the JFS2, the maximum file size is limited by the size of the file system itself.

If both of these conditions are met then you might be encountering some other issue.

aixtools · October 7, 2017, 7:19pm

Although last reply is 2194 days old - still seems to be the place to reply

a) my partition is, by design, coming up with minimal fs sizes
b) I got the message “JonDiskFreeLimited” which is not too surprising – but, it is still unclear which filesystems the BESClient is looking at. More than just /opt and 1G free space it seems.

root@x069:[/]ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited

was:

root@x069:[/]df -m
Filesystem    MB blocks      Free %Used    Iused %Iused Mounted on
/dev/hd4         512.00    421.62   18%     4192     5% /
/dev/hd2        1536.00     17.34   99%    23088    60% /usr
/dev/hd9var      128.00     19.56   85%     1662    26% /var
/dev/hd3         128.00     49.88   62%       61     1% /tmp
/dev/hd1         128.00    127.64    1%        5     1% /home
/dev/hd11admin    128.00    127.63    1%        6     1% /admin
/proc                 -         -    -         -     -  /proc
/dev/hd10opt     256.00     96.62   63%      388     2% /opt
/dev/livedump    256.00    255.64    1%        4     1% /var/adm/ras/livedump

root@x069:[/]chfs -a size=2G /opt
Filesystem size changed to 4194304

now:
Filesystem    MB blocks      Free %Used    Iused %Iused Mounted on
/dev/hd4         512.00    421.60   18%     4192     5% /
/dev/hd2        1536.00     17.34   99%    23088    60% /usr
/dev/hd9var      128.00     19.49   85%     1662    26% /var
/dev/hd3         128.00     49.88   62%       61     1% /tmp
/dev/hd1         128.00    127.64    1%        5     1% /home
/dev/hd11admin    128.00    127.63    1%        6     1% /admin
/proc                 -         -    -         -     -  /proc
/dev/hd10opt    2048.00   1888.34    8%      388     1% /opt
/dev/livedump    256.00    255.64    1%        4     1% /var/adm/ras/livedump

I am going to increase the filesystems - starting with /, then /tmp, then /var - to 1G and hope I can report which filesystem did the trick.

Update: not sure - but it seems /var needs to have extra space - as with / and /tmp - both with over 1G free - message continued. After increasing /var to have > 1G free the actions continued normally.

Actually - my bad! I was thinking the BESClient was in /opt - but that is just the executable. /var/opt/BESClient is what needs space - and I need to make a task the root/server can run (or perhaps a relay - to create a new filesystem at /var/opt/BESClient before I deploy the agent!

IMHO: bad practice to depend on /var - as there are too many other things that depend on /var - but nice to see that BESClient is monitoring it’s (BESClient) free space - rather than stomp on /var.