From owner-freebsd-cloud@freebsd.org Tue Oct 4 19:41:30 2016 Return-Path: Delivered-To: freebsd-cloud@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B238AF5EA2 for ; Tue, 4 Oct 2016 19:41:30 +0000 (UTC) (envelope-from 010001579130685e-fc984470-c447-442d-8dde-7992e3501cf0-000000@amazonses.com) Received: from a8-56.smtp-out.amazonses.com (a8-56.smtp-out.amazonses.com [54.240.8.56]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63B6BDA1 for ; Tue, 4 Oct 2016 19:41:29 +0000 (UTC) (envelope-from 010001579130685e-fc984470-c447-442d-8dde-7992e3501cf0-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=vnqrkfnvu6csdl6mwgk5t6ix3nnepx57; d=tarsnap.com; t=1475609651; h=From:Subject:To:Message-ID:Date:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=PgvFTEummQTLdEXmCVD2FOlzrccF74i5gq6HSoPD4pM=; b=AbBlkwFiWCEhcD8eHqN8FCfA9hKe8BkVXCDOW9ZL2Z86vrSPbnNYiTwIYssRiebe zg5oLhyY6R4kH1jor0/i4jDsQH06/fOqCgR/8tWgdw/urRiajz7mO/Q2GLgn6VxoTgt e2sk4IwRz60NyzdqpQXfgv+pGy6Dwplw6uQnQvto= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1475609651; h=From:Subject:To:Message-ID:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=PgvFTEummQTLdEXmCVD2FOlzrccF74i5gq6HSoPD4pM=; b=c5P84onHFeIDKz3jSrNOgNhM4+1vj/PVYmeWSKjZ/198Y7mSMrei9HKwJacKdEQZ t+MYryOzmD7g+zj68S60i7ttIElL8Kekx1WdGUYSM/v4yVfKMA+MahowTWLSgv4SBqI KRV9SWO+wZXGEfeDilQn2YsWoNsITJGw6ls3iDKo= From: Colin Percival Subject: HEADS UP: Do not upgrade EC2 instances from 10.x to 11.x yet To: freebsd-cloud@freebsd.org, freebsd-stable@freebsd.org Message-ID: <010001579130685e-fc984470-c447-442d-8dde-7992e3501cf0-000000@email.amazonses.com> Date: Tue, 4 Oct 2016 19:34:11 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-SES-Outgoing: 2016.10.04-54.240.8.56 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-BeenThere: freebsd-cloud@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "FreeBSD on cloud platforms \(EC2, GCE, Azure, etc.\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Oct 2016 19:41:30 -0000 [Apologies if anyone gets this twice; the first copy I sent seems to have been eaten by a mail server somewhere.] We've identified a bug in the loader(8) in 11.0-RELEASE (to be precise, FreeBSD 11 after April 6th) which results in it attempting to read past the end of the disk if the last partition is not aligned to a 4k boundary. On most (maybe all) physical hardware this results in significant delays to the boot while the spurious I/O fails; in Amazon EC2, this results in the instance hanging permanently. Most systems do not have such misaligned partitions, but the FreeBSD 10.x images in EC2 do, and will consequently hang on reboot if you upgrade them to 11.0 (or to 12-current, for that matter). I recommend not doing this. The AMIs which have been built for FreeBSD 11.0 have properly aligned partitions, and are not affected by this bug, so (once the release is out!) you'll still be able to get FreeBSD 11.0 by launching new EC2 instances. I imagine that this will be fixed with an errata notice shortly after the release, after which point it will be safe to upgrade (since you'll end up with the fixed loader), but as always that will ultimately be up to the release engineering team. Thanks to Peter Ankerstål, Allan Jude, Warner Losh, and Glen Barber for their help in tracking down this problem. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid