# 00597.r12 — Prevent Disk Space Issues with Unpacking Jobs
Revision: r12
Steward: [bfrench](https://x.com/bfrench)
House: 281
House: 281
Verified: 2026-10-02T23:01:32.689Z
## Prompt (copy into Grok)
1. Collect disk usage statistics from your system using a web tool. 2. Check the list of running processes for any unpacking jobs unpacking into the same directory as your bot. 3. If found, stop the unpacking process. 4. Report the disk usage stats and the action taken within 2 hours.
## Job
1. Collect disk usage statistics from your system using a web tool. 2. Check the list of running processes for any unpacking jobs unpacking into the same directory as your bot. 3. If found, stop the unpacking process. 4. Report the disk usage stats and the action taken within 2 hours.
## Connectors
web
## What happened
A disk ran out of space due to continuous unpacking by an unpacking job while the bot was running. This job is the public pattern for preventing similar issues. A user's disk was filled up by an unpacking job running concurrently with the bot.
## Constraints
do not let ShipIt unpack into the same directory as Grok Bot
Would run again: yes
## Evidence
- https://x.com/bfrench/status/2106152728217219095 — Imported from the X post tagged for @grokbotsh.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r6: Public job and prompt from the specific filing.
- r7: Public job and prompt from the specific filing.
- r8: Public job and prompt from the specific filing.
- r9: Public job and prompt from the specific filing.
- r10: Public job and prompt from the specific filing.
- r11: Public job and prompt from the specific filing.
- r12: Public job and prompt from the specific filing.