From nobody Fri Nov 01 01:38:35 2024 X-Original-To: fs@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 4Xfk635NPgz5bMNK for ; Fri, 01 Nov 2024 01:38:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xfk6318L1z4P5n for ; Fri, 1 Nov 2024 01:38:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1730425115; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uFcqGLvKf31A49f/u9BfhiEg7eokK07SJ/ycjq3rH0I=; b=lv1y1WEAvFYvLjJvzyMojQ549SNBi2AnHXQ0jJVBfwHkL8AG9TaW9br7Begg97SXzOgIHN tynvJjrEP8GZHKDnhiKBerDtzx9Hjy0YMXYYz+B80hLBp5CTlt9RutczC+H3IoMflueo0j 9EDTAIcLJarKQWv5YOd+8fc728vsvZt7NP6hjjcxWu6KSxQkZtTgW43ZxMMIvDsRDjVOpQ WUl3yZr/2jXQnr9+x2NvmhRr49wU5eI9XkznaRozcJ+NA+MQMgHETcPEOUhjJ/FWtyTmpU Ys7omz5t0vOdMTsf4IsVhWRX6EaUnIO65FdaqEBKHUjUAF0aca880bLCSHgRUA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1730425115; a=rsa-sha256; cv=none; b=xx+1U5fe9YU5gJJ/rUUhbWZMp2/YSNvr9BFewh+tVVMl5uyL6xUGnX7FmtYjqWqPZltJx0 5pTfH6coKrB1H4FXreN6HqoRh/To3PWH7/AqJShLl0UaeKw3c6LzxzUScKv12AFkKTvv82 f+jiApYQJLXmQuh+wjnKmwtE9hXfKhRUIRBL8454otVVFz2iToYbpUSVdZBmjJBBQzL4kL hGhe98eDeqryWChb5pEpQ/9dG79cMUr0T59cXuol5BV4dHNSDMUN2vZ+LbKbGYXJdHHzk5 nAsZaptLBzQoYTiy6tEgXWILcAb0hbXxdQZoECqp3HDmbZbTz7FHXnINqaYDuw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Xfk630mDgz10kH for ; Fri, 1 Nov 2024 01:38:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4A11cZcR076296 for ; Fri, 1 Nov 2024 01:38:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4A11cZe9076295 for fs@FreeBSD.org; Fri, 1 Nov 2024 01:38:35 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 282449] UFS deadlock with install -S during freebsd-update Date: Fri, 01 Nov 2024 01:38:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: Unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: Grau_Smue@md5hashing.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Filesystems List-Archive: https://lists.freebsd.org/archives/freebsd-fs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-fs@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D282449 --- Comment #6 from vfs-locking --- (In reply to Mark Millard from comment #5) Notwithstanding that it looks like an I/O pileup, my impression is that the= re is something more. My previous 2 or 3 encounters on VBox were all on hosti= ng ZFS with sync=3Ddisabled, and there were no errors on the host side at those times since it continued other VMs and I/O. I only tried sync=3Dstandard t= his time because I was out of good ideas in attempts to reproduce. On the VPS encounter a few weeks ago, there could very well have been limit= ed I/O. But not zero. It was the VPS encounter that convinced me I was looki= ng at something other than a VBox bug, which is what I had previously thought = this was. I had changed from SCSI to AHCI in the guest, and even read about a f= ix in VBox that could have been my issue, until it happened again. From there, it felt like a locking or race bug to me, that was happening because of the high volume of fsync() and rename() calls via install -S. I know those are hard to reproduce, but thats why I was willing to try repeatedly. --=20 You are receiving this mail because: You are the assignee for the bug.=