Validate available disk space before installing package

maybe change your policy to two different policies, one that checks for the right amount of free space and if its enough then call the CC install with a custom trigger. if there is not enough space, display the message and quit that script

If this is the only instance where you're using a script parameter with space, may I suggest an alternative?
Create an extension attribute that calculates free disk space. Then create a smart group that utilizes that extension attribute where only those that have more than X GB of free space can install the software.

Those that do not meet that criteria will obviously not see the Self Service item. But you could create the same smart group for those that have less than X GB of free space and have some sort of notifier via jamfHelper to let them know they do not have enough free space and need to clear up X GB to proceed. You'll probably need to instruct them to run an inventory check which could be either a separate policy (or maybe included in that same policy that notifies them, but that would probably mean having to run the same policy twice since they won't know they are low on space the first time they run that policy).

The EA capturing free disk space isn't a bad idea @bpavlov. We have one that does that for awhile since we want to keep track of that, but it should just be noted that EAs, like all inventory items are only static values in time. The amount of free disk space can change dramatically in a matter of minutes.
Example: The policy requires 70 GB+ of free disk space. One Mac has 77 GB of free disk space in the AM when their Mac submits inventory, so their Mac lands in the Smart Group scoped to the Self Service policy. A little after, they download some large files that consume ~10 GB of space, they are now at ~66 GB of free disk space, so below the amount necessary to run the policy without causing issues, but of course their Mac has not submitted new inventory since, maybe no new policies have run on it. The Mac will still be in the Smart Group b/c the JSS is unaware that the user just ate up a bunch of available space. What happens now when they run the policy from Self Service?

I'm not saying the above scenario will be very common, but its also quite possible to happen. I do like the idea of doing a dynamic on the fly check for requirements in a script, but, as I and others have noted elsewhere, policies are unfortunately only smart when they are taken as a whole. Individual items within a policy are actually quite dumb and have no knowledge of what has come before them or what comes after them. A script run "before" can't dictate to the package portion of the policy that it should not run the installation, nor vice versa. Its also why both of these feature requests have been made:
https://jamfnation.jamfsoftware.com/featureRequest.html?id=2991
https://jamfnation.jamfsoftware.com/featureRequest.html?id=3669
Its the same general problem, and its really one of my biggest complaints about how policies work. They are disparate items strung together on an assembly line. The assembly line equipment that is supposed to fill the bottle with soda is going to dispense the liquid even if the bottle isn't there! (Note: I do not know if that's actually how modern assembly lines work, so I'm just using it as an example)

I really hope JAMF is working on making this all more intelligent, because right now its kind of impossible to use some items in a policy (like Scripts) to dictate how the remainder of the policy should run, or not run as it were.

Indeed @mm2270 that is a very good point. I suppose depending on how often you have inventory take place the extension attribute will hopefully be usually accurate. However if policies had logic built into them then it would make things a lot easier to manage for sure. I can't recall right now but I do remember seeing a feature request that asked for it that was different from the one you linked that may have had a few more votes but would probably better address the issue at hand. The request was for policies to stop and not proceed if a certain step in the policy failed. If I can find it, I'll link it here.

If it doesn't already, Casper should do this automatically without the admin having to re-invent the wheel. Casper should track the size of the item and the space needed for its install and not attempt download or install if there is not enough free space. There should be no need for the admin to reinvent this logic over and over for each software item.

Creating Extension Attributes and Smart Groups is a very powerful feature of Casper, but an admin should not have to do this for every single software package just to ensure there is enough free space to install.

Another feature requested created: https://jamfnation.jamfsoftware.com/featureRequest.html?id=3698

Thanks @nessts, @bpavlov, @mm2270 and @gregneagle.

Thanks @dan.snelson for the script,
I'm looking for a similar solution the only difference is i'm caching rather than installing the Adobe packages in the policy.

Did you come up with a solution ?

I'm testing the approach suggested by @nessts (thank you also!) where the script in the first policy then triggers the cache policy if there's enough disk space.

This is working well apart from when the first policy runs in Self Service the progress bar states that it's running the script but it remains on that progress bar until the second policy has completed, does anyone know how this could be avoided ?

I was considering re-naming the script to something like "bepatientyourstuffisdownloadinggomakesometea.sh" to hopefully keep the downloader from panicking and force quiiting Self Service during their 8GB download.

1#Trigger part of the script
2
3else
4    echo "triggering cache policy"
5    jamf policy -trigger cachetestpolicy
6
7fi
8
9exit 0      ## Success

I guess it makes sense that it would sit there and wait. You could use a Cocoa Dialog to put up a notice or a progress bar before the trigger that notifies the user that they have enough disk space and tell them to be patient.

@nessts

I imagined that it should complete the first policy that contains the trigger script
then once the triggered policy is running then show the progress for that policy
"i imagine" many things....

I like the idea of a notification, thanks! It should be simple to add jamfhelper to the script

if you add a

&

after the cachetestpolicy it would likely finish the script.

@nessts Thank you, simple and effective!!

It now finishes the Self Service policy and runs the triggered policy in the background so i just need to add a notification to that policy.

Updates for macOS 10.12 (i.e., "Volume Free Space:" vs. "Volume Available Space:")

1#!/bin/sh
2####################################################################################################
3#
4# ABOUT
5#
6#   Check Free Space
7#
8####################################################################################################
9#
10# HISTORY
11#
12#   Version 1.0, 17-Jun-2015, Dan K. Snelson
13#   Version 2.0, 28-Oct-2015, Dan K. Snelson
14#       Stops Self Service by calling a policy which runs a script.
15#   Version 2.1, 04-Jan-2017, Dan K. Snelson
16#       Updated for macOS 10.12
17#
18####################################################################################################
19# Import logging functions
20source /path/to/client-side/logging/script/logging.sh
21####################################################################################################
22
23## Variables
24requiredSpace="$4"            # Availble Space Required (in GBs)
25
26
27osMinorVersion=$(/usr/bin/sw_vers -productVersion | /usr/bin/cut -d. -f2)
28
29    if [[ "$osMinorVersion" -lt 12 ]]; then
30
31        availableSpace=$(/usr/sbin/diskutil info / | grep "Volume Free Space:" | awk '{print $4}')
32        availableSpaceInt=$(/bin/echo "($availableSpace+0.5)/1" | bc)
33        totalSpace=$(/usr/sbin/diskutil info / | grep "Total Size:" | awk '{print $3}')
34
35    else
36
37        availableSpace=$(/usr/sbin/diskutil info / | grep "Volume Available Space:" | awk '{print $4}')
38        availableSpaceInt=$(/bin/echo "($availableSpace+0.5)/1" | bc)
39        totalSpace=$(/usr/sbin/diskutil info / | grep "Volume Total Space:" | awk '{print $4}')
40
41    fi
42
43
44
45ScriptLog "*** Check Free Space ***"
46ScriptLog "Required Space: $requiredSpace"
47ScriptLog "Available Space:    $availableSpaceInt"
48
49if [ "$availableSpaceInt" -lt "$requiredSpace" ]; then
50    /usr/local/jamf/bin/jamf displayMessage -message "Insufficient Free Space Available
51
52This installation requires $requiredSpace GB.
53There is $availableSpace GB available.
54
55"
56
57    /bin/sleep 2
58
59    jssLog "Error: Insufficient Free Space Available: This installation requires $requiredSpace GB; There is $availableSpace GB available."
60
61    ## Call policy to kill download
62    /usr/local/jamf/bin/jamf policy -trigger stopSelfService
63    exit 1      ## Failure
64
65else
66
67    jssLog "There is enough free space available: This installation requires $requiredSpace GB; There is $availableSpace GB available."
68
69fi
70
71
72exit 0      ## Success

Another way to do this. The benefit being not having to account for multiple OSes, or have to deal with TB or GB being returned

1df -g / | tail -n +2 | awk '{print $4}'

@seann Thanks for your command. I made it a bit simpler.

1df -g / | awk 'FNR==2{print $4}'

Quite old this post - but tried it, but seems to be issues with Catalina.

Scriptlog command cannot be found when I execute this one

1#!/bin/sh
2####################################################################################################
3#
4# ABOUT
5#
6#   Check Free Space
7#
8####################################################################################################
9#
10# HISTORY
11#
12#   Version 1.0, 17-Jun-2015, Dan K. Snelson
13#   Version 2.0, 28-Oct-2015, Dan K. Snelson
14#       Stops Self Service by calling a policy which runs a script.
15#   Version 2.1, 04-Jan-2017, Dan K. Snelson
16#       Updated for macOS 10.12
17#
18####################################################################################################
19# Import logging functions
20source /path/to/client-side/logging/script/logging.sh
21####################################################################################################
22
23## Variables
24requiredSpace="$4"            # Availble Space Required (in GBs)
25
26
27osMinorVersion=$(/usr/bin/sw_vers -productVersion | /usr/bin/cut -d. -f2)
28
29    if [[ "$osMinorVersion" -lt 15 ]]; then
30
31        availableSpace=$(/usr/sbin/diskutil info / | grep "Volume Free Space:" | awk '{print $4}')
32        availableSpaceInt=$(/bin/echo "($availableSpace+0.5)/1" | bc)
33        totalSpace=$(/usr/sbin/diskutil info / | grep "Total Size:" | awk '{print $3}')
34
35    else
36
37        availableSpace=$(/usr/sbin/diskutil info / | grep "Volume Available Space:" | awk '{print $4}')
38        availableSpaceInt=$(/bin/echo "($availableSpace+0.5)/1" | bc)
39        totalSpace=$(/usr/sbin/diskutil info / | grep "Volume Total Space:" | awk '{print $4}')
40
41    fi
42
43
44
45ScriptLog "*** Check Free Space ***"
46ScriptLog "Required Space: $requiredSpace"
47ScriptLog "Available Space:    $availableSpaceInt"
48
49if [ "$availableSpaceInt" -lt "$requiredSpace" ]; then
50    /usr/local/jamf/bin/jamf displayMessage -message "Insufficient Free Space Available
51
52This installation requires $requiredSpace GB.
53There is $availableSpace GB available.
54
55"
56
57    /bin/sleep 2
58
59    jssLog "Error: Insufficient Free Space Available: This installation requires $requiredSpace GB; There is $availableSpace GB available."
60
61    ## Call policy to kill download
62    /usr/local/jamf/bin/jamf policy -trigger stopSelfService
63    exit 1      ## Failure
64
65else
66
67    jssLog "There is enough free space available: This installation requires $requiredSpace GB; There is $availableSpace GB available."
68
69fi
70
71
72exit 0      ## Success

only compatible version or method with Catalina? this would be extremely useful. initially, i was considering using smart groups to scope out insufficient disk space but that would not be necessarily clear to the user, unless they were scoped out and a jamfhelper prompt notified them to clean up space to install future applications...

Seems like the script above is 1 part of it, while the scriptlog part is missing. It is quite old, but maybe someone can show a working example, could be usefull for me as I am not a script guy

I also struggled with this because the amount of free space reported by df and any other built-in cli utilities only shows that value based on the number of currently free blocks; it doesn't account for temp files and other items that the OS will automatically remove if some process requires it.  Fortunately I found a great utility to give you much more practical free space data: https://scriptingosx.com/2021/11/monterey-python-and-free-disk-space/.  It's a small and simple standalone binary written in Swift and is perfect for generating a more useful EA for available free space.