From owner-freebsd-fs@freebsd.org Tue Mar 2 19:39:48 2021 Return-Path: Delivered-To: freebsd-fs@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 D65B354E27F for ; Tue, 2 Mar 2021 19:39:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DqnX45X8wz3G32 for ; Tue, 2 Mar 2021 19:39:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id BBF4554E07D; Tue, 2 Mar 2021 19:39:48 +0000 (UTC) Delivered-To: fs@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 BBC0354E463 for ; Tue, 2 Mar 2021 19:39:48 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DqnX44tfDz3GMk for ; Tue, 2 Mar 2021 19:39:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 9AE761C4AF for ; Tue, 2 Mar 2021 19:39:48 +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 122JdmRV097309 for ; Tue, 2 Mar 2021 19:39:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 122Jdm9a097308 for fs@FreeBSD.org; Tue, 2 Mar 2021 19:39:48 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 244048] mksnap_ffs hangs machine (12.1 regression over 11.3) Date: Tue, 02 Mar 2021 19:39:48 +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: 12.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ml@netfence.it X-Bugzilla-Status: Open 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Mar 2021 19:39:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244048 --- Comment #16 from ml@netfence.it --- (In reply to Kirk McKusick from comment #15) I've never had problems with snapshots on 11.x (or earlier), up to 11.4, altough I never tried 11-STABLE. The problem started when either I built a new machine with 12.1 or upgraded= a 11.3 to 12.1. 12.2 also shows the problem. I never tried 12.0 or 12-STABLE. As I said, I was going to try 13.0 (should almost be the same as 13-STABLE = now, shouldn't it?) If you'd like me to also try 12-STABLE, I will. Does 11-STABLE differ that much from 11.4 (given 11.4 should be the last release on this branch)? I ask because it will be harder for me to try this. In fact I know how to trigger the problem exactly: I have a VM I can boot a= nd just issue "rm /mnt/.snap/1". Unfortunately, this disk image, besides being quite large, holds data that belongs to a customer of mine, so I cannot share it. I will try to build a new one with different data, but previously I wasn't = able to trigger the problem until I "rsync"ed from there, so it will take some t= ime and some luck. Thanks for your help. --=20 You are receiving this mail because: You are the assignee for the bug.=