From owner-freebsd-stable@freebsd.org Fri May 22 14:01:52 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DA3AF2C9456; Fri, 22 May 2020 14:01:52 +0000 (UTC) (envelope-from freebsd-lists-5@thismonkey.com) Received: from mail-01.thismonkey.com (mail-01.thismonkey.com [IPv6:2406:3400:35e:6602::a01:232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thismonkey.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49T7T94Cffz4Lh6; Fri, 22 May 2020 14:01:48 +0000 (UTC) (envelope-from freebsd-lists-5@thismonkey.com) Received: from mailhub-01.thismonkey.com (mailhub-01.thismonkey.com [IPv6:2406:3400:35e:6601:0:0:a01:11e]) by mail-01.thismonkey.com (8.15.2/8.15.2) with ESMTP id 04ME1Y53013810; Sat, 23 May 2020 00:01:36 +1000 (EST) (envelope-from freebsd-lists-5@thismonkey.com) X-TM-Via-MX: mailhub-01.thismonkey.com Received: from utility-01.thismonkey.com (utility-01.thismonkey.com [IPv6:2406:3400:35e:6601:0:0:a01:120]) by mailhub-01.thismonkey.com (8.15.2/8.15.2) with ESMTPS id 04ME1YXu054708 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 23 May 2020 00:01:34 +1000 (AEST) (envelope-from freebsd-lists-5@thismonkey.com) Received: from utility-01.thismonkey.com (localhost [127.0.0.1]) by utility-01.thismonkey.com (8.15.2/8.15.2) with ESMTP id 04ME1Yvd027988; Sat, 23 May 2020 00:01:34 +1000 (EST) (envelope-from freebsd-lists-5@thismonkey.com) Received: (from root@localhost) by utility-01.thismonkey.com (8.15.2/8.15.2/Submit) id 04ME1YPO027987; Sat, 23 May 2020 00:01:34 +1000 (EST) (envelope-from freebsd-lists-5@thismonkey.com) Date: Sat, 23 May 2020 00:01:34 +1000 From: Scott To: stable@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Is it me or does FreeBSD (12.1 amd64) hang when I manually snapshot it in VSphere 6.7? Message-ID: <20200522140133.GA93041@thismonkey.com> Mail-Followup-To: stable@freebsd.org, freebsd-stable@freebsd.org References: <34c87fb8aa97ce4fa20deaf25da738f2@ultra-secure.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <34c87fb8aa97ce4fa20deaf25da738f2@ultra-secure.de> User-Agent: Mutt/1.11.4 (2019-03-13) X-Virus-Scanned: clamav-milter 0.102.2 at mail-01.thismonkey.com X-Virus-Status: Clean X-Rspamd-Queue-Id: 49T7T94Cffz4Lh6 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=thismonkey.com; spf=pass (mx1.freebsd.org: domain of freebsd-lists-5@thismonkey.com designates 2406:3400:35e:6602::a01:232 as permitted sender) smtp.mailfrom=freebsd-lists-5@thismonkey.com X-Spamd-Result: default: False [-2.00 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-0.99)[-0.989]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_HAM_SHORT(-0.22)[-0.217]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[thismonkey.com,none]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:10143, ipnet:2406:3400:300::/40, country:AU]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 May 2020 14:01:52 -0000 On Fri, May 22, 2020 at 12:31:29AM +0200, rainer@ultra-secure.de wrote: > Hi, > > > subject says it all, basically. > > The system becomes totally unresponsive and has to be power-cycled. > > da0 at mpt0 bus 0 scbus2 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) > da0: Command Queueing enabled > da0: 40960MB (83886080 512 byte sectors) > da0: quirks=0x140 > > > This is a bit of a problem here, to say the least. > > #metoo: HV: VMware ESXi, 6.7.0, 11675023 VM: # freebsd-version -kru 12.1-RELEASE-p1 12.1-RELEASE-p1 12.1-RELEASE-p1 # uname -a FreeBSD XXX 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 GENERIC amd64 # pkg info open-vm\* open-vm-tools-nox11-11.0.1_1,2 doesn't hang but becomes *very* unresponsive over the network. pings are shot. Console is fine though. 100% idle on top across 4 cores. And: # openssl speed -evp aes-256-cbc ... 1024 bytes block: 542595.18k (1593774 in 3 seconds) I never noticed that before. I normally turn off snapshotting the RAM because it's so much faster and I'm happy with crash consistent rollbacks. Rebooting fixes the awful network behaviour. I didn't check the disk subsystem. Scott