From owner-freebsd-fs@freebsd.org Sun Sep 1 13:07:43 2019 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 05CABD99A2 for ; Sun, 1 Sep 2019 13:07:43 +0000 (UTC) (envelope-from madpilot@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 46LtmZ6Rlcz4Hgc for ; Sun, 1 Sep 2019 13:07:42 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id DB687D99A0; Sun, 1 Sep 2019 13:07:42 +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 DB187D999E; Sun, 1 Sep 2019 13:07:42 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LtmZ5T0Vz4HgZ; Sun, 1 Sep 2019 13:07:42 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from marvin.madpilot.net (host193-122-dynamic.17-87-r.retail.telecomitalia.it [87.17.122.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4C1EC1BB7D; Sun, 1 Sep 2019 13:07:42 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) To: current@freebsd.org Cc: fs@FreeBSD.org From: Guido Falsi Subject: panic: No vop_need_inactive Message-ID: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> Date: Sun, 1 Sep 2019 15:07:39 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 13:07:43 -0000 Hi, I'm experiencing a recurring panic I can trigger repeatably. The machine is: FreeBSD 13.0-CURRENT r351604 amd64 The panic looks ZFS related. This machine performs mainly poudriere builds. I also use portshaker to manage the ports tree. Portshaker works by downloading ports trees and overlays in zfses, then snapshots them, clones them placing the clones in the poudriere namespace, then modifies the ports there applying the required overlays. This happens to me any time I run poudriere and after the build I run portshaker to update the ports trees, when it tries to remove the snapshot of the freebsd base tree (which AFAIK is the base for the clone where poudriere works). I'm going to try to create a more clear and detailed use case, removing from the equation complex programs like poudriere and portshaker. Here is the panic message: VNASSERT failed 0xfffff800abfcbd20: tag zfs, type VDIR usecount 0, writecount 0, refcount 1 mountedhere 0 flags (VI_ACTIVE) VI_LOCKed lock type zfs: UNLOCKED name = portshaker-2019-09-01:11:04:20 parent_id = 2 id = 269 panic: No vop_need_inactive(0xfffff800abfcbd20, 0xfffffe00ba39b3f0) cpuid = 2 time = 1567342436 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00ba39b310 vpanic() at vpanic+0x19d/frame 0xfffffe00ba39b360 panic() at panic+0x43/frame 0xfffffe00ba39b3c0 VOP_NEED_INACTIVE_APV() at VOP_NEED_INACTIVE_APV+0x8f/frame 0xfffffe00ba39b3e0 vputx() at vputx+0x1ae/frame 0xfffffe00ba39b440 vfs_mount_destroy() at vfs_mount_destroy+0x14f/frame 0xfffffe00ba39b470 dounmount() at dounmount+0x7e8/frame 0xfffffe00ba39b4d0 zfs_unmount_snap() at zfs_unmount_snap+0xbb/frame 0xfffffe00ba39b4f0 zfs_ioc_destroy_snaps() at zfs_ioc_destroy_snaps+0xb3/frame 0xfffffe00ba39b540 zfsdev_ioctl() at zfsdev_ioctl+0x54c/frame 0xfffffe00ba39b5e0 devfs_ioctl() at devfs_ioctl+0xc9/frame 0xfffffe00ba39b630 vn_ioctl() at vn_ioctl+0x13d/frame 0xfffffe00ba39b740 devfs_ioctl_f() at devfs_ioctl_f+0x1f/frame 0xfffffe00ba39b760 kern_ioctl() at kern_ioctl+0x1e4/frame 0xfffffe00ba39b7c0 sys_ioctl() at sys_ioctl+0x15d/frame 0xfffffe00ba39b890 amd64_syscall() at amd64_syscall+0x284/frame 0xfffffe00ba39b9b0 fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00ba39b9b0 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80049f2da, rsp = 0x7fffffffc948, rbp = 0x7fffffffc9c0 --- KDB: enter: panic Anyone can help? -- Guido Falsi From owner-freebsd-fs@freebsd.org Sun Sep 1 13:19:29 2019 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 5574FDA034 for ; Sun, 1 Sep 2019 13:19:29 +0000 (UTC) (envelope-from mjguzik@gmail.com) 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 46Lv286fNHz4JNw for ; Sun, 1 Sep 2019 13:19:28 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mailman.nyi.freebsd.org (Postfix) id E0E08DA031; Sun, 1 Sep 2019 13:19:28 +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 E0859DA02F; Sun, 1 Sep 2019 13:19:28 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lv285KGgz4JNr; Sun, 1 Sep 2019 13:19:28 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-oi1-x22c.google.com with SMTP id b80so1790822oii.7; Sun, 01 Sep 2019 06:19:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZzrL5hYZvv/o8oq9cvthFD/d8W+vKeBP5vtcWT2Gmmk=; b=SfxV4hsp+1e0opY9bEiahAiGr+52KzUqDYdRsL7gGWO4orI3QolA3TTq10yqHN9ZJ8 6BsDb+JU6Y2Zw2V7+ElN6pJn/lVSh9SVP2xbvcxy/ParWZIxjby3Sc99jRUPDPQF05dE KTQPRhNjC+SJgdRkwkpedIFn9JqhHfNLTPZigk1kPO1p/9FaCxKdadk4BhIBKqYsLbW4 wxtgtPx/c5M3LyVlQ939uHdY2ANHvML3qKmKcmDFqaBtl+WqJLOQYw/hTh4Cz9DFzvbI e/mWVDQyJcjxdFjm66k3wUP/s2dsGE+llL4YOcMTH8ec8oDMIK+cpcQuHCtZ0uXBuPE3 DX7Q== 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=ZzrL5hYZvv/o8oq9cvthFD/d8W+vKeBP5vtcWT2Gmmk=; b=Vjd3cNE2du0CSDPLv56M1umjiqkMhP4yeHLwtBtkeN/eMAHoum14w/6+OR686QmM8G +Gzl2wFxrlL1htOLRNFayJznVYjuAAY3UfiO6UPYd8MqbJdRnYNIyuj6yAFyKulHewRW GgdVcwd3p1t5HltO1LmJJIfSkO4Oo9w68Xn/f9t8FSGrU2ikiFhoDEbiIrCH9/oRuEko xWo5ztT+GK5cKH6JqhSvKw/03g4eOOSTt9YUHWWi7m4zr+kdkvnhabyg58euDvEEeHzn SK271OEKUcZDzS3zh02Vsmr+p0su3eI5yiHLufSquj5UoOSxEb3OYoyR+3Ovr2Gr1fjJ xH0w== X-Gm-Message-State: APjAAAV17UuihrymlCx3rNmjSaozhETxgVLdZZKolkkRXZ2IJW5WhB+f IaA0PBFfsoBLMB76Z7qReabixzRBtd6OUu+qkVa+4Q== X-Google-Smtp-Source: APXvYqx0fbi9BDO7o981kj/COQCaVeO4FkHz/aNzZwZ2Zagw4423W6lj6utgjnXd8222YRtN/60Qs9p4KG+VgEm62yM= X-Received: by 2002:a05:6808:7c1:: with SMTP id f1mr16475597oij.77.1567343966626; Sun, 01 Sep 2019 06:19:26 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4a:458d:0:0:0:0:0 with HTTP; Sun, 1 Sep 2019 06:19:25 -0700 (PDT) In-Reply-To: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> From: Mateusz Guzik Date: Sun, 1 Sep 2019 15:19:25 +0200 Message-ID: Subject: Re: panic: No vop_need_inactive To: Guido Falsi Cc: current@freebsd.org, fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 46Lv285KGgz4JNr X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.98 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.99)[-0.985,0] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 13:19:29 -0000 This is fixed in https://svnweb.freebsd.org/base?view=revision&revision=351642 On 9/1/19, Guido Falsi wrote: > Hi, > > I'm experiencing a recurring panic I can trigger repeatably. > > The machine is: > > FreeBSD 13.0-CURRENT r351604 amd64 > > The panic looks ZFS related. This machine performs mainly poudriere > builds. I also use portshaker to manage the ports tree. > > Portshaker works by downloading ports trees and overlays in zfses, then > snapshots them, clones them placing the clones in the poudriere > namespace, then modifies the ports there applying the required overlays. > > This happens to me any time I run poudriere and after the build I run > portshaker to update the ports trees, when it tries to remove the > snapshot of the freebsd base tree (which AFAIK is the base for the clone > where poudriere works). > > I'm going to try to create a more clear and detailed use case, removing > from the equation complex programs like poudriere and portshaker. > > > Here is the panic message: > > VNASSERT failed > 0xfffff800abfcbd20: tag zfs, type VDIR > usecount 0, writecount 0, refcount 1 mountedhere 0 > flags (VI_ACTIVE) > VI_LOCKed lock type zfs: UNLOCKED > name = portshaker-2019-09-01:11:04:20 > parent_id = 2 > id = 269 > panic: No vop_need_inactive(0xfffff800abfcbd20, 0xfffffe00ba39b3f0) > cpuid = 2 > time = 1567342436 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00ba39b310 > vpanic() at vpanic+0x19d/frame 0xfffffe00ba39b360 > panic() at panic+0x43/frame 0xfffffe00ba39b3c0 > VOP_NEED_INACTIVE_APV() at VOP_NEED_INACTIVE_APV+0x8f/frame > 0xfffffe00ba39b3e0 > vputx() at vputx+0x1ae/frame 0xfffffe00ba39b440 > vfs_mount_destroy() at vfs_mount_destroy+0x14f/frame 0xfffffe00ba39b470 > dounmount() at dounmount+0x7e8/frame 0xfffffe00ba39b4d0 > zfs_unmount_snap() at zfs_unmount_snap+0xbb/frame 0xfffffe00ba39b4f0 > zfs_ioc_destroy_snaps() at zfs_ioc_destroy_snaps+0xb3/frame > 0xfffffe00ba39b540 > zfsdev_ioctl() at zfsdev_ioctl+0x54c/frame 0xfffffe00ba39b5e0 > devfs_ioctl() at devfs_ioctl+0xc9/frame 0xfffffe00ba39b630 > vn_ioctl() at vn_ioctl+0x13d/frame 0xfffffe00ba39b740 > devfs_ioctl_f() at devfs_ioctl_f+0x1f/frame 0xfffffe00ba39b760 > kern_ioctl() at kern_ioctl+0x1e4/frame 0xfffffe00ba39b7c0 > sys_ioctl() at sys_ioctl+0x15d/frame 0xfffffe00ba39b890 > amd64_syscall() at amd64_syscall+0x284/frame 0xfffffe00ba39b9b0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe00ba39b9b0 > --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80049f2da, rsp = > 0x7fffffffc948, rbp = 0x7fffffffc9c0 --- > KDB: enter: panic > > > Anyone can help? > > > -- > Guido Falsi > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Mateusz Guzik From owner-freebsd-fs@freebsd.org Sun Sep 1 13:30:49 2019 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 92E47DA426 for ; Sun, 1 Sep 2019 13:30:49 +0000 (UTC) (envelope-from contact@evilham.com) 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 46LvHF1lzXz4K2t for ; Sun, 1 Sep 2019 13:30:49 +0000 (UTC) (envelope-from contact@evilham.com) Received: by mailman.nyi.freebsd.org (Postfix) id 38858DA425; Sun, 1 Sep 2019 13:30:49 +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 3835EDA423; Sun, 1 Sep 2019 13:30:49 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [IPv6:2a02:2770::216:3eff:fee1:cf9]) (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 46LvH91n0rz4K2g; Sun, 1 Sep 2019 13:30:44 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 46Lv8t2Cjpz3wpY; Sun, 1 Sep 2019 15:25:18 +0200 (CEST) From: Evilham To: Guido Falsi Cc: current@freebsd.org, fs@FreeBSD.org Subject: Re: panic: No vop_need_inactive References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> In-reply-to: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> Date: Sun, 01 Sep 2019 15:25:14 +0200 Message-ID: <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 46LvH91n0rz4K2g X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 2a02:2770::216:3eff:fee1:cf9 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-5.43 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-1.66)[ipnet: 2a02:2770::/32(-4.69), asn: 196752(-3.64), country: NL(0.01)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.96)[-0.965,0]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:2a02:2770::/32, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 13:30:49 -0000 On dg., set. 01 2019, Guido Falsi wrote: > Hi, > > I'm experiencing a recurring panic I can trigger repeatably. > > The machine is: > > FreeBSD 13.0-CURRENT r351604 amd64 > > The panic looks ZFS related. This machine performs mainly > poudriere > builds. I also use portshaker to manage the ports tree. > > Portshaker works by downloading ports trees and overlays in > zfses, then > snapshots them, clones them placing the clones in the poudriere > namespace, then modifies the ports there applying the required > overlays. > > This happens to me any time I run poudriere and after the build > I run > portshaker to update the ports trees, when it tries to remove > the > snapshot of the freebsd base tree (which AFAIK is the base for > the clone > where poudriere works). > > I'm going to try to create a more clear and detailed use case, > removing > from the equation complex programs like poudriere and > portshaker. > Interesting! I was going to send a similar email a few hours ago to the current ML but decided to debug some more before that. I use poudriere to manage my ports tree with svn, I do use ZFS. I can trigger the panic by running poudriere bulk on e.g. finance/gnucash. Some more info that may be related: - This worked fine on a build from the 2nd week of August, after r350551 (a fix for AMD Ryzen laptops). - Since that build had an issue with bhyve (as mentioned on this list a few days ago), I upgraded last week which started triggering this issue with poudriere - It still happens with: # uname -v FreeBSD 13.0-CURRENT r351654+209e505321db-c262365(master) GENERIC Which is posterior to r351642 that was mentioned by Mateusz. > Here is the panic message: > > VNASSERT failed > 0xfffff800abfcbd20: tag zfs, type VDIR > usecount 0, writecount 0, refcount 1 mountedhere 0 > flags (VI_ACTIVE) > VI_LOCKed lock type zfs: UNLOCKED > name = portshaker-2019-09-01:11:04:20 > parent_id = 2 > id = 269 > panic: No vop_need_inactive(0xfffff800abfcbd20, > 0xfffffe00ba39b3f0) > cpuid = 2 > time = 1567342436 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame > 0xfffffe00ba39b310 > vpanic() at vpanic+0x19d/frame 0xfffffe00ba39b360 > panic() at panic+0x43/frame 0xfffffe00ba39b3c0 > VOP_NEED_INACTIVE_APV() at VOP_NEED_INACTIVE_APV+0x8f/frame > 0xfffffe00ba39b3e0 > vputx() at vputx+0x1ae/frame 0xfffffe00ba39b440 > vfs_mount_destroy() at vfs_mount_destroy+0x14f/frame > 0xfffffe00ba39b470 > dounmount() at dounmount+0x7e8/frame 0xfffffe00ba39b4d0 > zfs_unmount_snap() at zfs_unmount_snap+0xbb/frame > 0xfffffe00ba39b4f0 > zfs_ioc_destroy_snaps() at zfs_ioc_destroy_snaps+0xb3/frame > 0xfffffe00ba39b540 > zfsdev_ioctl() at zfsdev_ioctl+0x54c/frame 0xfffffe00ba39b5e0 > devfs_ioctl() at devfs_ioctl+0xc9/frame 0xfffffe00ba39b630 > vn_ioctl() at vn_ioctl+0x13d/frame 0xfffffe00ba39b740 > devfs_ioctl_f() at devfs_ioctl_f+0x1f/frame 0xfffffe00ba39b760 > kern_ioctl() at kern_ioctl+0x1e4/frame 0xfffffe00ba39b7c0 > sys_ioctl() at sys_ioctl+0x15d/frame 0xfffffe00ba39b890 > amd64_syscall() at amd64_syscall+0x284/frame 0xfffffe00ba39b9b0 > fast_syscall_common() at fast_syscall_common+0x101/frame > 0xfffffe00ba39b9b0 > --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80049f2da, > rsp = > 0x7fffffffc948, rbp = 0x7fffffffc9c0 --- > KDB: enter: panic > FWIW: I am not 100% sure I it's the same panic, I am missing a cable ATM to get a full dump, but I do think they sound very similar. -- Evilham From owner-freebsd-fs@freebsd.org Sun Sep 1 13:50:17 2019 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 D3C59DAB97 for ; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Lvjj5G76z4L66 for ; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id B104CDAB93; Sun, 1 Sep 2019 13:50:17 +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 AF6B3DAB91; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lvjj2yvzz4L63; Sun, 1 Sep 2019 13:50:17 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from marvin.madpilot.net (host193-122-dynamic.17-87-r.retail.telecomitalia.it [87.17.122.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id D35F51C046; Sun, 1 Sep 2019 13:50:16 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Subject: Re: panic: No vop_need_inactive To: Evilham Cc: current@freebsd.org, fs@FreeBSD.org References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> From: Guido Falsi Message-ID: <67cc0491-2b4a-f166-7319-c6dce0bfee9d@FreeBSD.org> Date: Sun, 1 Sep 2019 15:50:15 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 13:50:17 -0000 On 01/09/19 15:25, Evilham wrote: > > FWIW: I am not 100% sure I it's the same panic, I am missing a cable ATM > to get a full dump, but I do think they sound very similar. I'm not using serial communications to get dumps, not necessary anymore. You can have the kernel debugger output this information to disk (in /var/crash) using the "textdump dump" command. You can also usse the capture buffer in ddb to perform other operations and have the screen output saved in a buffer. This is all documented in ddb(4) and textdump(4) (regarding the crash it has been reported as fixed in a later commit) -- Guido Falsi From owner-freebsd-fs@freebsd.org Sun Sep 1 13:51:22 2019 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 8BD64DAD0E for ; Sun, 1 Sep 2019 13:51:22 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Lvky364Xz4LKs for ; Sun, 1 Sep 2019 13:51:22 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 6A7BCDAD0C; Sun, 1 Sep 2019 13:51:22 +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 6A313DAD0A; Sun, 1 Sep 2019 13:51:22 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lvky27Rhz4LKr; Sun, 1 Sep 2019 13:51:22 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from marvin.madpilot.net (host193-122-dynamic.17-87-r.retail.telecomitalia.it [87.17.122.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id BC9871C047; Sun, 1 Sep 2019 13:51:21 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Subject: Re: panic: No vop_need_inactive To: Mateusz Guzik Cc: current@freebsd.org, fs@freebsd.org References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> From: Guido Falsi Message-ID: Date: Sun, 1 Sep 2019 15:51:20 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 13:51:22 -0000 On 01/09/19 15:19, Mateusz Guzik wrote: > This is fixed in https://svnweb.freebsd.org/base?view=revision&revision=351642 Thanks! I missed that one! -- Guido Falsi From owner-freebsd-fs@freebsd.org Sun Sep 1 18:41:07 2019 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 7803FE173C for ; Sun, 1 Sep 2019 18:41:07 +0000 (UTC) (envelope-from contact@evilham.com) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46M29H1crtz4dVW for ; Sun, 1 Sep 2019 18:41:07 +0000 (UTC) (envelope-from contact@evilham.com) Received: by mailman.nyi.freebsd.org (Postfix) id 35F2CE173A; Sun, 1 Sep 2019 18:41:07 +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 3570FE1738; Sun, 1 Sep 2019 18:41:07 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [46.19.33.155]) (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 46M29G1YC8z4dVS; Sun, 1 Sep 2019 18:41:05 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 46M29C53Mlz3x6X; Sun, 1 Sep 2019 20:41:03 +0200 (CEST) From: Evilham To: Guido Falsi Cc: current@freebsd.org, fs@FreeBSD.org Subject: Re: panic: No vop_need_inactive References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> In-reply-to: <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> Date: Sun, 01 Sep 2019 20:41:00 +0200 Message-ID: <51a6c6b2-5680-4431-bfc4-b351eaa07880@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 46M29G1YC8z4dVS X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 46.19.33.155 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-4.41 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-0.73)[asn: 196752(-3.66), country: NL(0.01)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_DN_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.88)[-0.878,0]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:196752, ipnet:46.19.32.0/21, country:NL]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 18:41:07 -0000 On dg., set. 01 2019, Evilham wrote: > On dg., set. 01 2019, Guido Falsi wrote: > >> Hi, >> >> I'm experiencing a recurring panic I can trigger repeatably. >> > > I was going to send a similar email a few hours ago to the > current > ML but decided to debug some more before that. > > FWIW: I am not 100% sure I it's the same panic, I am missing a > cable ATM to get a full dump, but I do think they sound very > similar. Awkward, my panic is gone after some fiddling around. I hope yours is indeed also gone after upgrading. -- Evilham From owner-freebsd-fs@freebsd.org Sun Sep 1 19:14:54 2019 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 00E79E2464 for ; Sun, 1 Sep 2019 19:14:54 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46M2wF659mz3CfS for ; Sun, 1 Sep 2019 19:14:53 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id CF146E2461; Sun, 1 Sep 2019 19:14:53 +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 CEBE8E245F; Sun, 1 Sep 2019 19:14:53 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46M2wF54M8z3CfQ; Sun, 1 Sep 2019 19:14:53 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Received: from tommy.madpilot.net (host193-122-dynamic.17-87-r.retail.telecomitalia.it [87.17.122.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: madpilot/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 271A81E752; Sun, 1 Sep 2019 19:14:53 +0000 (UTC) (envelope-from madpilot@FreeBSD.org) Subject: Re: panic: No vop_need_inactive To: Evilham Cc: current@freebsd.org, fs@FreeBSD.org References: <6d695bc6-37e3-e068-6620-dcd5616b2a5c@FreeBSD.org> <889667e1-9610-46c0-bd23-3e034f835d7f@yggdrasil.evilham.com> <51a6c6b2-5680-4431-bfc4-b351eaa07880@yggdrasil.evilham.com> From: Guido Falsi Autocrypt: addr=madpilot@FreeBSD.org; prefer-encrypt=mutual; keydata= mQENBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNjWIntsxuX fptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezrHPdRp7wdxi23GN80 qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUjgqJn+phDTdCFLvrSFdmgx4Wl c0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9gVv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+ wuREpRO4lKOkTnj9TtQJRiptlhcHQiAlG1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEB AAG0Ikd1aWRvIEZhbHNpIDxtYWRwaWxvdEBGcmVlQlNELm9yZz6JATYEEwEIACACGwMCHgEC F4AFAlLvzwUFCwkIBwMFFQoJCAsEFgIDAQAKCRAa5oYOVsvSk6EzCAC4ovSo6XF4x0spuKmp RzVuZ5ywqCJAfRIrJHpW8HjSPkcUYwmXVOE3zjul9j2C2eHPPGobEDN5FqovAtzb7HdYGGcU aUdhDApUMMRVkzflwb23C/CI1RBcZxjC0noajSKgbIHx4+Afg6CFMgpngq+NJwEaaVrKlYzq G+KcfeVKAdwlWHJOgQJIEylUtwtBqXx/iJDrGwKO5A6a1uSEZrZfuwjSh8cBqoUfIwLZUIFE HBjHa8pUkp8mWx7JaZ19vBF6pDpPVZSoLSg8stWd1DPesn/qySYgtSGSY6hpWABVF98HRsBG +VXlHtqCaB0j0cGCDhCpHQUI10oGGc8k4zcvuQINBFMQe0EBEAChYaw3HqD3SvyBw0pqI+kk GIrLzO1XYXJXkuxPQ6BAFbe8jG3+h22zFU02OnJL8E1kLLMsCwVzVasYHOFiyY831IYHn/lh O+TN/lhWJTlUCxmWP8xFYJmta2mJzhzQDs3hyw5hF422T+rxgHg8gWxn0D6RO6hmGe7m3k91 8EDvj5JXAq7zj49mT3AMRjUtsVVPy8zjagqyaizCUiHAnbG4kj+BuT5wxR7TKJGk2OjhK/Dh EHzgHq4XB1Gv8+1LvGLZmqih/kBpBP1hIGkakok579CTkw/g8XoWqr6Cjz2fvtjaQmTBwdou gP8Yn5kMBIiIxF7XLngUc5DVEJMYamcktd0q4aHC/cnbWlTwc2WrQBI1AwxCZgDC1RbOOan8 oTIjWqRyaNp9zFvxOaJqgrxJA3Vl/3p9z+witk3pnmg4ITLIJDSmsf89MDaOVGQpDjzs9MaT YlIpTlW5Lns2WTYOue+NanntpX14UCGmeusk+4aYXPzf89zyALS3s3uLtVUdhFwLmdrFgHZS gjU5STLGlP8e9AVddVnf8qZ1czOvHX3UCCAI9YjBQA/5VxpRFJil4OTr9lUA5U57UKGpwmKw IPvArbT8468nYC2Rat4a7UJn3NLHucr9Vh0uvfgbFDhtPUb72sFA2cVI1tfZMnjfUx2jUYKM N5ErgK1Kes0piQARAQABiQEfBBgBCAAJBQJTEHtBAhsMAAoJEBrmhg5Wy9KTDecIAOGwpF/6 sBFQtOk6HkegtqbrZklkDIKQ2qq7+uR7m6PkBpoNj+HsE2EEOIOqGFktN6h8alVVoSs+xY36 1fnR/Kmwi30oCHL3QYWu2shmVa7IrjCyhm8N+n3JpGT6Ugznx3D9Fx/GfrvQlo9MVJE8QJWf +4uoGElKRtiVjbXZhP1/FVRMl7rAi8MtCtASOtAP+HUUyF9wuECqyd2W1F3oM+9Mp4x3/pUD GfSGSgEqETLkuRaMz0Iemm75sGRD3X+SPa4lBJc7x66ifAcdLdz7o3aLYfsjR6Zwca7TvC5E Ha0OfD9EsHGiF9909lPaRvG4buWFUfPBUPDkNHBLDwaQ53K5AQ0ET4b6XQEIALHepqzqtRkm cJc0bHDUGvVtlgf904+DjeDy9nvQfoXPZU/58tswd2oF7ucG7F088MYCaUE+4TR5AknJFvfI dx0YxX4WTzQoCJ7lBrI3DclYLkIfv+O3JIaYdLO1PugeMjbiIqkGZOJqPFoAjY9WCIoVZhlh LIAzsDGmo2w2GdK9f9xpCpWIzl3lLk/1oKLq60keaGSVTQP5OF9h+zNyVK9QUnN9i+wSbfDO wJ7bpepNeydC/BppLy701LUEzvqfg2EDJ2tp4A9z2wL0EXGxBp5IPQAa3RBdFqeBsfoBhlrM hSpR7z3TLYFgMtybEvq0GqRui6Ft8lCacKRKQPOinQcAEQEAAYkBHwQoAQgACQUCUxB9DQId AQAKCRAa5oYOVsvSkzGXCADErInRheCqYxnCs4ZDStLBKXr3HpUOg84E+5HF7qui0OmDq26H 9vyj4Bonvf06BWXyVx/MxORnn6pCrx2W2LLFopRb5CPdBfZ9d/JBttOTQf9s5WkG++P7/WTF yV3IqZyMfk9rTjAgYByVONSDCZgfjX0beQOgg8rSXYVsaqabBKOY48v+7STNTZ+OxvO7QFfK lTVLc20us3Z2xweFtgScAjm21b/HqS94bvy+Xn1do9rUm1U5sryvwpWDAanbVKN7j1++Rhfy rmAwjj9QUwOc85s6eDzFXfoJh3DIAmSmOpb3BLXYuRSyNMHtpHGPH3z7zNnejDYRbBi2lSPe SdKKiQEfBBgBAgAJBQJPhvpdAhsMAAoJEBrmhg5Wy9KTNfEH/R0zTYbvDdCEirZkfJYD4Sbr vPazhGvCihGra+H0O4C/oZmDhKmf8hy3D0LxsWwJS0exdEoXirwBJOAdWhcBlCz6NEs7jtHf 1rVTBGxmveSU5v+pn4spljJVn/FInw9TAys8z0ezptMm3qDzPEv0UE26FFNVi6cHeJoPaVSZ StMa+eRjkhzX+Ju0vj9ZL5d8YJhI9eM1TKvciQTVhZbECuXIon4e7BaX7sVnRFW7YCHcacyJ ii10iwNLzq6CgL8RUxgawat78VenlJmisneR221no5mn2NbmuXXJ3sPZcaVii3apAtu1bdAp Lvi7U2N99uVfgQoZ3MDXCSUuyDJgc+s= Message-ID: Date: Sun, 1 Sep 2019 21:14:50 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 MIME-Version: 1.0 In-Reply-To: <51a6c6b2-5680-4431-bfc4-b351eaa07880@yggdrasil.evilham.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 19:14:54 -0000 On 01/09/19 20:41, Evilham wrote: > On dg., set. 01 2019, Evilham wrote: > >> On dg., set. 01 2019, Guido Falsi wrote: >> >>> Hi, >>> >>> I'm experiencing a recurring panic I can trigger repeatably. >>> >> >> I was going to send a similar email a few hours ago to the current >> ML but decided to debug some more before that. >> >> FWIW: I am not 100% sure I it's the same panic, I am missing a >> cable ATM to get a full dump, but I do think they sound very >> similar. > > Awkward, my panic is gone after some fiddling around. > I hope yours is indeed also gone after upgrading. Yes, the upgrade worked, at least that's what I have seen in the few tests I made since. -- Guido Falsi From owner-freebsd-fs@freebsd.org Sun Sep 1 21:00:20 2019 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 A1BFFE4F94 for ; Sun, 1 Sep 2019 21:00:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46M5Fw3pNSz3KPt for ; Sun, 1 Sep 2019 21:00:20 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 76D8DE4F92; Sun, 1 Sep 2019 21:00:20 +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 7677BE4F91 for ; Sun, 1 Sep 2019 21:00:20 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46M5Fw1mkhz3KPn for ; Sun, 1 Sep 2019 21:00:20 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 218667556 for ; Sun, 1 Sep 2019 21:00:20 +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 x81L0KM3050195 for ; Sun, 1 Sep 2019 21:00:20 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x81L0KbB050194 for fs@FreeBSD.org; Sun, 1 Sep 2019 21:00:20 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201909012100.x81L0KbB050194@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, 1 Sep 2019 21:00:20 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 21:00:20 -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 Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS Open | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data Open | 235665 | panic: handle_written_inodeblock: live inodedep Open | 237067 | ZFS: Crash in vdev_dtl_reassess when using GELI w 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun Sep 1 21:09:27 2019 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 22A2AE6064 for ; Sun, 1 Sep 2019 21:09:27 +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 46M5SR0BQVz3Ls7 for ; Sun, 1 Sep 2019 21:09:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 045C9E6063; Sun, 1 Sep 2019 21:09:27 +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 0426AE6062 for ; Sun, 1 Sep 2019 21:09:27 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46M5SQ6M2Zz3Ls6 for ; Sun, 1 Sep 2019 21:09:26 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BAE807801 for ; Sun, 1 Sep 2019 21:09:26 +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 x81L9Qdv093787 for ; Sun, 1 Sep 2019 21:09:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x81L9QjT093782 for fs@FreeBSD.org; Sun, 1 Sep 2019 21:09:26 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 233849] r339008 broke repquota on UFS Date: Sun, 01 Sep 2019 21:09:24 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sef@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sef@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12+ 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Sep 2019 21:09:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233849 --- Comment #11 from Sean Eric Fagan --- My question is does this need to go into 11/stable? I don't have the test systems for this any longer, which makes me a bit hesitant, but I can't try= to reproduce them. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Mon Sep 2 01:27:43 2019 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 764FDCCC8F for ; Mon, 2 Sep 2019 01:27:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46MCBR2cGpz45P8 for ; Mon, 2 Sep 2019 01:27:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 57BBBCCC8D; Mon, 2 Sep 2019 01:27:43 +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 57833CCC8B for ; Mon, 2 Sep 2019 01:27:43 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MCBR1jp7z45P5 for ; Mon, 2 Sep 2019 01:27:43 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1EA0FA6AE for ; Mon, 2 Sep 2019 01:27:43 +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 x821RhoS019920 for ; Mon, 2 Sep 2019 01:27:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x821Rhtg019919 for fs@FreeBSD.org; Mon, 2 Sep 2019 01:27:43 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 221077] Boot from ZFS fails following freebsd-update Date: Mon, 02 Sep 2019 01:27:42 +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: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwb@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 01:27:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 Jason W. Bacon changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Works As Intended Status|New |Closed --- Comment #25 from Jason W. Bacon --- I think this is some sort of conflict between ZFS and certain hardware RAID controllers. Creating separate volumes for each disk and using RAIDZ inste= ad of installing a ZFS filesystem on top of a hardware RAID config seems to av= oid the issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Sep 2 04:05:22 2019 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 10C18CFEDE for ; Mon, 2 Sep 2019 04:05:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46MGhK6khYz4CZ7 for ; Mon, 2 Sep 2019 04:05:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E4E4ECFEDC; Mon, 2 Sep 2019 04:05:21 +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 E3951CFEDB for ; Mon, 2 Sep 2019 04:05:21 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MGhK5Vbcz4CZ6 for ; Mon, 2 Sep 2019 04:05:21 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9F209C58D for ; Mon, 2 Sep 2019 04:05:21 +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 x8245LbR002763 for ; Mon, 2 Sep 2019 04:05:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x8245Leo002762 for fs@FreeBSD.org; Mon, 2 Sep 2019 04:05:21 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 233849] r339008 broke repquota on UFS Date: Mon, 02 Sep 2019 04:05:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: philip@abv.bg X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sef@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12+ 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 04:05:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233849 Philip Petrov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |philip@abv.bg --- Comment #12 from Philip Petrov --- I can confirm this bug on my end still exists: root@srv2:~ # repquota / Block limits=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 File limits User used soft hard grace used=20= =20=20 soft hard grace root -- 18505800 0 0 - 843339= =20=20=20=20=20 0 0 - root@srv2:~ # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 11.3-RELEASE from update2.freebsd.org... do= ne. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 11.3-RELEASE-p3. root@srv2:~ # uname -v FreeBSD 11.3-RELEASE-p2 #0: Tue Aug 6 05:07:20 UTC 2019=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Mon Sep 2 06:03:09 2019 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 981C1D2532 for ; Mon, 2 Sep 2019 06:03:09 +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 46MKJF3VDQz4J1b for ; Mon, 2 Sep 2019 06:03:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 77D1DD2531; Mon, 2 Sep 2019 06:03:09 +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 7798CD2530 for ; Mon, 2 Sep 2019 06:03:09 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MKJF2PDmz4J1Z for ; Mon, 2 Sep 2019 06:03:09 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 35DB0DAD3 for ; Mon, 2 Sep 2019 06:03:09 +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 x82639U0040301 for ; Mon, 2 Sep 2019 06:03:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x82639YA040296 for fs@FreeBSD.org; Mon, 2 Sep 2019 06:03:09 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 233849] r339008 broke repquota on UFS Date: Mon, 02 Sep 2019 06:03:09 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mail@fbsd.e4m.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sef@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12+ 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 06:03:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233849 --- Comment #13 from Andre Albsmeier --- > My question is does this need to go into 11/stable?=20 Yes. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Mon Sep 2 10:30:24 2019 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 4F1F7D959A for ; Mon, 2 Sep 2019 10:30:24 +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 46MRDc1TVgz4Y2w for ; Mon, 2 Sep 2019 10:30:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 30937D9599; Mon, 2 Sep 2019 10:30:24 +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 30555D9598 for ; Mon, 2 Sep 2019 10:30:24 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MRDc0SPJz4Y2t for ; Mon, 2 Sep 2019 10:30:24 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id E8A8A18A9E for ; Mon, 2 Sep 2019 10:30:23 +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 x82AUN5o076449 for ; Mon, 2 Sep 2019 10:30:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x82AUNBK076448 for fs@FreeBSD.org; Mon, 2 Sep 2019 10:30:23 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 221077] Boot from ZFS fails following freebsd-update Date: Mon, 02 Sep 2019 10:30:08 +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: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: 000.fbsd@quip.cz X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 10:30:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 Miroslav Lachman <000.fbsd@quip.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |000.fbsd@quip.cz --- Comment #26 from Miroslav Lachman <000.fbsd@quip.cz> --- (In reply to Jason W. Bacon from comment #25) Why this was closed?=20 If ZFS stopped working after some update procedure then there is a bug. It is true that it is better to run ZFS pool on top of individual disks but= it definitely should work on top of any GEOM or RAID device without this kind = of failure. I am using ZFS from the early days on FreeBSD always on individual disks but this year I was forced to maintain one system on similar configuration like= in this PR - ZFS pool on top of some Avago RAID card which cannot expose individual disk devices.=20 It is working fine now but what it will do after system upgrade? (running 1= 1.2 now) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Sep 2 13:18:05 2019 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 28EB0DDAA1 for ; Mon, 2 Sep 2019 13:18:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46MVy50M1fz3DmV for ; Mon, 2 Sep 2019 13:18:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0A014DDAA0; Mon, 2 Sep 2019 13:18:05 +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 09C43DDA9F for ; Mon, 2 Sep 2019 13:18:05 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MVy46XNrz3DmT for ; Mon, 2 Sep 2019 13:18:04 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C4EEC1A907 for ; Mon, 2 Sep 2019 13:18:04 +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 x82DI4fH042010 for ; Mon, 2 Sep 2019 13:18:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x82DI4QS042009 for fs@FreeBSD.org; Mon, 2 Sep 2019 13:18: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 221077] Boot from ZFS fails following freebsd-update Date: Mon, 02 Sep 2019 13:18:03 +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: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwb@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 13:18:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 --- Comment #27 from Jason W. Bacon --- I think proximity of the original failure to an update was a coincidence. = I've since seen a couple of systems fail randomly in the absence of updates, and= one (HP Proliant) simply would not work from the beginning with ZFS on a hardwa= re RAID. After configuring each disk as a separate volume in the RAID control= ler, everything was fine. You're welcome to reopen the PR if you want to pursue= it further. Very few people run ZFS on top of a hardware RAID, though, so it = may be difficult to support. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Sep 2 16:49:01 2019 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 D9490E2C8C for ; Mon, 2 Sep 2019 16:49:01 +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 46MbdT5Pf4z41Pc for ; Mon, 2 Sep 2019 16:49:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id B7BBCE2C8B; Mon, 2 Sep 2019 16:49:01 +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 B7846E2C8A for ; Mon, 2 Sep 2019 16:49:01 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MbdT4Nrgz41PY for ; Mon, 2 Sep 2019 16:49:01 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7A1E91D084 for ; Mon, 2 Sep 2019 16:49:01 +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 x82Gn1pe066410 for ; Mon, 2 Sep 2019 16:49:01 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x82Gn1o7066409 for fs@FreeBSD.org; Mon, 2 Sep 2019 16:49:01 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 221077] Boot from ZFS fails following freebsd-update Date: Mon, 02 Sep 2019 16:49:00 +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: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: 000.fbsd@quip.cz X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Sep 2019 16:49:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 --- Comment #28 from Miroslav Lachman <000.fbsd@quip.cz> --- (In reply to Jason W. Bacon from comment #27) If I have a choice I will choose individual disks but this machine is rented one without any choice to configure it differently. Tech support told us controller does not support JBOD. Anyway - what is the root cause of the ZFS pool failure? Only the boot reco= rds are damaged or the whole pool and data on it are crushed? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Sep 3 04:51:05 2019 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 2974CCA3B2 for ; Tue, 3 Sep 2019 04:51:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Mvfd0L5rz3JX5 for ; Tue, 3 Sep 2019 04:51:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0B830CA3B1; Tue, 3 Sep 2019 04:51:05 +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 0B46ACA3B0 for ; Tue, 3 Sep 2019 04:51:05 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Mvfc6TCPz3JX4 for ; Tue, 3 Sep 2019 04:51:04 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C1B3F2553B for ; Tue, 3 Sep 2019 04:51:04 +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 x834p4Ku029652 for ; Tue, 3 Sep 2019 04:51:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x834p4dJ029651 for fs@FreeBSD.org; Tue, 3 Sep 2019 04:51:04 GMT (envelope-from bugzilla-noreply@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: [Bug 233849] r339008 broke repquota on UFS Date: Tue, 03 Sep 2019 04:51:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sef@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12+ 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Sep 2019 04:51:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233849 --- Comment #14 from commit-hook@freebsd.org --- A commit references this bug: Author: sef Date: Tue Sep 3 04:50:39 UTC 2019 New revision: 351730 URL: https://svnweb.freebsd.org/changeset/base/351730 Log: MFC r343881, r343882 r339008 broke repquota for UFS. This rectifies that. PR: 233849 Changes: _U stable/11/ stable/11/lib/libutil/quotafile.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Sep 3 04:53:47 2019 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 BADE3CA864 for ; Tue, 3 Sep 2019 04:53:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Mvjl4WYmz3Jth for ; Tue, 3 Sep 2019 04:53:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 9B106CA863; Tue, 3 Sep 2019 04:53:47 +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 9AD24CA862 for ; Tue, 3 Sep 2019 04:53:47 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Mvjl3djMz3Jtg for ; Tue, 3 Sep 2019 04:53:47 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 618C4256D6 for ; Tue, 3 Sep 2019 04:53:47 +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 x834rl5B037864 for ; Tue, 3 Sep 2019 04:53:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x834rlnb037863 for fs@FreeBSD.org; Tue, 3 Sep 2019 04:53:47 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 233849] r339008 broke repquota on UFS Date: Tue, 03 Sep 2019 04:53:47 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.2-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: sef@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: sef@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? mfc-stable12+ 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Sep 2019 04:53:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233849 --- Comment #15 from Sean Eric Fagan --- Ok, I MFC'd the two patches. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Sep 4 19:35:36 2019 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 0A34ACB445 for ; Wed, 4 Sep 2019 19:35:36 +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 46NvDl6ShLz3JZp for ; Wed, 4 Sep 2019 19:35:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id D4C03CB444; Wed, 4 Sep 2019 19:35:35 +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 D4809CB443 for ; Wed, 4 Sep 2019 19:35: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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46NvDl5Frtz3JZk for ; Wed, 4 Sep 2019 19:35:35 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 988F4206E5 for ; Wed, 4 Sep 2019 19:35: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 x84JZZxj091347 for ; Wed, 4 Sep 2019 19:35:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x84JZZIH091346 for fs@FreeBSD.org; Wed, 4 Sep 2019 19:35: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 228750] panic on zfs mirror removal Date: Wed, 04 Sep 2019 19:35:34 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2019 19:35:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 miguelmclara@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |miguelmclara@gmail.com --- Comment #20 from miguelmclara@gmail.com --- Sorry to bring this up again but was this fixed on 12.0 too? I just removed a device and I did see the message in status about stating to remove it but then it panics with a similar error, only n my case I see: panic: solaris assert: ((offset) & ((1ULL << vd->vdev_ashift) - 1)) =3D=3D = 0 (0xa00 =3D=3D 0x0), file /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/metaslab.c, line: 3= 561 The fact that it shoes vdev_ashift leads me to believe that the cause is slightly different but still related to device removal. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Wed Sep 4 23:04:09 2019 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 41FDED07AB for ; Wed, 4 Sep 2019 23:04:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46NzsP112hz40PN for ; Wed, 4 Sep 2019 23:04:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 209B7D07AA; Wed, 4 Sep 2019 23:04:09 +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 205E2D07A9 for ; Wed, 4 Sep 2019 23:04:09 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46NzsP02zhz40PL for ; Wed, 4 Sep 2019 23:04:09 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D969A22D2C for ; Wed, 4 Sep 2019 23:04:08 +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 x84N48DE099885 for ; Wed, 4 Sep 2019 23:04:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x84N48Tc099884 for fs@FreeBSD.org; Wed, 4 Sep 2019 23:04:08 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 228750] panic on zfs mirror removal Date: Wed, 04 Sep 2019 23:04:08 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: panic X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: miguelmclara@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mav@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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Sep 2019 23:04:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228750 --- Comment #21 from miguelmclara@gmail.com --- Imported in read only and I see: remove: Evacuation of label/zfs1 in progress since Wed Sep 4 17:37:55 2019 29.5K copied out of 837G at 1/s, 0.00% done, (copy is slow, no estimated time) But also with zdb I can see that ashift is not the same and I'm guessing th= at's why I get the panic: metaslab_array: 33 metaslab_shift: 33 ashift: 9 asize: 1000199946240 is_log: 0 removing: 1 I suppose its probably easier to rebuild the pool --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Sep 5 21:27:43 2019 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 92F4CD420A for ; Thu, 5 Sep 2019 21:27:43 +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 46PYgg3NCGz4PBQ for ; Thu, 5 Sep 2019 21:27:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 72168D4209; Thu, 5 Sep 2019 21:27:43 +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 71D18D4208 for ; Thu, 5 Sep 2019 21:27:43 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PYgg0wRMz4PBN for ; Thu, 5 Sep 2019 21:27:43 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 03742A634 for ; Thu, 5 Sep 2019 21:27:43 +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 x85LRgLb090150 for ; Thu, 5 Sep 2019 21:27:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x85LRgOw090149 for fs@FreeBSD.org; Thu, 5 Sep 2019 21:27:42 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 210316] panic after trying to r/w mount msdosfs on write protected media Date: Thu, 05 Sep 2019 21:27:40 +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: cem@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: cem@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_file_loc assigned_to bug_status 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Sep 2019 21:27:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210316 Conrad Meyer changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://reviews.freebsd.org | |/D21539 Assignee|fs@FreeBSD.org |cem@freebsd.org Status|New |In Progress --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Sep 6 10:44:57 2019 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 D6859EFE1D for ; Fri, 6 Sep 2019 10:44:57 +0000 (UTC) (envelope-from mail@florian-schulze.net) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (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 46PvMS1zF7z4BHX; Fri, 6 Sep 2019 10:44:51 +0000 (UTC) (envelope-from mail@florian-schulze.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 64A5222223; Fri, 6 Sep 2019 06:44:51 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 06 Sep 2019 06:44:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= florian-schulze.net; h=from:to:cc:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s=fm1; bh= HNGgstATYar7EFWr3VYoJ4c789KV29q73rqXi3ozWGQ=; b=0/VsvBn1caH4gF7I Um7WRel21kPS7qvaDr2e0V7tSRxs2mSpRwFsaA5SYi8XwyF+mVxxVOf1gVyT22HS TrA5OPn6fhUKD/Ys8ggCdM88nbt15Is33woIbhykUAt2KV7mF/ceufjd9cpxnmz4 7JegGLpPEU6/bv1rueZ1Gy4AC2ya6BXTw+bQCO3iF2SzL1F9Eh0cIgnMhd7+uonV vdeWOVH71D0gEGolHEyCFDz1LOS0LfUChLu9co7C/B2anDKJciuQ8JTYJ7TML/zJ Rz8JIhanDXBA//LkAEVubRuDYyLX0quWoGQYSgHfkTqeyEckyUAt01yuVWbQT4Tu VuHOug== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=HNGgst ATYar7EFWr3VYoJ4c789KV29q73rqXi3ozWGQ=; b=vfBFGKXY2tQi6tLXOCI/zj yjVQEV7HvEE4m9UaRuF9Egt8p6hvLLkeyjPwuWTk0sv7WyaAln5gPNbuj9xzEqTj xv/OSdwTppBVFvctw5qLto0K/nHpVh+XRBDRicCx/EF7Lg1xIxfujfa9tbo0RU/K cPVBhAxPyXqJEMtrCd1xWgfHnxHHkfYC7aTFzUTJX9lwftILGyG0ZN89j+UkRUmX mp4c0BPlroz2DbD1NF+gs7FugD6TwUMsMZ76PoTDWPBIj2KVbMUY1K0SYyl7/gNQ YeFVjWsbE+EYiofHGOpnz1r/rCVYnIGVla5FUR3CDL3zHzxuSzonpQQMY6awGTmA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejledgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfggtgfgsehtqhhmtd ertddtnecuhfhrohhmpedfhfhlohhrihgrnhcuufgthhhulhiivgdfuceomhgrihhlsehf lhhorhhirghnqdhstghhuhhliigvrdhnvghtqeenucffohhmrghinhepghhithhhuhgsrd gtohhmnecukfhppeejledrvdeghedrheekrddukeejnecurfgrrhgrmhepmhgrihhlfhhr ohhmpehmrghilhesfhhlohhrihgrnhdqshgthhhulhiivgdrnhgvthenucevlhhushhtvg hrufhiiigvpedt X-ME-Proxy: Received: from [192.168.1.182] (p4ff53abb.dip0.t-ipconnect.de [79.245.58.187]) by mail.messagingengine.com (Postfix) with ESMTPA id 230038005C; Fri, 6 Sep 2019 06:44:50 -0400 (EDT) From: "Florian Schulze" To: freebsd-fs@freebsd.org Cc: kib@freebsd.org, mgj@freebsd.org Subject: held file reference issue with ZFS and nullfs Date: Fri, 06 Sep 2019 12:44:46 +0200 X-Mailer: MailMate (1.12.5r5635) Message-ID: <45B080A9-DE0F-4633-91F8-71438408D4B8@florian-schulze.net> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable Autocrypt: addr=mail@florian-schulze.net; keydata=mQENBFliSUoBCADLKPuy1qhTI+A3XRleyZ7WlXhRfYiXBCSMiIqUb+nx88xKLVAclRJqMnqlJHzAJcb4JW9i3riRU+V1rVG9BDaBCCih5Si0BQO5W84SpaadTdcE3rUO8Ihdxc6dJN9DiAtp26WyO1fXSA2NkwpakIerxlF91knkrnSa/VgLrlB+Ahtcisbsn9XYSnv0wr/njQJOfJMsmJfWAKXWWaWDWb0Z4/UITsBe259Ppkf6bTYS3j7oCPqygPzdyc14ILINb0N3ksT3tKLiS4b2gh7RAO4uf/C8TvlZSYvoX/sel5xFFxcgmqG+V0d4jjhdvY5zFHU+/Egr5y3HPgSQjevEHsNxABEBAAG0KkZsb3JpYW4gU2NodWx6ZSA8bWFpbEBmbG9yaWFuLXNjaHVsemUubmV0PokBOQQTAQgAIwUCWWJJSgIbAwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEC0N2jSLcB7qWo4H/jEgS6Id1TkRtlh+vZanpswS83sH8pOfc20qHbPEM2a1pk9aEgvvnckaeLiGVYaHKZccxRaE2E6zGKW26sI5WPcMehCZkiYf4zxfoppWsWDIGAsuptByHT+etkQVEANwNdDM5hIn4Hq0e6gsH1zu68SBhH4FtW4+ukCK3WrHZ0QJBoECU1otWxhP5BqOO8h9OCY2vESxHC2nH+y3vsqVL43JQWmBUv7uaaX4OusdWUZCW8jlYnWd//cmt3RKHh4PCKY7JK0itzoUi+DnnHBN7jxz2FFjX3+BinUeZX3bpXQhw3Xsv1ZXW9aeyGLgzYOuLdBSXmXJcetyJ0heCrOwZUS5AQ0EWWJJSgEIANlJdoChOEMMB7vh3YB0HjrBpK2+iyWC1Y1VCWOpKg/PiYq5GmZDMh1SGq+s/3ZVG5kAYcSKqdHSBqC8sRjY/gU/hysR3w9IU0J5/j1jTFZsw09vTfloEVRAJaAEyOAKvgUw+ fwiGhJsJPS9W8dqieVovqft5DpzNIBztPJxfiDrlHvKbxrwyCEW9+EAHMVJf7F6wqp0rAnlxZQujasL7Urx1Kl0RKT9HT8QHyzTJFpbpuO0hApiWCWD5GCy3AIc0KK3jJIz3ODCVFSGhbLiV0j9FB4j3wmM5JSvsyMhLZAkaFy/kqmlaVeroLWMBbmKUfEA968b37O+kILc3iXYQmMAEQEAAYkBHwQYAQgACQUCWWJJSgIbDAAKCRAtDdo0i3Ae6oyuB/4rh42bgTYncPkMv0l9jsKTB61wwe2Imxfxd52Gk3Ev5slaSFYl2r2FwhTFCX5Ay5XXqoueIG2AlZY2do7jnuLW66dye4GAI67PgKkZfzWJqD+q3bOimnmdlyKM1x2AxGnwPBEdjc4sShFm/uPOPPGJu4f8I9PKjGI62RJUCGHN9KxYJclomhNYe6n1xDsF0e3lDEtWn+KL1WesHO/NY2Mv//qGs9dqIu7rdAXrXiBQaSUz8ol0o4Z924qEWX+23tlWn3XLZPbFPJAB8sPHKWapt3nR/zaPJqfqkqwKWnWFdiKaKIB9GhlXmBlq+0alpjNjbicGlOF1YGF4agbFyoCb X-Rspamd-Queue-Id: 46PvMS1zF7z4BHX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=florian-schulze.net header.s=fm1 header.b=0/VsvBn1; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=vfBFGKXY; dmarc=none; spf=pass (mx1.freebsd.org: domain of mail@florian-schulze.net designates 66.111.4.26 as permitted sender) smtp.mailfrom=mail@florian-schulze.net X-Spamd-Result: default: False [-4.53 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[florian-schulze.net:s=fm1,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_MISSING_CHARSET(2.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[florian-schulze.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[florian-schulze.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.98)[-0.979,0]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[26.4.111.66.list.dnswl.org : 127.0.5.1]; RECEIVED_SPAMHAUS_PBL(0.00)[187.58.245.79.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-3.45)[ip: (-9.69), ipnet: 66.111.4.0/24(-4.84), asn: 11403(-2.68), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 10:44:57 -0000 Hi! Since FreeBSD 12 (updated from 10.3, I skipped 11.x completely, the box = started around 9.3) I have the issue that ZFS is not freeing up space = for some deleted files. The filesystems where this happens are mounted = into multiple jails via nullfs. Only one jail has write access, the = others are read only. When files are deleted the space for them is not = freed. I can still see their objects via zdb. When I unmount one of the = read only nullfs mounts the space is freed and the objects released. I already used lsof, procstat and fstat to see if any process still has = a reference to the file, but that is not the case. But it seems to = matter which nullfs mount is unmounted, it is always one of the read = only ones. The processes which access the read only mounts are = completely different, it only seems to matter that the files are opened = at all. Killing the processes doesn't help, only unmounting the nullfs. Today I noticed an odd message when I used zfs diff: "Unable to = determine path or stats for object 6 in = =2E..@zfs-diff-15651-00000001d86eb8cb: Stale NFS file handle". I don't = have NFS enabled anywhere (just checked the properties) and it never was = enabled! The zdb output for object 6: Dataset ... [ZPL], ID 18405, cr_txg 36040566, 10.2G, 43 objects Object lvl iblk dblk dsize dnsize lsize %full type 6 1 16K 16K 16K 512 32K 100.00 SA attr = layouts ZFS_DBGMSG(zdb): spa_open_common: opening ... spa_load(tank2, config trusted): LOADING disk vdev '/dev/diskid/DISK-WD-...': best uberblock found for spa tank2. = txg 40503599 spa_load(tank2, config untrusted): using uberblock with txg=3D40503599 spa_load(tank2, config trusted): spa_load_verify found 0 metadata errors = and 2 data errors spa_load(tank2, config trusted): LOADED In the zfs diff was also a line "- ...(on_delete_queue)". I have one zfs filesystem where this happens quite often, one were it = happens sometimes and a few others which have a similar setup and where = I never noticed it (though the average file size on them is smaller). I asked in #freebsd about this and koobs said I should write to this = list and CC kib@freebsd.org and mgj@freebsd.org He also did a quick look at the nullfs changes between 10.3 and 12.0 and = spotted the following change, which he said I should mention as well: https://github.com/freebsd/freebsd/commit/82f9c275c43da09f404546cceeff187= a90ecc573#diff-81e7d6520611101890dd6425324dd8f8 Is there a known bug there? Could the stale NFS handle cause the leak? = Where is that NFS handle coming from? Regards, Florian Schulze From owner-freebsd-fs@freebsd.org Fri Sep 6 12:43:56 2019 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 8A914F2E9F for ; Fri, 6 Sep 2019 12:43:56 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 46Py0q21khz4KWR for ; Fri, 6 Sep 2019 12:43:54 +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 x86Chaws003006 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 6 Sep 2019 15:43:39 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x86Chaws003006 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x86ChaHX003004; Fri, 6 Sep 2019 15:43:36 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 6 Sep 2019 15:43:36 +0300 From: Konstantin Belousov To: Florian Schulze Cc: freebsd-fs@freebsd.org, mgj@freebsd.org Subject: Re: held file reference issue with ZFS and nullfs Message-ID: <20190906124336.GE2559@kib.kiev.ua> References: <45B080A9-DE0F-4633-91F8-71438408D4B8@florian-schulze.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45B080A9-DE0F-4633-91F8-71438408D4B8@florian-schulze.net> User-Agent: Mutt/1.12.1 (2019-06-15) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-Rspamd-Queue-Id: 46Py0q21khz4KWR X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=gmail.com (policy=none); spf=softfail (mx1.freebsd.org: 2001:470:d5e7:1::1 is neither permitted nor denied by domain of kostikbel@gmail.com) smtp.mailfrom=kostikbel@gmail.com X-Spamd-Result: default: False [-2.98 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all:c]; IP_SCORE_FREEMAIL(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; IP_SCORE(0.00)[ip: (-2.68), ipnet: 2001:470::/32(-4.45), asn: 6939(-3.14), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DMARC_POLICY_SOFTFAIL(0.10)[gmail.com : No valid SPF, No valid DKIM,none] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 12:43:56 -0000 On Fri, Sep 06, 2019 at 12:44:46PM +0200, Florian Schulze wrote: > Hi! > > Since FreeBSD 12 (updated from 10.3, I skipped 11.x completely, the box > started around 9.3) I have the issue that ZFS is not freeing up space > for some deleted files. The filesystems where this happens are mounted > into multiple jails via nullfs. Only one jail has write access, the > others are read only. When files are deleted the space for them is not > freed. I can still see their objects via zdb. When I unmount one of the > read only nullfs mounts the space is freed and the objects released. > > I already used lsof, procstat and fstat to see if any process still has > a reference to the file, but that is not the case. But it seems to > matter which nullfs mount is unmounted, it is always one of the read > only ones. The processes which access the read only mounts are > completely different, it only seems to matter that the files are opened > at all. Killing the processes doesn't help, only unmounting the nullfs. There were some bugs in past where nullfs referenced a lower vnode but did not dereferenced it. > > Today I noticed an odd message when I used zfs diff: "Unable to > determine path or stats for object 6 in > ...@zfs-diff-15651-00000001d86eb8cb: Stale NFS file handle". I don't > have NFS enabled anywhere (just checked the properties) and it never was > enabled! This is probably unrelated. > > The zdb output for object 6: > > Dataset ... [ZPL], ID 18405, cr_txg 36040566, 10.2G, 43 objects > > Object lvl iblk dblk dsize dnsize lsize %full type > 6 1 16K 16K 16K 512 32K 100.00 SA attr > layouts > > > ZFS_DBGMSG(zdb): > spa_open_common: opening ... > spa_load(tank2, config trusted): LOADING > disk vdev '/dev/diskid/DISK-WD-...': best uberblock found for spa tank2. > txg 40503599 > spa_load(tank2, config untrusted): using uberblock with txg=40503599 > spa_load(tank2, config trusted): spa_load_verify found 0 metadata errors > and 2 data errors > spa_load(tank2, config trusted): LOADED > > > In the zfs diff was also a line "- ...(on_delete_queue)". > > I have one zfs filesystem where this happens quite often, one were it > happens sometimes and a few others which have a similar setup and where > I never noticed it (though the average file size on them is smaller). > > I asked in #freebsd about this and koobs said I should write to this > list and CC kib@freebsd.org and mgj@freebsd.org > He also did a quick look at the nullfs changes between 10.3 and 12.0 and > spotted the following change, which he said I should mention as well: > https://github.com/freebsd/freebsd/commit/82f9c275c43da09f404546cceeff187a90ecc573#diff-81e7d6520611101890dd6425324dd8f8 > > Is there a known bug there? Could the stale NFS handle cause the leak? > Where is that NFS handle coming from? So what is the exact version of your system ? If 12.0, upgrade kernel to latest stable/12 and see if it helps with the leak. From owner-freebsd-fs@freebsd.org Fri Sep 6 13:18:31 2019 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 C5F93F3C21 for ; Fri, 6 Sep 2019 13:18:31 +0000 (UTC) (envelope-from mail@florian-schulze.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 46Pymj567Sz4MWX for ; Fri, 6 Sep 2019 13:18:28 +0000 (UTC) (envelope-from mail@florian-schulze.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 461AB21EEB; Fri, 6 Sep 2019 09:18:28 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Fri, 06 Sep 2019 09:18:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= florian-schulze.net; h=from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-type :content-transfer-encoding; s=fm1; bh=We54kscZEd2ao2LVxNpD1mKz1R rs1jFah/dvZH9mnuM=; b=5SBK15+T8tSmhMOLhn2NSL26nGH6D0BNz4OrHXgj3c IuJPhpx3HRzIXw7pEw/42HO2hqZ7bc28M1FTizD1W6WhuwaPMQ1VHgh8dqBv3Sqw bkOLQbn2OuzUUGFkDFv7Bjns2U/eT0DgM7Uas9oes+jfZ97CODCVYQTpv4bnqbQh N+tmsAPXvNeqQtEHL8XZnkBMf5Bm2HYgvJCM/3fPNLN6HlxFzkTrTVEO8sfFI0GR BiOgqX1AbxShDnzj2/mtpHlY6EPPuxC4EvBX/0dOyk9sPy5kpea+xZhpwbHJKBEj kv9CAd5DhaP4wkHlTIJsXkzBeLrXOq6TUgLhlB2ENVVg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=We54kscZEd2ao2LVxNpD1mKz1Rrs1jFah/dvZH9mn uM=; b=FjjZtM64bhqOthIvuiozGqxGXe0xL9c1cdpKejD8mcBRTgTN9MOk/EJoY QXMD9ZS/Yzdm0xhtb/cU36dYJwu11wonW9Fll8tMWK5BIe2RW9sZEvs1Og7OTXVa 6KDSDgDT12GILfGduFf9CYcNdhqlb9Ewbgv3m1SCGhuBbOzJR/BUn9DGgAkXvxXc Bk6QNLv0UMGuhe3Q5BiY94IF4tZlUF0x5eQQYCG9zEotzDVH5D+Bw65lfjIkt3PT otIdn6B0sPDpAgtrpHiCBV1YNsJ34yND5iX2WTl31AUW8s4S8ox1abErQaoEV1Jn 5oOsPnIwna80s+vV/1L3XzLz2tJPQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrudejledghedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffokfgjfhggtgfgsehtqh hmtdertddtnecuhfhrohhmpedfhfhlohhrihgrnhcuufgthhhulhiivgdfuceomhgrihhl sehflhhorhhirghnqdhstghhuhhliigvrdhnvghtqeenucffohhmrghinhepghhithhhuh gsrdgtohhmnecukfhppeejledrvdeghedrheekrddukeejnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmrghilhesfhhlohhrihgrnhdqshgthhhulhiivgdrnhgvthenucevlhhush htvghrufhiiigvpedt X-ME-Proxy: Received: from [192.168.1.182] (p4ff53abb.dip0.t-ipconnect.de [79.245.58.187]) by mail.messagingengine.com (Postfix) with ESMTPA id 539D7D60057; Fri, 6 Sep 2019 09:18:27 -0400 (EDT) From: "Florian Schulze" To: "Konstantin Belousov" Cc: freebsd-fs@freebsd.org Subject: Re: held file reference issue with ZFS and nullfs Date: Fri, 06 Sep 2019 15:18:24 +0200 X-Mailer: MailMate (1.12.5r5635) Message-ID: <5B1BEA13-F8CB-4E3C-9236-629892AF48F5@florian-schulze.net> In-Reply-To: <20190906124336.GE2559@kib.kiev.ua> References: <45B080A9-DE0F-4633-91F8-71438408D4B8@florian-schulze.net> <20190906124336.GE2559@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable Autocrypt: addr=mail@florian-schulze.net; keydata=mQENBFliSUoBCADLKPuy1qhTI+A3XRleyZ7WlXhRfYiXBCSMiIqUb+nx88xKLVAclRJqMnqlJHzAJcb4JW9i3riRU+V1rVG9BDaBCCih5Si0BQO5W84SpaadTdcE3rUO8Ihdxc6dJN9DiAtp26WyO1fXSA2NkwpakIerxlF91knkrnSa/VgLrlB+Ahtcisbsn9XYSnv0wr/njQJOfJMsmJfWAKXWWaWDWb0Z4/UITsBe259Ppkf6bTYS3j7oCPqygPzdyc14ILINb0N3ksT3tKLiS4b2gh7RAO4uf/C8TvlZSYvoX/sel5xFFxcgmqG+V0d4jjhdvY5zFHU+/Egr5y3HPgSQjevEHsNxABEBAAG0KkZsb3JpYW4gU2NodWx6ZSA8bWFpbEBmbG9yaWFuLXNjaHVsemUubmV0PokBOQQTAQgAIwUCWWJJSgIbAwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEC0N2jSLcB7qWo4H/jEgS6Id1TkRtlh+vZanpswS83sH8pOfc20qHbPEM2a1pk9aEgvvnckaeLiGVYaHKZccxRaE2E6zGKW26sI5WPcMehCZkiYf4zxfoppWsWDIGAsuptByHT+etkQVEANwNdDM5hIn4Hq0e6gsH1zu68SBhH4FtW4+ukCK3WrHZ0QJBoECU1otWxhP5BqOO8h9OCY2vESxHC2nH+y3vsqVL43JQWmBUv7uaaX4OusdWUZCW8jlYnWd//cmt3RKHh4PCKY7JK0itzoUi+DnnHBN7jxz2FFjX3+BinUeZX3bpXQhw3Xsv1ZXW9aeyGLgzYOuLdBSXmXJcetyJ0heCrOwZUS5AQ0EWWJJSgEIANlJdoChOEMMB7vh3YB0HjrBpK2+iyWC1Y1VCWOpKg/PiYq5GmZDMh1SGq+s/3ZVG5kAYcSKqdHSBqC8sRjY/gU/hysR3w9IU0J5/j1jTFZsw09vTfloEVRAJaAEyOAKvgUw+ fwiGhJsJPS9W8dqieVovqft5DpzNIBztPJxfiDrlHvKbxrwyCEW9+EAHMVJf7F6wqp0rAnlxZQujasL7Urx1Kl0RKT9HT8QHyzTJFpbpuO0hApiWCWD5GCy3AIc0KK3jJIz3ODCVFSGhbLiV0j9FB4j3wmM5JSvsyMhLZAkaFy/kqmlaVeroLWMBbmKUfEA968b37O+kILc3iXYQmMAEQEAAYkBHwQYAQgACQUCWWJJSgIbDAAKCRAtDdo0i3Ae6oyuB/4rh42bgTYncPkMv0l9jsKTB61wwe2Imxfxd52Gk3Ev5slaSFYl2r2FwhTFCX5Ay5XXqoueIG2AlZY2do7jnuLW66dye4GAI67PgKkZfzWJqD+q3bOimnmdlyKM1x2AxGnwPBEdjc4sShFm/uPOPPGJu4f8I9PKjGI62RJUCGHN9KxYJclomhNYe6n1xDsF0e3lDEtWn+KL1WesHO/NY2Mv//qGs9dqIu7rdAXrXiBQaSUz8ol0o4Z924qEWX+23tlWn3XLZPbFPJAB8sPHKWapt3nR/zaPJqfqkqwKWnWFdiKaKIB9GhlXmBlq+0alpjNjbicGlOF1YGF4agbFyoCb X-Rspamd-Queue-Id: 46Pymj567Sz4MWX X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=florian-schulze.net header.s=fm1 header.b=5SBK15+T; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=FjjZtM64; dmarc=none; spf=pass (mx1.freebsd.org: domain of mail@florian-schulze.net designates 66.111.4.27 as permitted sender) smtp.mailfrom=mail@florian-schulze.net X-Spamd-Result: default: False [-4.57 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[florian-schulze.net:s=fm1,messagingengine.com:s=fm3]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_MISSING_CHARSET(2.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[florian-schulze.net]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[florian-schulze.net:+,messagingengine.com:+]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.99)[-0.990,0]; IP_SCORE(-3.48)[ip: (-9.81), ipnet: 66.111.4.0/24(-4.84), asn: 11403(-2.68), country: US(-0.05)]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_IN_DNSWL_LOW(-0.10)[27.4.111.66.list.dnswl.org : 127.0.5.1]; RECEIVED_SPAMHAUS_PBL(0.00)[187.58.245.79.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11403, ipnet:66.111.4.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 13:18:31 -0000 Hi! On 6 Sep 2019, at 14:43, Konstantin Belousov wrote: Thanks for the reply ... > On Fri, Sep 06, 2019 at 12:44:46PM +0200, Florian Schulze wrote: >> Hi! >> >> Since FreeBSD 12 (updated from 10.3, I skipped 11.x completely, the = >> box >> started around 9.3) I have the issue that ZFS is not freeing up space >> for some deleted files. The filesystems where this happens are = >> mounted >> into multiple jails via nullfs. Only one jail has write access, the >> others are read only. When files are deleted the space for them is = >> not >> freed. I can still see their objects via zdb. When I unmount one of = >> the >> read only nullfs mounts the space is freed and the objects released. >> >> I already used lsof, procstat and fstat to see if any process still = >> has >> a reference to the file, but that is not the case. But it seems to >> matter which nullfs mount is unmounted, it is always one of the read >> only ones. The processes which access the read only mounts are >> completely different, it only seems to matter that the files are = >> opened >> at all. Killing the processes doesn't help, only unmounting the = >> nullfs. > There were some bugs in past where nullfs referenced a lower vnode but > did not dereferenced it. Could you be more concrete about "past"? In the past of the 12.0 = version, or during 11.x? >> I have one zfs filesystem where this happens quite often, one were it >> happens sometimes and a few others which have a similar setup and = >> where >> I never noticed it (though the average file size on them is smaller). >> >> I asked in #freebsd about this and koobs said I should write to this >> list and CC kib@freebsd.org and mgj@freebsd.org >> He also did a quick look at the nullfs changes between 10.3 and 12.0 = >> and >> spotted the following change, which he said I should mention as well: >> https://github.com/freebsd/freebsd/commit/82f9c275c43da09f404546cceeff= 187a90ecc573#diff-81e7d6520611101890dd6425324dd8f8 >> >> Is there a known bug there? Could the stale NFS handle cause the = >> leak? >> Where is that NFS handle coming from? > > So what is the exact version of your system ? If 12.0, upgrade kernel > to latest stable/12 and see if it helps with the leak. I'm on 12.0-RELEASE-p3. I will probably be able to try 12.0-RELEASE-p10 = during the weekend. Not sure I will find the time to try and compile my = own kernel, or is there a way to do it using freebsd-update by using a = snapshot? If not, I'd probably rather wait for 12.1. Regards, Florian Schulze From owner-freebsd-fs@freebsd.org Fri Sep 6 17:33:14 2019 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 04286D122F for ; Fri, 6 Sep 2019 17:33:14 +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 46Q4Qd6Ln2z4c3q for ; Fri, 6 Sep 2019 17:33:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id D9EB6D122D; Fri, 6 Sep 2019 17:33:13 +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 D9B0AD122C for ; Fri, 6 Sep 2019 17:33:13 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Q4Qd5T1rz4c3p for ; Fri, 6 Sep 2019 17:33:13 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A030E204F2 for ; Fri, 6 Sep 2019 17:33:13 +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 x86HXDcT066393 for ; Fri, 6 Sep 2019 17:33:13 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x86HXDWO066392 for fs@FreeBSD.org; Fri, 6 Sep 2019 17:33:13 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 221077] Boot from ZFS fails following freebsd-update Date: Fri, 06 Sep 2019 17:33:13 +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: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwb@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 17:33:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 --- Comment #29 from Jason W. Bacon --- Only boot records. You don't really need JBOD support. Creating separate 1-disk volumes for e= ach drive has worked for me. It's not ideal, but it seems to be reliable. Thi= s is what I had to do for the Proliant server and I've had no problems with it. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Sep 6 17:56:48 2019 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 209B9D2019 for ; Fri, 6 Sep 2019 17:56: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 46Q4xq64vqz4fm5 for ; Fri, 6 Sep 2019 17:56:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CEA6BD2018; Fri, 6 Sep 2019 17:56:47 +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 CE476D2017 for ; Fri, 6 Sep 2019 17:56:47 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Q4xq4t7pz4fm1 for ; Fri, 6 Sep 2019 17:56:47 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8C3F2208E6 for ; Fri, 6 Sep 2019 17:56:47 +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 x86HulLv019378 for ; Fri, 6 Sep 2019 17:56:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x86Huluq019377 for fs@FreeBSD.org; Fri, 6 Sep 2019 17:56:47 GMT (envelope-from bugzilla-noreply@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: [Bug 230260] [FUSEFS] [PERFORMANCE]: Performance issue (I/O block size) Date: Fri, 06 Sep 2019 17:56:47 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 17:56:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230260 --- Comment #17 from commit-hook@freebsd.org --- A commit references this bug: Author: asomers Date: Fri Sep 6 17:56:27 UTC 2019 New revision: 351943 URL: https://svnweb.freebsd.org/changeset/base/351943 Log: MFC r344183-r344187, r344333-r344334, r344407, r344857, r344865 (by cem) r344183: FUSE: Respect userspace FS "do-not-cache" of file attributes The FUSE protocol demands that kernel implementations cache user filesyst= em file attributes (vattr data) for a maximum period of time in the range of [0, ULONG_MAX] seconds. In practice, typical requests are for 0, 1, or 10 seconds; or "a long time" to represent indefinite caching. Historically, FreeBSD FUSE has ignored this client directive entirely. T= his works fine for local-only filesystems, but causes consistency issues with multi-writer network filesystems. For now, respect 0 second cache TTLs and do not cache such metadata. Non-zero metadata caching TTLs in the range [0.000000001, ULONG_MAX] seco= nds are still cached indefinitely, because it is unclear how a userspace filesystem could do anything sensible with those semantics even if implemented. In the future, as an optimization, we should implement notify_inval_entry, etc, which provide userspace filesystems a way of evicting the kernel cac= he. One potentially bogus access to invalid cached attribute data was left in fuse_io_strategy. It is restricted behind the undocumented and non-defau= lt "vfs.fuse.fix_broken_io" sysctl or "brokenio" mount option; maybe these a= re deadcode and can be eliminated? Some minor APIs changed to facilitate this: 1. Attribute cache validity is tracked in FUSE inodes ("fuse_vnode_data"). 2. cache_attrs() respects the provided TTL and only caches in the FUSE inode if TTL > 0. It also grows an "out" argument, which, if non-NULL, stores the translated fuse_attr (even if not suitable for caching). 3. FUSE VTOVA(vp) returns NULL if the vnode's cache is invalid, to help avoid programming mistakes. 4. A VOP_LINK check for potential nlink overflow prior to invoking the FU= SE link op was weakened (only performed when we have a valid attr cache). T= he check is racy in a multi-writer network filesystem anyway -- classic TOCT= OU. We have to trust any userspace filesystem that rejects local caching to account for it correctly. PR: 230258 (inspired by; does not fix) r344184: FUSE: Respect userspace FS "do-not-cache" of path components The FUSE protocol demands that kernel implementations cache user filesyst= em path components (lookup/cnp data) for a maximum period of time in the ran= ge of [0, ULONG_MAX] seconds. In practice, typical requests are for 0, 1, or 10 seconds; or "a long time" to represent indefinite caching. Historically, FreeBSD FUSE has ignored this client directive entirely. T= his works fine for local-only filesystems, but causes consistency issues with multi-writer network filesystems. For now, respect 0 second cache TTLs and do not cache such metadata. Non-zero metadata caching TTLs in the range [0.000000001, ULONG_MAX] seco= nds are still cached indefinitely, because it is unclear how a userspace filesystem could do anything sensible with those semantics even if implemented. Pass fuse_entry_out to fuse_vnode_get when available and only cache lookup if the user filesystem did not set a zero second TTL. PR: 230258 (inspired by; does not fix) r344185: FUSE: Only "dirty" cached file size when data is dirty Most users of fuse_vnode_setsize() set the cached fvdat->filesize and upd= ate the buf cache bounds as a result of either a read from the underlying FUSE filesystem, or as part of a write-through type operation (like truncate = =3D> VOP_SETATTR). In these cases, do not set the FN_SIZECHANGE flag, which indicates that an inode's data is dirty (in particular, that the local buf cache and fvdat->filesize have dirty extended data). PR: 230258 (related) r344186: FUSE: The FUSE design expects writethrough caching At least prior to 7.23 (which adds FUSE_WRITEBACK_CACHE), the FUSE protoc= ol specifies only clean data to be cached. Prior to this change, we implement and default to writeback caching. This is ok enough for local only filesystems without hardlinks, but violates t= he general design contract with FUSE and breaks distributed filesystems or concurrent access to hardlinks of the same inode. In this change, add cache mode as an extension of cache enable/disable. = The new modes are UC (was: cache disabled), WT (default), and WB (was: cache enabled). For now, WT caching is implemented as write-around, which meets the goal = of only caching clean data. WT can be better than WA for workloads that frequently read data that was recently written, but WA is trivial to implement. Note that this has no effect on O_WRONLY-opened files, which were already coerced to write-around. Refs: * https://sourceforge.net/p/fuse/mailman/message/8902254/ * https://github.com/vgough/encfs/issues/315 PR: 230258 (inspired by) r344187: FUSE: Refresh cached file size when it changes (lookup) The cached fvdat->filesize is indepedent of the (mostly unused) cached_attrs, and we failed to update it when a cached (but perhaps inactive) vnode was found during VOP_LOOKUP to have a different size than cached. As noted in the code comment, this can occur in distributed filesystems or with other kinds of irregular file behavior (anything is possible in FUSE= ). We do something similar in fuse_vnop_getattr already. PR: 230258 (as reported in description; other issues explored in comments are not all resolved) Reported by: MooseFS FreeBSD Team Submitted by: Jakub Kruszona-Zawadzki (earlier vers= ion) r344333: fuse: add descriptions for remaining sysctls (Except reclaim revoked; I don't know what that goal of that one is.) r344334: Fuse: whitespace and style(9) cleanup Take a pass through fixing some of the most egregious whitespace issues in fs/fuse. Also fix some style(9) warts while here. Not 100% cleaned up, = but somewhat less painful to look at and edit. No functional change. r344407: fuse: Fix a regression introduced in r337165 On systems with non-default DFLTPHYS and/or MAXBSIZE, FUSE would attempt = to use a buf cache block size in excess of permitted size. This did not aff= ect most configurations, since DFLTPHYS and MAXBSIZE both default to 64kB. The issue was discovered and reported using a custom kernel with a DFLTPH= YS of 512kB. PR: 230260 (comment #9) Reported by: ken@ r344857: FUSE: Prevent trivial panic When open(2) was invoked against a FUSE filesystem with an unexpected fla= gs value (no O_RDONLY / O_RDWR / O_WRONLY), an assertion fired, causing pani= c. For now, prevent the panic by rejecting such VOP_OPENs with EINVAL. This is not considered the correct long term fix, but does prevent an unprivileged denial-of-service. PR: 236329 Reported by: asomers Reviewed by: asomers Sponsored by: Dell EMC Isilon r344865: fuse: switch from DFLTPHYS/MAXBSIZE to maxcachebuf On GENERIC kernels with empty loader.conf, there is no functional change. DFLTPHYS and MAXBSIZE are both 64kB at the moment. This change allows larger bufcache block sizes to be used when either MAXBSIZE (custom kerne= l) or the loader.conf tunable vfs.maxbcachebuf (GENERIC) is adjusted higher than the default. Suggested by: ken@ Changes: _U stable/12/ stable/12/sys/fs/fuse/fuse.h stable/12/sys/fs/fuse/fuse_device.c stable/12/sys/fs/fuse/fuse_file.c stable/12/sys/fs/fuse/fuse_file.h stable/12/sys/fs/fuse/fuse_internal.c stable/12/sys/fs/fuse/fuse_internal.h stable/12/sys/fs/fuse/fuse_io.c stable/12/sys/fs/fuse/fuse_ipc.c stable/12/sys/fs/fuse/fuse_ipc.h stable/12/sys/fs/fuse/fuse_node.c stable/12/sys/fs/fuse/fuse_node.h stable/12/sys/fs/fuse/fuse_vfsops.c stable/12/sys/fs/fuse/fuse_vnops.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Sep 6 17:59:12 2019 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 E8A9ED214D for ; Fri, 6 Sep 2019 17:59:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 46Q50c5xwzz4fwS for ; Fri, 6 Sep 2019 17:59:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id CA672D214C; Fri, 6 Sep 2019 17:59:12 +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 CA2A9D214A for ; Fri, 6 Sep 2019 17:59:12 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Q50c52lgz4fwR for ; Fri, 6 Sep 2019 17:59:12 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 913F5208FC for ; Fri, 6 Sep 2019 17:59:12 +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 x86HxCm9023017 for ; Fri, 6 Sep 2019 17:59:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x86HxCOi023016 for fs@FreeBSD.org; Fri, 6 Sep 2019 17:59:12 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 230260] [FUSEFS] [PERFORMANCE]: Performance issue (I/O block size) Date: Fri, 06 Sep 2019 17:59:12 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable11- mfc-stable12+ X-Bugzilla-Changed-Fields: flagtypes.name bug_status resolution 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.29 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Sep 2019 17:59:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230260 Alan Somers changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |mfc-stable11-, | |mfc-stable12+ Status|In Progress |Closed Resolution|--- |FIXED --=20 You are receiving this mail because: You are the assignee for the bug.=