Can we please get the disk space increased on jenkins1.qa.scl3.mozilla.com? Please see bug https://bugzilla.mozilla.org/show_bug.cgi?id=1137171 .
How much were you thinking? An expansion requires a reboot to pick up the new partition scheme. We'll need to have that timing planned.
Can we double it to 500GB? That should give us more than enough. I'd be happy to schedule a time for this box to be restarted.
So, in bug 1137171 comment 10 it sounds like there are plans to move things off. Since storage is a shared resource, I want to avoid overallocation wherever possible, and 250G is a lot. Growing is easy, reclaiming is hard, running out is disastrous. If 250's what's really needed, okay. If you're hedging high, I'd ask that we just go with what you think will conservatively get you through, and if we end up needing a 2nd bump we can do that.
Makes sense. Let's bump us up to a total disk space of 300GB and see if that gets us what we need.
Prepped the host to have 300G. It needs a reboot (partition table change). If you can reboot it, do it whenever you like. If you need us to, we usually have someone available between 1100 and 0500 UTC during the week (though 1300-2100 would be happiest), just let us know. After rebooting, we can expand the filesystem.
I've just triggered a reboot, and the VM has not come back online. I'll raise a separate bug for someone to look at the box.
Filesystem expanded now the machine is back up: [email@example.com pradcliffe]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 293G 197G 82G 71% / tmpfs 7.8G 0 7.8G 0% /dev/shm /dev/sda1 985M 71M 864M 8% /boot
Machine rebooted again on new kernel with expanded filesystem.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.