Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Determine how to configure larger VMs #1

Open
jkeenan opened this issue Jun 2, 2018 · 3 comments
Open

Determine how to configure larger VMs #1

jkeenan opened this issue Jun 2, 2018 · 3 comments
Assignees

Comments

@jkeenan
Copy link
Member

jkeenan commented Jun 2, 2018

The box we have been using as the basis for our VM, generic/freebsd11, is way too small for our needs. After only a few day's use, it was 63% full.

$ df
Filesystem   1K-blocks     Used    Avail Capacity  Mounted on
xxxxxxxxxx  30450780 17556964 10457756    63%    /

After two runs of test-against-dev processes, it was up to 86% full. Instead of a 31G (df -H) disk, we probably need 300 to 400 G.

Based on web searches, it should be possible to write a Vagrantfile which, upon vagrant up, will be that large. Make it so.

@jkeenan
Copy link
Member Author

jkeenan commented Jun 2, 2018

Additional data point: Simply populating the VM with FreeBSD packages needed to make the VM useful for test-against-dev fills the VM up to 16% of capacity.

[vagrant@experiment37 ~]$ df -H
Filesystem      Size    Used   Avail Capacity  Mounted on
xxxxxxxxxxx      31G    4.7G     24G    16%    /

@andrewvillano
Copy link
Contributor

perl-reporter-03 is now at 150G. Had to use a package that runs growfs on boot. https://forums.freebsd.org/threads/cannot-grow-filesystem-on-vagrant-server.66456/#post-392807

[vagrant@perl-reporter-03 ~]$ df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ada0s1a 142G 4.3G 127G 3% /
devfs 1.0K 1.0K 0B 100% /dev

@jkeenan
Copy link
Member Author

jkeenan commented Jul 8, 2018

As discussed, to the extent that we can make this reproducible via inclusion in a Vagrantfile, we should do that. Otherwise, we'll need a list of instructions, which we should store under configs/.

Thank you very much.
Jim Keenan

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants