From owner-freebsd-fs@freebsd.org Sun Nov 20 14:52:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 054BFC4BF80 for ; Sun, 20 Nov 2016 14:52:24 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 C2D4DFD3 for ; Sun, 20 Nov 2016 14:52:23 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c8TTg-0001Bv-HK; Sun, 20 Nov 2016 14:52:20 +0000 Date: Sun, 20 Nov 2016 14:52:20 +0000 From: Gary Palmer To: Kent Kuriyama Cc: freebsd-fs@freebsd.org Subject: Re: ZFS question: "L2ARC is disabled" Message-ID: <20161120145220.GA99344@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 14:52:24 -0000 On Fri, Nov 18, 2016 at 04:31:49AM -1000, Kent Kuriyama wrote: > I have set up a ZFS pool (zpool0) with both zil and L2ARC. The output of > zpool status is: > > ------------------------------------ > zpool status > pool: zpool0 > state: ONLINE > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > zpool0 ONLINE 0 0 0 > da0p2 ONLINE 0 0 0 > logs > ada0p8 ONLINE 0 0 0 > cache > ada0p9 ONLINE 0 0 0 > > errors: No known data errors > ---------------------------------- > > When I run "zfs-stats -v" I get the message "L2ARC is disabled". ARC is > healthy. Can someone please tell me what I am doing wrong to prevent L2ARC > from being enabled? I am running a qbittorrent on a FreeBSD 11.0p3 system > and expected to benefit from L2ARC because of the intense read activity. > Both the ZIL and L2ARC are on an SSD partition. What is the output from zfs get secondarycache zpool0 Gary From owner-freebsd-fs@freebsd.org Sun Nov 20 15:02:37 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F383C4B23C for ; Sun, 20 Nov 2016 15:02:37 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 4E06C1628 for ; Sun, 20 Nov 2016 15:02:37 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.87 (FreeBSD)) (envelope-from ) id 1c8Tdb-0001nD-NY; Sun, 20 Nov 2016 15:02:35 +0000 Date: Sun, 20 Nov 2016 15:02:35 +0000 From: Gary Palmer To: Marek Salwerowicz Cc: "freebsd-fs@freebsd.org" Subject: Re: zpool raidz2 stopped working after failure of one drive Message-ID: <20161120150235.GB99344@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 15:02:37 -0000 On Sat, Nov 19, 2016 at 09:15:54PM +0100, Marek Salwerowicz wrote: > Hi all, > > I run a following server: > > - Supermicro 6047R-E1R36L > - 96 GB RAM > - 1x INTEL CPU E5-2640 v2 @ 2.00GHz > - FreeBSD 10.3-RELEASE-p11 > > Drive for OS: > - HW RAID1: 2x KINGSTON SV300S37A120G > > zpool: > - 18x WD RED 4TB @ raidz2 > - log: mirrored Intel 730 SSD > - cache: single Intel 730 SSD > > > Today after one drive's failure, the whole vdev was removed from the > zpool (basically the zpool was down, zpool / zfs commands were not > responding): > [snip] > There was no other option than hard-rebooting server. > SMART value "Raw_Read_Error_Rate " for the failed drive has increased 0 > -> 1. I am about to replace it - it still has warranty. > > I have now disabled the failing drive in zpool and it works fine (of > course, in DEGRADED state until I replace the drive) > > However, I am concerned by the fact that one drive's failure has blocked > completely zpool. > Is it normal normal behaviour for zpools ? What is the setting in zpool get failmode By default it is "wait", which I suspect is what caused your issues. See the man page for zpool for more. > Also, is there already auto hot-spare in ZFS? If I had a hot spare drive > in my zpool, would it be automatically replaced? zfsd in 11.0 and later is the current path to hot spare management in FreeBSD. FreeBSD 10.x does not have the ability to automatically use hot spares to replace failing drives. Regards Gary From owner-freebsd-fs@freebsd.org Sun Nov 20 20:03:37 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F006FC4C9B0 for ; Sun, 20 Nov 2016 20:03:37 +0000 (UTC) (envelope-from marek.salwerowicz@misal.pl) Received: from mail3.misal.pl (mail3.misal.pl [83.19.131.174]) (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 A2DF21A9E; Sun, 20 Nov 2016 20:03:37 +0000 (UTC) (envelope-from marek.salwerowicz@misal.pl) Received: from localhost (mail3.misal.pl [127.0.0.1]) by mail3.misal.pl (Postfix) with ESMTP id 12597317C; Sun, 20 Nov 2016 21:03:33 +0100 (CET) X-Virus-Scanned: amavisd X-Spam-Flag: NO X-Spam-Score: -3 X-Spam-Level: X-Spam-Status: No, score=-3 tagged_above=-9999 required=9 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: mail3.misal.pl (amavisd-new); dkim=pass (1024-bit key) header.d=misal.pl Received: from mail3.misal.pl ([127.0.0.1]) by localhost (mail3.misal.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UxXLae3va_XE; Sun, 20 Nov 2016 21:03:32 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.10.3 mail3.misal.pl B42803175 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=misal.pl; s=misal.pl; t=1479672211; bh=qgIPbrsVpIi77bSlgOjKARj8eaZFyyNsfh+h5sZXW1w=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=spFhw2wdPMtz7RcLVCUS3iQKhFNbpYnZlrKojCTeKXrxIjmaljc1q66RyhGLQ4d2N lsA3eqGaD3OWV8zUdGNs4YcZXK9g/+i9FzZ/SDztNOsBz7kN2STAIn8JtvITNSFT2E wx4FcSfDBsQ+9BbdG8YF5+s0UuZ+9ophG80JdftA= Subject: Re: zpool raidz2 stopped working after failure of one drive To: Gary Palmer References: <20161120150235.GB99344@in-addr.com> Cc: "freebsd-fs@freebsd.org" From: Marek Salwerowicz Message-ID: Date: Sun, 20 Nov 2016 21:03:30 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161120150235.GB99344@in-addr.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 20:03:38 -0000 W dniu 2016-11-20 o 16:02, Gary Palmer pisze: > >> However, I am concerned by the fact that one drive's failure has blocked >> completely zpool. >> Is it normal normal behaviour for zpools ? > > What is the setting in > > zpool get failmode > > By default it is "wait", which I suspect is what caused your issues. > See the man page for zpool for more. Indeed, it's wait. However, I was trying to reproduce the problem in a VM by removing SATA disk on the fly from raidz2 (while pool was under I/O by bonnie++ ), and it worked correctly - drive state is "REMOVED" in "zpool status" command. But the pool works correctly. Taking into account this PR, I am wondering if it might be a hardware issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348 > zfsd in 11.0 and later is the current path to hot spare management > in FreeBSD. FreeBSD 10.x does not have the ability to automatically use > hot spares to replace failing drives. Thanks - I will try it out. Cheers Marek -- Marek Salwerowicz MISAL-SYSTEM tel. + 48 222 198891 From owner-freebsd-fs@freebsd.org Sun Nov 20 21:00:30 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00195C4C99E for ; Sun, 20 Nov 2016 21:00:29 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EB2861F42 for ; Sun, 20 Nov 2016 21:00:29 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAKL01og016611 for ; Sun, 20 Nov 2016 21:00:29 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201611202100.uAKL01og016611@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 20 Nov 2016 21:00:29 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2016 21:00:30 -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 | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 203419 | solaris assert: (dn->dn_phys->dn_nlevels == 0 && Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Tue Nov 22 00:27:35 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19B07C4CEAE for ; Tue, 22 Nov 2016 00:27:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0954787A for ; Tue, 22 Nov 2016 00:27:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAM0RYgB020044 for ; Tue, 22 Nov 2016 00:27:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 180894] [panic] rm -rf causes kernel panic Date: Tue, 22 Nov 2016 00:27:35 +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: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: mckusick@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 00:27:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D180894 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: mckusick Date: Tue Nov 22 00:27:19 UTC 2016 New revision: 308946 URL: https://svnweb.freebsd.org/changeset/base/308946 Log: MFC r307978: Bug 180894 reports that rm -rf on a directory causes kernel panic and reb= oot. Return EINVAL rather than panic for low directory link count. PR: 180894 Changes: _U stable/10/ stable/10/sys/ufs/ufs/ufs_vnops.c --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Nov 22 00:36:49 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FA84C4D0D1 for ; Tue, 22 Nov 2016 00:36:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6F22DC23 for ; Tue, 22 Nov 2016 00:36:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAM0aneZ042999 for ; Tue, 22 Nov 2016 00:36:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 180894] [panic] rm -rf causes kernel panic Date: Tue, 22 Nov 2016 00:36:49 +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: CURRENT X-Bugzilla-Keywords: crash X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: mckusick@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 00:36:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D180894 Kirk McKusick changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Closed Resolution|--- |FIXED --- Comment #10 from Kirk McKusick --- The bugfix has been MFC'ed to 10-stable and 11-stable, so I am now closing = it. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Tue Nov 22 07:09:31 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E966C4E83C for ; Tue, 22 Nov 2016 07:09:31 +0000 (UTC) (envelope-from jamesmorris8@outlook.com) Received: from BLU004-OMC4S20.hotmail.com (blu004-omc4s20.hotmail.com [65.55.111.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3370A1B9F for ; Tue, 22 Nov 2016 07:09:30 +0000 (UTC) (envelope-from jamesmorris8@outlook.com) Received: from IND01-MA1-obe.outbound.protection.outlook.com ([65.55.111.137]) by BLU004-OMC4S20.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 21 Nov 2016 23:08:24 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=JiCP0Zn9cQPUMLpTI2CV7DgEFKbGI0H/vIU+arehFhM=; b=uwz+XKwA+7o6z2/zBdUMOrDfzPFJJnry86dvbZYoK7EuwyLE/RRUqtfmn6QcbeqYHJJAQdOvB/VRBYeSgNatfPKjMEXJEXodGkuAKmogxKAcSOnMrXWP8OoZQ+yoms6cvsp7+bgMRAWoD/3trJabqvCau/e9FrdLKBfkbMpO1gjFi74e3UnReKD7rqYg2FXCgFHeyoGwSgp/t2rG9Aniw+ZDUWmv8Da+J8HP6XV0etOCx2QIxyZyjxaJ8oYWzrqrSYmG09yGrByFaSpV+K3nJ60vPDpqM7ndtGBS//0fb481e5cqMgaX7B8E6xV3DPAPUGB8+Q77DK/fHmqlY0XR+g== Received: from MA1IND01FT003.eop-IND01.prod.protection.outlook.com (10.152.200.58) by MA1IND01HT003.eop-IND01.prod.protection.outlook.com (10.152.200.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5; Tue, 22 Nov 2016 07:08:13 +0000 Received: from BM1PR01MB0209.INDPRD01.PROD.OUTLOOK.COM (10.152.200.51) by MA1IND01FT003.mail.protection.outlook.com (10.152.200.70) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.5 via Frontend Transport; Tue, 22 Nov 2016 07:08:13 +0000 Received: from BM1PR01MB0209.INDPRD01.PROD.OUTLOOK.COM ([10.164.129.147]) by BM1PR01MB0209.INDPRD01.PROD.OUTLOOK.COM ([10.164.129.147]) with mapi id 15.01.0734.007; Tue, 22 Nov 2016 07:08:12 +0000 From: James Morris To: freebsd-fs Subject: Unresponsive system, ZFS ARK forcing proceses into swap Thread-Topic: Unresponsive system, ZFS ARK forcing proceses into swap Thread-Index: AQHSRIxYt2P25AuZpEeTIliP4ppnMg== Date: Tue, 22 Nov 2016 07:08:11 +0000 Message-ID: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: FreeBSD.org; dkim=none (message not signed) header.d=none;FreeBSD.org; dmarc=none action=none header.from=outlook.com; x-incomingtopheadermarker: OriginalChecksum:; UpperCasedChecksum:; SizeAsReceived:7243; Count:36 x-tmn: [6cGT0ue668HrrHxN20sAyrrkOJxLMd5G] x-incomingheadercount: 36 x-eopattributedmessage: 0 x-microsoft-exchange-diagnostics: 1; MA1IND01HT003; 5:JfJtlzaGPPh5ZOd4ddJ6D5gxKW7JF/01HnVh++P7YPF6U/v4iPLuhPBYlkyI8hEdmz46Zdqabgi+XnteA51mTk+IDdeDSPNdsZZJ7urZN0K5LXXZ58WvZ4/xez7evj5AYoBp5LNvwg7TJWDevuvOig==; 24:NQ9AOtQjjkWLxMY5MIZD31+05sVUsF3RRXJuAvrIIzMPZT6HT7/bV4khxDbQ+JCebJmdyNwzz5FYgvkP3kvEZhbXUYPlfThNUKnBHI+q4M0=; 7:bO7yg4fcq2ERlEE+fnQQpkgSnEBK/h16VsswQ86fd8dOxS1HrHvcXfHz63ZRUocHANqGoVpefImiUqjwZueqfvJwh2tyWnb9Y0l67xPTcz4/lqv0YeUJDKf8665ZeIKn5UlL1IA+eRABxaEXSIhUEGMvuzUIedTDG0gHytVq6qO6UDqmap7OXg/DaW/C9rMjjHPzoC291uVmZlXhwpMB/Bv5D6eJr+3RiK+U3ZVhPB8WB7kzinggH0gFZ1IuBM8AGGSNKEdOqq+hSNi54NZbhOJZ9mXuru7faAsO6CB3oeNNw1aihCl4XVmAQrE8iV/GEfhx0rlwnHrtUdqIpmodgfZBNYVkQV0IG/YSpH4cncU= x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:MA1IND01HT003; H:BM1PR01MB0209.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; x-ms-office365-filtering-correlation-id: e22895eb-573d-4f45-5ad3-08d412a652c1 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(1601124038)(1603103113)(1603101340)(1601125047); SRVR:MA1IND01HT003; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:MA1IND01HT003; BCL:0; PCL:0; RULEID:; SRVR:MA1IND01HT003; x-forefront-prvs: 0134AD334F spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Nov 2016 07:08:11.8829 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: MA1IND01HT003 X-OriginalArrivalTime: 22 Nov 2016 07:08:24.0969 (UTC) FILETIME=[3785BF90:01D2448F] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 07:09:31 -0000 Hi, I have a freebsd 10.3 zfs server running with multiple zfs jails. I run samba, syslog-ng, a web server and a few assorted other services in e= ach jail. The machine is not used much, but I have noticed that I can not ssh into th= e base system or reach a web server that I run on the base system after a f= ew days of running. On connecting via the console I notice that arc is taking up a bulk of the = ram and it seems processes like sshd and nginx are frozen. Also the swap space is utilised and the ARC is taking up the majority of my= RAM. When I try and run an interactive command like top, less, ... It loads, but= the system takes exceedingly long 10min+ to close these. The same symptoms are true when I try to use ^c to quit a running process l= ike ping. Any help triaging this issue will be much appreciated. I believe that the ZFS ARC has something to do with it, but I do not want t= o turn it off altogether. Is there a way to make sure ZFS does not push my other processes (sshd, ngi= nx, ...) into swap where they are unresponsive. Output of top while in this state is below last pid: 31465; load averages: 0.43, 0.56, 0.54 up 1+08:18:48 13:5= 9:44 319 processes: 1 running, 308 sleeping, 1 stopped, 3 zombie, 6 waiting Mem: 82M Active, 336K Inact, 15G Wired, 76M Cache, 12M Free ARC: 12G Total, 3503M MFU, 26M MRU, 13M Anon, 22M Header, 8572M Other Swap: 2048M Total, 1064M Used, 984M Free, 51% Inuse Thanks in advance, James= From owner-freebsd-fs@freebsd.org Tue Nov 22 13:34:03 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1250EC4DFC0 for ; Tue, 22 Nov 2016 13:34:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 01ED9177F for ; Tue, 22 Nov 2016 13:34:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uAMDY1rq011900 for ; Tue, 22 Nov 2016 13:34:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 209158] node / npm triggering zfs rename deadlock Date: Tue, 22 Nov 2016 13:34:02 +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: CURRENT X-Bugzilla-Keywords: needs-qa, patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2016 13:34:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209158 Julien Cigar changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |julien@perdition.city --- Comment #47 from Julien Cigar --- any idea if an EN is planned for this bug? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Thu Nov 24 10:54:14 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0044CC52B33 for ; Thu, 24 Nov 2016 10:54:14 +0000 (UTC) (envelope-from julien@perdition.city) Received: from relay-b03.edpnet.be (relay-b03.edpnet.be [212.71.1.220]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "edpnet.email", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B50FF1DD0 for ; Thu, 24 Nov 2016 10:54:12 +0000 (UTC) (envelope-from julien@perdition.city) X-ASG-Debug-ID: 1479984164-0a88184195bdc6f0001-3nHGF7 Received: from mordor.lan (77.109.124.121.adsl.dyn.edpnet.net [77.109.124.121]) by relay-b03.edpnet.be with ESMTP id IovYxf9HapLu0iRm (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 24 Nov 2016 11:42:45 +0100 (CET) X-Barracuda-Envelope-From: julien@perdition.city X-Barracuda-Effective-Source-IP: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Apparent-Source-IP: 77.109.124.121 Date: Thu, 24 Nov 2016 11:42:44 +0100 From: Julien Cigar To: freebsd-fs@freebsd.org Subject: PR 209158 Message-ID: <20161124104244.GO56668@mordor.lan> X-ASG-Orig-Subj: PR 209158 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="DBUa/BSa4z6QPQv1" Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) X-Barracuda-Connect: 77.109.124.121.adsl.dyn.edpnet.net[77.109.124.121] X-Barracuda-Start-Time: 1479984164 X-Barracuda-Encrypted: ECDHE-RSA-AES256-GCM-SHA384 X-Barracuda-URL: https://212.71.1.220:443/cgi-mod/mark.cgi X-Barracuda-Scan-Msg-Size: 845 X-Virus-Scanned: by bsmtpd at edpnet.be X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.4942 1.0000 0.0000 X-Barracuda-Spam-Score: 1.50 X-Barracuda-Spam-Status: No, SCORE=1.50 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=6.0 tests=BSF_SC0_MV0713, BSF_SC0_MV0713_2 X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.34706 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 1.00 BSF_SC0_MV0713_2 BSF_SC0_MV0713_2 0.50 BSF_SC0_MV0713 Custom rule MV0713 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 10:54:14 -0000 --DBUa/BSa4z6QPQv1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, We have a bunch of machines which use the node package manager (NPM) quite heavily and so PR 209158 is very problematic to us as this deadlock occur almost every time npm is triggered.. and only option is=20 to reboot the machine. It has another annoying side effect: backups are stalled because our backup software (Bacula) try to backup a directory which is involved in the deadlock ... Now that the fix has been MFC'ed to 10-STABLE I would like to know if an EN is planned (we're running 10.3-RELEASE), or if I have to upgrade to -STABLE ..? Thanks! Julien --=20 Julien Cigar Belgian Biodiversity Platform (http://www.biodiversity.be) PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0 No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced. --DBUa/BSa4z6QPQv1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAABCgAGBQJYNsQhAAoJELK7NxCiBCPADkkQAMy55YoG+sEGex+56Xsm0SIu FVe1ohNd10lfJddHiGUafvkAsdbo+DgR/Khw5gIq/7o4ZRxjeeDuW6hqCW94Ikfi IM7bexxa0rWh9yNxLFVPuamapA7J/W99o/tiotijjIcnTHecT9dhHJVINsKVG+oB 1scIKdk6R0gAlJwjXnfZ05QObTWsncjS7YAiqWs8aVS8m6OqbkgDLGtoPi2c/3FF NPZTbprXXBgZ5ixj8ZaKZQXWNtSm42ie50zSQvB3Uah+TeV823DeQ8Ag4rSQn/Hk 9/pUvBTKscF+JIwskzhgdJ0gJc+zUYEnIrjnmdoW5DkbF8EkzF5t03vJVJdFf8M6 kpSTl2tw9EwHaLq9A5fdeFnsrACQ17MLB1Gfu+lu8CDOKTIRFfhhJIc2TLF0CFhd QTZPICpTZiBS2WbZK5jI7dKmdNAK5D18dTQ9Wo515q+hnybQRu/sEnJepROcbrfa 56jUevOi8/g+yiu8KchNBp2BeE8YTVcVX0GXE9Lar8yJa+4Jo9EBKsqVFUCTwhWf n7qCOkbzwaiiVteYOYDBTy3M0dC/z/4K1KnBsSMYSgBaMN0eSjPuWznlZ4JFIMZQ dfAWGKFk6hJ28SvET5VVEE+QjJHAKe1kVZmyfIm8XdGQEQhty/xpU6aAr4ZRwVMj YSSEVQMq0zG+Ot3wU59I =GYuw -----END PGP SIGNATURE----- --DBUa/BSa4z6QPQv1-- From owner-freebsd-fs@freebsd.org Thu Nov 24 11:39:09 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E973C53CCD for ; Thu, 24 Nov 2016 11:39:09 +0000 (UTC) (envelope-from javocado@gmail.com) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA4F0B9F for ; Thu, 24 Nov 2016 11:39:08 +0000 (UTC) (envelope-from javocado@gmail.com) Received: by mail-lf0-x230.google.com with SMTP id t196so26594500lff.3 for ; Thu, 24 Nov 2016 03:39:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=SuedKLJ5DV/T0MWHzKGpd3ugfqPQ0yQJ6ntlC+BwHwk=; b=WI2I4lewqnRn5qZdZLErm1Sv1jkSQS3otPS9D2QaDZLxAUOW8pqi3qgMNz9jD7wfF0 5P8Kjk091IRP+jvH4MyTGo91zowbaI3/ozdRERQcSdLvZdEoyKLts5W3TltlA3SVv9Ca iJhHAZlMte/JWpEdZtyjJwJuEjSUTNEydHmPxm5h/f3ejHjjr9qU6aAwMpCLu7+RLwE5 yW5QuU/QfoWjCNk7PpLgrUCJwAMrXpmTgiQVkcjISwhjP1pVV7W8uQfcuPBvLVfGvnb5 EgvILm9cw0OlDGXt1tsE/YWm/RbugWL7oZZHWr9LS+VGLSMPiZS5cnPuBAsFveavkakv SS7g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=SuedKLJ5DV/T0MWHzKGpd3ugfqPQ0yQJ6ntlC+BwHwk=; b=evAzlolPTOs0EwyY31no87LrvakBuJieIWy1lncAGxS7k0RiZ2ORY5/MskNbv56NBA 2aB+LiHWoEkJA2VcJv0TEmKR7FE0nCzm8x3RLSVBiygYwUCetwBZqqCmbICKTNnEqPXO Im0hwjlNaNs7nsm7ZPM91jrjXbXkF0VHQopDrAmZ8sXaf4ZsUmn3mLy0xJSOGYDx7L59 +/m/XUTLHiWLnZ0dHkOP5qwCWB6ABZOFyF9zeKG+vTP72KVReZirS1flJkYQIHIs5Smo oG1eF8jY1y9aMeWa2r+ZCA2adm9VJsJ1kq9VMxgJfx/MYD74kEj4KyygCMk7bBRxNMg1 mEUA== X-Gm-Message-State: AKaTC02kUqweTFdJ8XNjPhbhRNB1RdqA09/eSya+cns168yzztfP8/q7aster7M8VS/zLN2MmzQ030GxFCnJKg== X-Received: by 10.25.195.194 with SMTP id t185mr665199lff.13.1479987546432; Thu, 24 Nov 2016 03:39:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.114.78.200 with HTTP; Thu, 24 Nov 2016 03:39:05 -0800 (PST) From: javocado Date: Thu, 24 Nov 2016 03:39:05 -0800 Message-ID: Subject: mpssas_evt_handler error during zfs remove + scrub To: FreeBSD Filesystems Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 11:39:09 -0000 My system was in the process of starting my zpool ... which was rebooted during a (large) zfs destroy operation and also happened to be scrubbing too ... and it was taking it's time doing who-knows-what when suddenly on console and before the zpool is fully up and available I see: mpssas_evt_handler: allocate failed for fw_event mpssas_evt_handler: allocate failed for event_data mpssas_evt_handler: allocate failed for event_data mpssas_evt_handler: allocate failed for event_data mpssas_evt_handler: allocate failed for event_data (last message repeats every 30s or so) anybody know what this means? From owner-freebsd-fs@freebsd.org Thu Nov 24 21:08:34 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 158ABC53A1E for ; Thu, 24 Nov 2016 21:08:34 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 D0CECDC for ; Thu, 24 Nov 2016 21:08:32 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id D4E6928490 for ; Thu, 24 Nov 2016 22:08:29 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 42F4528484 for ; Thu, 24 Nov 2016 22:08:29 +0100 (CET) To: freebsd-fs@FreeBSD.org From: Miroslav Lachman <000.fbsd@quip.cz> Subject: how to clear FS cache Message-ID: <583756CC.7000506@quip.cz> Date: Thu, 24 Nov 2016 22:08:28 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 21:08:34 -0000 Is there a way to clear FS read cache between some benchmar runs? I am looking for something like this on linux $ sh -c "sync && echo 3 > /proc/sys/vm/drop_caches" Miroslav Lachman From owner-freebsd-fs@freebsd.org Thu Nov 24 21:34:45 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 049F1C54425 for ; Thu, 24 Nov 2016 21:34:45 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92ADFBDB for ; Thu, 24 Nov 2016 21:34:44 +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 uAOLYdku072041 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 24 Nov 2016 23:34:40 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua uAOLYdku072041 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id uAOLYdNp072040; Thu, 24 Nov 2016 23:34:39 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 24 Nov 2016 23:34:39 +0200 From: Konstantin Belousov To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-fs@FreeBSD.org Subject: Re: how to clear FS cache Message-ID: <20161124213439.GV54029@kib.kiev.ua> References: <583756CC.7000506@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <583756CC.7000506@quip.cz> User-Agent: Mutt/1.7.1 (2016-10-04) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 21:34:45 -0000 On Thu, Nov 24, 2016 at 10:08:28PM +0100, Miroslav Lachman wrote: > Is there a way to clear FS read cache between some benchmar runs? > > I am looking for something like this on linux > > $ sh -c "sync && echo 3 > /proc/sys/vm/drop_caches" cd /your/mount/point umount /your/mount/point First command makes the mount point busy, so the unmount fails. But before failing, it flushes everything that is not used. From owner-freebsd-fs@freebsd.org Thu Nov 24 21:44:16 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A9BD0C54740 for ; Thu, 24 Nov 2016 21:44:16 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (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 70D6611A6 for ; Thu, 24 Nov 2016 21:44:15 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 8316528461; Thu, 24 Nov 2016 22:44:13 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id E66DE28426; Thu, 24 Nov 2016 22:44:11 +0100 (CET) Subject: Re: how to clear FS cache To: Konstantin Belousov Cc: freebsd-fs@FreeBSD.org References: <583756CC.7000506@quip.cz> <20161124213439.GV54029@kib.kiev.ua> From: Miroslav Lachman <000.fbsd@quip.cz> Message-ID: <58375F2B.1000904@quip.cz> Date: Thu, 24 Nov 2016 22:44:11 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 MIME-Version: 1.0 In-Reply-To: <20161124213439.GV54029@kib.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 21:44:16 -0000 Konstantin Belousov wrote on 2016/11/24 22:34: > On Thu, Nov 24, 2016 at 10:08:28PM +0100, Miroslav Lachman wrote: >> Is there a way to clear FS read cache between some benchmar runs? >> >> I am looking for something like this on linux >> >> $ sh -c "sync && echo 3 > /proc/sys/vm/drop_caches" > > cd /your/mount/point > umount /your/mount/point > > First command makes the mount point busy, so the unmount fails. But before > failing, it flushes everything that is not used. Nice trick, thank you! :) Miroslav Lachman From owner-freebsd-fs@freebsd.org Thu Nov 24 21:55:27 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AC59AC54B32 for ; Thu, 24 Nov 2016 21:55:27 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bbn0100.outbound.protection.outlook.com [157.56.111.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D7AF18D7 for ; Thu, 24 Nov 2016 21:55:26 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0190.CANPRD01.PROD.OUTLOOK.COM (10.165.218.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.734.8; Wed, 23 Nov 2016 23:17:02 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.0734.014; Wed, 23 Nov 2016 23:17:03 +0000 From: Rick Macklem To: "freebsd-fs@freebsd.org" Subject: patch that adds a -E option to nfsstat Thread-Topic: patch that adds a -E option to nfsstat Thread-Index: AQHSRd+HBrblGvFgT0efm+4a7BloxA== Date: Wed, 23 Nov 2016 23:17:02 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-microsoft-exchange-diagnostics: 1; YTXPR01MB0190; 7:n1cLP08o7Q3PHz3KCP3CMuWtUADCYJyTQkhrlbD5nYJzem4YN00/fsqg2QG0U8P0DLmpheFIL0EqabvRCp4M9lIUvUeOCb6oWIeSPN4lfk7GcUdlCQ/7EsH01V1R6M5voLpXBFISVZpUCkppjajsjxXiAUcXWbBi/H+MUYdgcufKWi4vBGCioAK+ZxyuHZCDEVIznWYDBueXa7x0FjWsIgyGh7oUzySf4KDC620NgBBVt3QOQDSlVQWRnNq4mLJIuTQ4uUcGp78xOt90u1rh2DEnVVwv9mFiXRXcmwQgjBW7BVvwahkPX7HAd6O0aAd6I0hQfHXh1iMOAsPu6vk5Zy6GkkZfui8Rf0XuNeLezXA= x-ms-office365-filtering-correlation-id: 70f9fcbd-03da-4a15-9acb-08d413f6d579 x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:YTXPR01MB0190; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6060326)(6040307)(6045199)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(6061324)(2016111802025)(6043046)(6042181); SRVR:YTXPR01MB0190; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0190; x-forefront-prvs: 013568035E x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(199003)(189002)(54356999)(8676002)(74482002)(189998001)(101416001)(97736004)(50986999)(2351001)(7846002)(33656002)(2501003)(77096005)(305945005)(74316002)(8936002)(107886002)(102836003)(38730400001)(81156014)(81166006)(7696004)(6916009)(450100001)(6506003)(68736007)(5640700001)(9686002)(106356001)(106116001)(110136003)(86362001)(105586002)(122556002)(92566002)(2906002)(3280700002)(5660300001)(2900100001)(3660700001)(129583001); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0190; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Nov 2016 23:17:02.9210 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0190 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2016 21:55:27 -0000 Hi, I've put a patch up at: https://reviews.freebsd.org/D8626 that adds a "-E" option to nfsstat (similar to -e) that also displays stats for NFSV4.1. It also doesn't clip the counts at 1 billion. If anyone is interested in testing and/or reviewing this, please do so. (Feel free to add yourself as a reviewer.) rick