From owner-freebsd-fs@freebsd.org Sun Jul 15 21:00:45 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07E541028B49 for ; Sun, 15 Jul 2018 21:00:45 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7BC5F97CDF for ; Sun, 15 Jul 2018 21:00:44 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3AFC91028B39; Sun, 15 Jul 2018 21:00:44 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 004D21028B32 for ; Sun, 15 Jul 2018 21:00:44 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 909C197CCF for ; Sun, 15 Jul 2018 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DA1669ABE for ; Sun, 15 Jul 2018 21:00:42 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6FL0got064194 for ; Sun, 15 Jul 2018 21:00:42 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6FL0gKm064183 for fs@FreeBSD.org; Sun, 15 Jul 2018 21:00:42 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201807152100.w6FL0gKm064183@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 15 Jul 2018 21:00:42 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jul 2018 21:00:45 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off New | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Jul 16 17:44:19 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7CBB1032C85 for ; Mon, 16 Jul 2018 17:44:19 +0000 (UTC) (envelope-from jack@chillysky.com) Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33D957B933 for ; Mon, 16 Jul 2018 17:44:19 +0000 (UTC) (envelope-from jack@chillysky.com) Received: by mail-wr1-x442.google.com with SMTP id a3-v6so23544341wrt.2 for ; Mon, 16 Jul 2018 10:44:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chillysky-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qP8oEVHu1Tz1fB9GsYqFgbEPewKnW9iHd2lJ5PDYhhQ=; b=rrb2zw2yWGzTj5BqTxU7cRRNR73UFyFOVZQ/Mzggs//Wv1wImfT/g3NTz96CjbxuBT fAacM/4D6K+S2uH1xVMPY0E4FCczjxH++mEJ9yqxn4BT7rxv/J4Y+t8rbJpL0jOVxpMo NUN/PWOk4jx2rmoxG55OXy3wob3wBv4ArvcnoqNxEMzAphT+rAbtx9rZYlSu3W5ky3TX SNYLIW1LLIqr4+1ZDfGzyIT2YeN2FhE3pROUbw3dUA57Y/nY/p4487vhj0ACMF5mQyVb 0GQV/mj6Jcfzh7aiGBVO2pBVbI+rHEKNS3iKP7L6T/zyRl06gR6LdhUfPnE0IJ+cY7W7 YLRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qP8oEVHu1Tz1fB9GsYqFgbEPewKnW9iHd2lJ5PDYhhQ=; b=bsto7xgtH3P6I5xT0yYTPPjbONVrU9u3mRzpYVhJYgrqvbISPh80/Jp8KQACPt3j85 Ke2woSRscLCYRZisJYdgrUgco/wrYsvS5dlzMrcLiwneDoqW+KedF/Cz319+aRgsu1eA 8VDPlp3E+DKeqIrP8HqjT7f+t/CbwOICmfZs3Kkf85AGLgEPmRLGXOtyPSrvl22sXBkK ejOoBt0ckhSNvbuXXihR7tn3/TnyQot9FxIS2+MVi0IBVJbbT8iiRVKAvnLKfdQCkMIX Z03FRcgX8t7CoSfSHgaLX6W9UVrV9fJRWT6JT5EEwtYfCH8nvfNwmgxyPZ7ho15H4EzB S/dw== X-Gm-Message-State: AOUpUlF1FM04Td7+F6oQW4vmRHzEaK5RfPh1MQ0ZLhJY6HMyUQaCSfQ0 SGRALSpNTbzMinPzeZZQmj8on0tp8EBbxEADsHXrCrum X-Google-Smtp-Source: AAOMgpehsMsqoMpn2YQxRnOGCCn12I4uwjHBKDkVzAMtZMFk397sA1v/hbmZQOwh3d8x47OeGqfIsUDrdOYGC4ddCNo= X-Received: by 2002:adf:a541:: with SMTP id j1-v6mr14048180wrb.155.1531763057937; Mon, 16 Jul 2018 10:44:17 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a1c:3b09:0:0:0:0:0 with HTTP; Mon, 16 Jul 2018 10:44:17 -0700 (PDT) In-Reply-To: <20180714074829.GR5562@kib.kiev.ua> References: <20180714074829.GR5562@kib.kiev.ua> From: Jack Humphries Date: Mon, 16 Jul 2018 10:44:17 -0700 Message-ID: Subject: Re: tmpfs questions To: Konstantin Belousov Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2018 17:44:19 -0000 Thanks a lot, Konstantin. I also noticed that the tmpfs_mount structure is not necessarily protected by a lock when an access is made to the tm_nodes_inuse member in the if statement at the beginning of the tmpfs_alloc_node function in tmpfs_subr.c (though this member is protected by the allnode_lock when it is modified). Thus conceivably it is possible to create more nodes than the maximum number allowed if multiple threads try to do so at the same time. Do you know how this situation is handled? What am I looking at incorrectly? Thanks again! Jack On Sat, Jul 14, 2018 at 12:48 AM, Konstantin Belousov wrote: > On Fri, Jul 13, 2018 at 05:42:59PM -0700, Jack Humphries wrote: >> Hi everyone, >> >> I'm trying to study the FreeBSD tmpfs implementation as a personal >> project, and I had a couple questions. I've been looking through the >> code for a week and modifying various parts. I appreciate any help! >> >> 1. It seems that vnodes are locked before being passed to the various >> VOP functions in tmpfs (because there is a call to >> MPASS(VOP_ISLOCKED(vp)) near the beginning of each function). >> Therefore, is the implicit assumption that a thread that holds the >> vnode lock has exclusive access to the corresponding tmpfs_node >> struct? In other words, is this why there are accesses to the tmpfs >> node variables even though the tmpfs node is not locked? Note: I see >> tn_interlock, but based on a comment above it in the source, it only >> protects tn_vpstate and tn_status. > tmpfs nodes are protected by the vnode locks. Note that vnode lock > can be held exclusive or shared. Typically, only exclusive lock allows > the code to modify the node, owning shared vnode lock only means that > the node can be read safely. > > Interlock exists because node state must be examined sometimes without > owning the vnode lock, in non-sleepable context. > >> >> 2. What is the duplicate node list for (tn_dupindex)? If I had to >> guess, it seems to have something to do with the case where one thread >> calls readdir on a directory while another is modifying the directory, >> but I'm not sure. Can someone explain this deeper? > As an optimization, children of the directory node are organized into > red/black tree, which cannot hold two entries with the same key value. > If a second entry with the existing key is attempted to be created in > the directory, it is added to the dup list instead. From owner-freebsd-fs@freebsd.org Mon Jul 16 18:10:11 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B2BF1033A8E for ; Mon, 16 Jul 2018 18:10:11 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 EE61F7C573 for ; Mon, 16 Jul 2018 18:10:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w6GIA1aF085367 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Jul 2018 21:10:04 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w6GIA1aF085367 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w6GIA077085366; Mon, 16 Jul 2018 21:10:00 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 16 Jul 2018 21:10:00 +0300 From: Konstantin Belousov To: Jack Humphries Cc: freebsd-fs@freebsd.org Subject: Re: tmpfs questions Message-ID: <20180716181000.GA1876@kib.kiev.ua> References: <20180714074829.GR5562@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2018 18:10:11 -0000 On Mon, Jul 16, 2018 at 10:44:17AM -0700, Jack Humphries wrote: > Thanks a lot, Konstantin. I also noticed that the tmpfs_mount > structure is not necessarily protected by a lock when an access is > made to the tm_nodes_inuse member in the if statement at the beginning > of the tmpfs_alloc_node function in tmpfs_subr.c (though this member > is protected by the allnode_lock when it is modified). Thus > conceivably it is possible to create more nodes than the maximum > number allowed if multiple threads try to do so at the same time. Do > you know how this situation is handled? What am I looking at > incorrectly? Thanks again! Well, the problem is not in the lock-less check at the start of the tmpfs_alloc_node() function. Even if we checked under the lock, we still would drop it immediately after the check and this is where the problem is. Imagine that we have several threads allocating nodes for the same mount point, and the current count is at max - 1. All of them would pass the check, but also all of them would insert a new node into the mount. To correctly handle this case, the check must be done under the TMPFS_LOCK() at the end of the function, before the counter is incremented. I am not sure that rollback of the fully allocated node is worth possible minor overflow. > > Jack > > On Sat, Jul 14, 2018 at 12:48 AM, Konstantin Belousov > wrote: > > On Fri, Jul 13, 2018 at 05:42:59PM -0700, Jack Humphries wrote: > >> Hi everyone, > >> > >> I'm trying to study the FreeBSD tmpfs implementation as a personal > >> project, and I had a couple questions. I've been looking through the > >> code for a week and modifying various parts. I appreciate any help! > >> > >> 1. It seems that vnodes are locked before being passed to the various > >> VOP functions in tmpfs (because there is a call to > >> MPASS(VOP_ISLOCKED(vp)) near the beginning of each function). > >> Therefore, is the implicit assumption that a thread that holds the > >> vnode lock has exclusive access to the corresponding tmpfs_node > >> struct? In other words, is this why there are accesses to the tmpfs > >> node variables even though the tmpfs node is not locked? Note: I see > >> tn_interlock, but based on a comment above it in the source, it only > >> protects tn_vpstate and tn_status. > > tmpfs nodes are protected by the vnode locks. Note that vnode lock > > can be held exclusive or shared. Typically, only exclusive lock allows > > the code to modify the node, owning shared vnode lock only means that > > the node can be read safely. > > > > Interlock exists because node state must be examined sometimes without > > owning the vnode lock, in non-sleepable context. > > > >> > >> 2. What is the duplicate node list for (tn_dupindex)? If I had to > >> guess, it seems to have something to do with the case where one thread > >> calls readdir on a directory while another is modifying the directory, > >> but I'm not sure. Can someone explain this deeper? > > As an optimization, children of the directory node are organized into > > red/black tree, which cannot hold two entries with the same key value. > > If a second entry with the existing key is attempted to be created in > > the directory, it is added to the dup list instead. From owner-freebsd-fs@freebsd.org Tue Jul 17 00:46:26 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D782B10456BF for ; Tue, 17 Jul 2018 00:46:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6D93B8B5F1 for ; Tue, 17 Jul 2018 00:46:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 249F010456B0; Tue, 17 Jul 2018 00:46:26 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11E6B10456AE for ; Tue, 17 Jul 2018 00:46:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A28258B5EE for ; Tue, 17 Jul 2018 00:46:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CF50718610 for ; Tue, 17 Jul 2018 00:46:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6H0kO1d011133 for ; Tue, 17 Jul 2018 00:46:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6H0kOB3011132 for fs@FreeBSD.org; Tue, 17 Jul 2018 00:46:24 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 219049] ftruncate() slow on UFS+journaled softupdates Date: Tue, 17 Jul 2018 00:46:22 +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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: info@murrawhip.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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 00:46:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219049 --- Comment #10 from info@murrawhip.net --- I'm currently experiencing this again during an upgrade from 11.1 to 11.2. Changing debug.softdep.flushcache from its default 0 appears to have no eff= ect on the package extraction. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jul 17 10:20:58 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 328BB1035EF0 for ; Tue, 17 Jul 2018 10:20:58 +0000 (UTC) (envelope-from ganael.laplanche@martymac.org) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) (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 B868981A7E for ; Tue, 17 Jul 2018 10:20:57 +0000 (UTC) (envelope-from ganael.laplanche@martymac.org) X-Originating-IP: 193.54.192.15 Received: from dmc12.centralesupelec.fr (nat-personnel.rennes.supelec.fr [193.54.192.15]) (Authenticated sender: ganael.laplanche@martymac.org) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id B374E60003 for ; Tue, 17 Jul 2018 10:20:49 +0000 (UTC) From: Ganael Laplanche To: freebsd-fs@freebsd.org Subject: fpsync gains cpio(1) support Date: Tue, 17 Jul 2018 12:20:44 +0200 Message-ID: <3459157.rPZctSQzey@dmc12.centralesupelec.fr> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Spam-Level: X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 10:20:58 -0000 Hi Everyone, Maybe some of you know fpart(1) and fpsync(1), two utilities I wrote to parallelize rsync(1) passes (locally or through a cluster of SSH workers) and speed up big data migrations: https://github.com/martymac/fpart/ I am pleased to announce that fpsync(1) now supports cpio(1) natively, see: https://github.com/martymac/fpart/commit/ f4777ee3163f62d2dcd95b2a38df8603381c7584 That mode enables even more faster replication passes (useful during first passes, not the 'final' -cleaning- one). Since I've not yet tagged a new release, the FreeBSD port (sysutils/fpart) is not up-to-date yet, but the git version should build out-of-the box. I would be pleased to get feedback about that new feature, feel free to contact me if you have any remarks or questions :) Best regards, -- Ganael LAPLANCHE http://www.martymac.org | http://contribs.martymac.org FreeBSD: martymac , http://www.FreeBSD.org From owner-freebsd-fs@freebsd.org Tue Jul 17 14:58:37 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65AA51042C6D for ; Tue, 17 Jul 2018 14:58:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BDFEF8CB17 for ; Tue, 17 Jul 2018 14:58:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 77CA21042C69; Tue, 17 Jul 2018 14:58:36 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6651E1042C68 for ; Tue, 17 Jul 2018 14:58:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 061108CB13 for ; Tue, 17 Jul 2018 14:58:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E89971FC67 for ; Tue, 17 Jul 2018 14:58:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6HEwYOA066035 for ; Tue, 17 Jul 2018 14:58:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6HEwY6h066034 for fs@FreeBSD.org; Tue, 17 Jul 2018 14:58:34 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 229829] [zfs] scrubbing prevents shutdown and slows down startup Date: Tue, 17 Jul 2018 14:58: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: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 14:58:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229829 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jul 17 16:03:12 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67CE610452C1 for ; Tue, 17 Jul 2018 16:03:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EA2778F365 for ; Tue, 17 Jul 2018 16:03:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A903A10452C0; Tue, 17 Jul 2018 16:03:11 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 969DA10452BF for ; Tue, 17 Jul 2018 16:03:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 271898F363 for ; Tue, 17 Jul 2018 16:03:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 71A0220614 for ; Tue, 17 Jul 2018 16:03:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6HG3A25080772 for ; Tue, 17 Jul 2018 16:03:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6HG3AoI080770 for fs@FreeBSD.org; Tue, 17 Jul 2018 16:03:10 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 229829] [zfs] scrubbing prevents shutdown and slows down startup Date: Tue, 17 Jul 2018 16:03:10 +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: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2018 16:03:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229829 --- Comment #1 from Martin Birgmeier --- I now analyzed the startup time for scenario 3. This scenario continued as follows: - type "^c" - result: console shows "^c", otherwise no reaction, no command prompt - type "^zbg" - result: console shows "^zbg", otherwise no reaction, no command prompt - type "exit" - leave console unattended Using last(1) the time from typing "exit" to finding the corresponding "boot time" entry was 20 minutes. This most likely means that the pool import too= k 20 minutes to complete (I was not at the console anymore at that time). -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jul 19 11:10:07 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2626A102EB0E for ; Thu, 19 Jul 2018 11:10:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 977788B7E6 for ; Thu, 19 Jul 2018 11:10:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 528E5102EB0D; Thu, 19 Jul 2018 11:10:06 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 404A6102EB0C for ; Thu, 19 Jul 2018 11:10:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD1138B7E5 for ; Thu, 19 Jul 2018 11:10:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 0B00C16F42 for ; Thu, 19 Jul 2018 11:10:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6JBA4eZ078844 for ; Thu, 19 Jul 2018 11:10:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6JBA44f078843 for fs@FreeBSD.org; Thu, 19 Jul 2018 11:10:04 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 229829] [zfs] scrubbing prevents shutdown and slows down startup Date: Thu, 19 Jul 2018 11:10:05 +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: 11.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at 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 MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2018 11:10:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229829 --- Comment #2 from Martin Birgmeier --- Scenarios, continued: - server up, scrub of pool is continuing - gstat is running - 2 VirtualBox VMs are running - another VirtualBox VM is accessing a zvol via iSCSI (ctl) Result: - The machine freezes: not immediately, but process after process gets stuck Scenario continued: - After 30 minutes watching this, perform hard reset - Start single user - "fsck -p" -> cleans UFS root fs - issue "zpool export pool" in order to start multiuser without the pool be= ing imported Result: - The scrubbing starts again immediately, no command prompt Scenario continued: - Issue "ifconfig inet " into console buffer - Issue "ifconfig inet6 " into console buffer - On another machine, wait until ping succeeds Result: - First ping after ca. 20 minutes (see previous scenarios) - Console shows that 20G gmirror for swap has been rebuilt - pool is exported I am running with https://reviews.freebsd.org/D7538 applied because otherwi= se the system was slowly filling all swap space and swapping continuously, even with no activity. Something is very wrong in FreeBSD 11.2 with ZFS, swapping, and memory management. I did not have these problems with 11.1. -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jul 19 13:12:31 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81C301034DF9 for ; Thu, 19 Jul 2018 13:12:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1577990870 for ; Thu, 19 Jul 2018 13:12:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CA2701034DF5; Thu, 19 Jul 2018 13:12:30 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7E121034DF4 for ; Thu, 19 Jul 2018 13:12:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5538C90866 for ; Thu, 19 Jul 2018 13:12:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7FA2318127 for ; Thu, 19 Jul 2018 13:12:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6JDCTF0056216 for ; Thu, 19 Jul 2018 13:12:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6JDCT40056201 for fs@FreeBSD.org; Thu, 19 Jul 2018 13:12:29 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 229887] zfs quota related panic: solaris assert: 0 == dmu_tx_assign(tx, TXG_WAIT), Date: Thu, 19 Jul 2018 13:12:29 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2018 13:12:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229887 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Jul 19 14:36:43 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E4B4103C908 for ; Thu, 19 Jul 2018 14:36:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 116E994237 for ; Thu, 19 Jul 2018 14:36:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C2E37103C907; Thu, 19 Jul 2018 14:36:42 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AEC09103C903 for ; Thu, 19 Jul 2018 14:36:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45FD794231 for ; Thu, 19 Jul 2018 14:36:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 85F6918C3D for ; Thu, 19 Jul 2018 14:36:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6JEaf09036591 for ; Thu, 19 Jul 2018 14:36:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6JEafc6036590 for fs@FreeBSD.org; Thu, 19 Jul 2018 14:36:41 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 229887] zfs quota related panic: solaris assert: 0 == dmu_tx_assign(tx, TXG_WAIT), Date: Thu, 19 Jul 2018 14:36:41 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mav@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jul 2018 14:36:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229887 Alexander Motin changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |avg@FreeBSD.org --- Comment #1 from Alexander Motin --- The first panic indeed looks like combination of r334810 making dmu_tx_assi= gn() errors fatal and quota overflow causing that. We need to handle those erro= rs somehow. About second panic I am not sure, but I found such an interesting comment a= bove zfs_unlinked_add(): * When dealing with the unlinked set, we dmu_tx_hold_zap(), but we * don't specify the name of the entry that we will be manipulating. We * also fib and say that we won't be adding any new entries to the * unlinked set, even though we might (this is to lower the minimum file * size that can be deleted in a full filesystem). So on the small * chance that the nlink list is using a fat zap (ie. has more than * 2000 entries), we *may* not pre-read a block that's needed. * Therefore it is remotely possible for some of the assertions * regarding the unlinked set below to fail due to i/o error. On a * nondebug system, this will result in the space being leaked. Curios whether it can be the case here. --=20 You are receiving this mail because: You are the assignee for the bug.=