From nobody Tue Feb 22 19:11:35 2022 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id D745B19D8222 for ; Tue, 22 Feb 2022 19:11:46 +0000 (UTC) (envelope-from pete@twisted.org.uk) Received: from toybox.twisted.org.uk (toybox.twisted.org.uk [178.250.76.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4K380x6mgvz4W9w for ; Tue, 22 Feb 2022 19:11:45 +0000 (UTC) (envelope-from pete@twisted.org.uk) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=twisted.org.uk; s=x; h=Content-Transfer-Encoding:Content-Type:Subject:From: To:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=XtM+7KjdYlAnq9OJQ9YnHNT/CaQHWBzM5KGpi7lbTpo=; b=lKWaZP921EiIXVaMA8/ZbGw829 J8EvfPj50rtSyD/DfYmZp0Qz+FdXM3BTrRFrM0G1musd/PZ2rp3JaUIiovTl9chKYgrmOJlGic8Mn sihH4MjPNiU/hBqK+tkz2ZTpblYrXlVex5O1W61kVpOxVNgfHTXtbFTsTVSoJfG+x8bI=; Received: from mailnull by toybox.twisted.org.uk with spamc-scanned (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1nMaZV-000Bpm-N1 for freebsd-stable@freebsd.org; Tue, 22 Feb 2022 19:11:38 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.5 (2021-03-20) on toybox.twisted.org.uk X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=ALL_TRUSTED,TW_NV autolearn=unavailable autolearn_force=no version=3.4.5 X-Spam-Score: -0.9 () Received: from [2001:470:6cc4:1:cd6:5836:ddba:7b54] by toybox.twisted.org.uk with esmtpsa (TLS1.3) tls TLS_AES_128_GCM_SHA256 (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1nMaZV-000Bpj-Ko for freebsd-stable@freebsd.org; Tue, 22 Feb 2022 19:11:37 +0000 Message-ID: Date: Tue, 22 Feb 2022 19:11:35 +0000 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 To: FreeBSD Stable Mailing List From: Pete French Subject: Instance drives in AWS comming up with the wrong size Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-spamc-toybox: true X-transport-toybox: lookuphost X-Rspamd-Queue-Id: 4K380x6mgvz4W9w X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=twisted.org.uk header.s=x header.b=lKWaZP92; dmarc=none; spf=pass (mx1.freebsd.org: domain of pete@twisted.org.uk designates 178.250.76.50 as permitted sender) smtp.mailfrom=pete@twisted.org.uk X-Spamd-Result: default: False [-3.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[twisted.org.uk:s=x]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:178.250.76.50/32]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[twisted.org.uk]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[twisted.org.uk:+]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MLMMJ_DEST(0.00)[freebsd-stable]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:12290, ipnet:178.250.72.0/21, country:GB]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N So, I have a number of machines in AWS. They are all of type r5a.xlarge which is supposed to have 140 gig of instance syorage on it. All these machines started life as clones of the same dirve, ro are runnign the same OS kernel, and they all have mysql on them. Some of them also have Apache and some other software, but I thought the config of the base OS was the same. Certainly /boot/loader.conf and /etc/sysctl.conf are indentical and its the same kernel and userland running on all of them. but on the mysql-only of the machines the instance drives have the worng size, around a gig, and are not recognised properly. Example, heres iw what it is supposed to look like (from one of the Apache machines) root@sydney01:/usr/home/webadmin # diskinfo -v nda2 nda2 512 # sectorsize 150000000000 # mediasize in bytes (140G) 292968750 # mediasize in sectors 0 # stripesize 0 # stripeoffset Amazon EC2 NVMe Instance Storage # Disk descr. AWSB7ABDF8FE8D0597AF # Disk ident. nvme2 # Attachment Yes # TRIM/UNMAP support 0 # Rotation rate in RPM and here is one of the ones which is wrong... root@serpentine-sydy:~ # diskinfo -v nda2 nda2 512 # sectorsize 886571008 # mediasize in bytes (846M) 1731584 # mediasize in sectors 131072 # stripesize 0 # stripeoffset No # TRIM/UNMAP support Unknown # Rotation rate in RPM But both machines, in dmesg, have lines which look like this: nda2 at nvme2 bus 0 scbus2 target 0 lun 1 nda2: nda2: Serial Number AWSB7ABDF8FE8D0597AF nda2: nvme version 1.0 x0 (max x0) lanes PCIe Gen0 (max Gen0) link nda2: 143051MB (292968750 512 byte sectors) So on both of then the detection says its the right size. The oddest this is that this is completely reproducible betwene data centres - the above machines above are in Sydney, but I get precisely the same result from the machines in North Virginia. So its something about the config but what on earth could it be ? I am very puzzled - I have a set of database-nly machine sin Frankfurt, and they behave fine! Poissibly I should just clone those to Australia and the US, but I would like to find out what the magic difference is between them. -pete.