From nobody Wed Jul 20 19:30:06 2022 X-Original-To: freebsd-hackers@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 4Lp5Q36sYSz4Wm6G; Wed, 20 Jul 2022 19:30:19 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Lp5Q24mHgz3S3B; Wed, 20 Jul 2022 19:30:18 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.16.1) with ESMTPS id 26KJU7IJ037021 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Jul 2022 21:30:08 +0200 (CEST) (envelope-from wojtek@puchar.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=puchar.net; s=default; t=1658345408; bh=eDC3ajNzXlJ+PF0LHi5Vld8gp/TCdIOCSlimZaWPFxc=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=WGwLTfCQXT9YIr/h7BrMdRT3DmpNgWwHBX1o2ls+vlJplqhWDmVrmjZI36jpDB2K+ qH2G6z6zglfgSysW0ImTELlhMOUr/ckCyqohIsbTT3HCHE5h0axoV2QrfZXMez7kOt 2OaaWrWPdpq6uNFBRPVzmG0Whde7ByxVjxPPoeE8= Received: from wojtek.intra (localhost [127.0.0.1]) by wojtek.intra (8.16.1/8.16.1) with ESMTP id 26KJU7Ei077677; Wed, 20 Jul 2022 21:30:07 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by wojtek.intra (8.16.1/8.16.1/Submit) with ESMTP id 26KJU60L077674; Wed, 20 Jul 2022 21:30:07 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: wojtek.intra: wojtek owned process doing -bs Date: Wed, 20 Jul 2022 21:30:06 +0200 (CEST) From: Wojciech Puchar To: Wei Hu cc: "freebsd-arm@freebsd.org" , "freebsd-hackers@FreeBSD.org" , Li-Wen Hsu , Souradeep Chakrabarti , "andrew@FreeBSD.org" Subject: Re: UFS checksum error during arm64 VM installation In-Reply-To: Message-ID: References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Rspamd-Queue-Id: 4Lp5Q24mHgz3S3B X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=puchar.net header.s=default header.b=WGwLTfCQ; dmarc=none; spf=pass (mx1.freebsd.org: domain of wojtek@puchar.net designates 194.1.144.90 as permitted sender) smtp.mailfrom=wojtek@puchar.net X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.998]; SUBJECT_ENDS_SPACES(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[puchar.net:s=default]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-arm@freebsd.org]; TO_DN_EQ_ADDR_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; DKIM_TRACE(0.00)[puchar.net:+]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_FIVE(0.00)[6]; ASN(0.00)[asn:43476, ipnet:194.1.144.0/24, country:PL]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[puchar.net]; HAS_XAW(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N hard to say. I've never in my life seen such an error, using FreeBSD for about 15 years, lots of different computers. Anyway i never used FreeBSD as guest on any VM, and i don't use Windows nor it's VM host software. May be a bug in Hyper-V that improperly emulates SCSI controller (i think it's emulating SCSI because your device is /dev/da*) - which result in error only on some kind of loads. ZFS and UFS works completely different. For example UFS is far more probable to do parallel writes to different locations in the same time. In the other hand it may be FreeBSD bug if Hyper-V emulated SCSI conform to standards but behave different than real SCSI controller and disk. As you are from microsoft you certainly could debug hyper-V to check if all reads and writes perform properly - i.e. writes data that it should write from guest memory, reads what it should and place in guest memory properly. I sugges to force fsck on this partition to check if it shows this checksum error or not. fsck doesn't do parallel reads If not - it's read handling problem. If yes - it may be both, but most probably write handling problems.