From nobody Fri Feb 25 14:13:04 2022 X-Original-To: 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 AA92A19E6636 for ; Fri, 25 Feb 2022 14:13:12 +0000 (UTC) (envelope-from SRS0=Xigz=TI=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 4K4sF331SCz3rb9 for ; Fri, 25 Feb 2022 14:13:11 +0000 (UTC) (envelope-from SRS0=Xigz=TI=klop.ws=ronald-lists@realworks.nl) Date: Fri, 25 Feb 2022 15:13:04 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1645798384; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Td318JuglYBOIxIbmLog/vpARUrn7599xg03+wdxRGY=; b=taV8QTlyokOl9EyUNZmNZIDGeFbkMx2m1y6HkrEzFC2J+77VvmmUML9PSJbj81TbjT/zyk 2OR4JFYugKx+1XglruBJYBQRAII33JBJpn3KKcWNRjyCc1MVXyxjOj8+6mHXGzPc3GZs7r /LQzm1iHRwKTVrcqPuIgrGQkJMmpw9sD1Fsh54qB4+1UbhnmMP0wIJG9uf4qhf82aiiIQK IxfErPOM2IQgXPEMeFsPvBQwzUCxRsMP0uxH52vgyDMy5RI1193ubCGarHMArcQMSsAD9I kgWOOQvkO2klvSlpdlHTURytgepxYUKukHykzzcFkXD9LMo41H+5UEBEu7RpCA== From: Ronald Klop To: Pete French Cc: stable@freebsd.org, Chuck Tuffli Message-ID: <911165478.11.1645798384085@mailrelay> In-Reply-To: References: <82956746-91aa-4744-c12f-40c5ff7c3f39@twisted.org.uk> Subject: Re: Instance drives in AWS comming up with the wrong size 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 Content-Type: multipart/alternative; boundary="----=_Part_10_656879731.1645798383998" X-Mailer: Realworks (598.165.b8bc7a1) Importance: Normal X-Priority: 3 (Normal) X-Rspamd-Queue-Id: 4K4sF331SCz3rb9 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=taV8QTly; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=Xigz=TI=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=Xigz=TI=klop.ws=ronald-lists@realworks.nl" X-Spamd-Result: default: False [-3.20 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; HAS_X_PRIO_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[stable]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=Xigz=TI=klop.ws=ronald-lists@realworks.nl]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=Xigz=TI=klop.ws=ronald-lists@realworks.nl]; FREEMAIL_CC(0.00)[freebsd.org,gmail.com] X-ThisMailContainsUnwantedMimeParts: N ------=_Part_10_656879731.1645798383998 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Wow, diskinfo.c has explicit support for regular files: isreg = S_ISREG(sb.st_mode); if (isreg) { mediasize = sb.st_size; sectorsize = S_BLKSIZE; fwsectors = 0; fwheads = 0; But I would not know the proper use case for that related to the name of the tool. Anyways, nice catch. Computers are weird. Cheers, Ronald. Van: Pete French Datum: vrijdag, 25 februari 2022 11:30 Aan: Chuck Tuffli CC: stable@freebsd.org Onderwerp: Re: Instance drives in AWS comming up with the wrong size > > Ok, I found what was causing this, there is no bug, and I am somewhat embarassed. > > Somehow I ended up with a file called 'nda2' in /root > > So doing 'diskinfo' in /root finds the file not the device. Simple as that. > > sorry for the noise! > > -pete. > > > > ------=_Part_10_656879731.1645798383998 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Wow,

diskinfo.c has explicit support for regular files:

                isreg = S_ISREG(sb.st_mode);
                if (isreg) {
                        mediasize = sb.st_size;
                        sectorsize = S_BLKSIZE;
                        fwsectors = 0;
                        fwheads = 0;

But I would not know the proper use case for that related to the name of the tool.

Anyways, nice catch. Computers are weird.

Cheers,
Ronald.

 

Van: Pete French <pete@twisted.org.uk>
Datum: vrijdag, 25 februari 2022 11:30
Aan: Chuck Tuffli <ctuffli@gmail.com>
CC: stable@freebsd.org
Onderwerp: Re: Instance drives in AWS comming up with the wrong size

Ok, I found what was causing this, there is no bug, and I am somewhat embarassed.

Somehow I ended up with a file called 'nda2' in /root

So doing 'diskinfo' in /root finds the file not the device. Simple as that.

sorry for the noise!

-pete.
 
------=_Part_10_656879731.1645798383998--