Date: Mon, 11 Feb 2019 08:32:26 +0000 From: Colin Percival <cperciva@tarsnap.com> To: Ben Woods <woodsb02@gmail.com>, freebsd-cloud@freebsd.org, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: Any plans for EC2 AMIs with RootOnZFS? Message-ID: <01000168dbaf9e03-9e3417ac-5ed5-4f32-9378-132cc620a63c-000000@email.amazonses.com> In-Reply-To: <dd6abea1-de34-5d5c-00dd-86aa11ba1432@tarsnap.com> References: <CAOc73CBQ%2B282amu-d%2BcxUehLBuhPKSrWTnft1_eSvY5FNKynwg@mail.gmail.com> <01000167dd7b16cd-58ee733f-c662-42d5-9c75-2301fbc8377a-000000@email.amazonses.com> <dd6abea1-de34-5d5c-00dd-86aa11ba1432@tarsnap.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/27/18 5:44 PM, Colin Percival wrote: > Can people please try out this AMI and let me know if there's anything else > (ZFS-related) which I should fix? Some time next week I'll fix whatever > people notice and build AMIs for all the regions. Ok, so "next week" turned into "six weeks later", but I now have a new AMI: ami-0629bc11fede58e9e (us-east-1 region). This should correct the issues Ben noticed with my earlier attempt: * The ZFS mounts should now match the installer default. * I've added some settings to loader.conf and sysctl.conf. * If you launch the AMI with a >10 GB disk, it will resize the zpool to use the available space. (This uses the /etc/rc.d/growfs update which I committed on Friday.) Please try this AMI and let me know if you find any more issues. Once everything is working I'll publish the AMI in all the public EC2 regions and blog about the process I used to create this. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01000168dbaf9e03-9e3417ac-5ed5-4f32-9378-132cc620a63c-000000>