From owner-freebsd-fs@FreeBSD.ORG Sun Aug 31 00:17:52 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 904B4EB2 for ; Sun, 31 Aug 2014 00:17:52 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 77B681BCF for ; Sun, 31 Aug 2014 00:17:52 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7V0Hq2K063901 for ; Sun, 31 Aug 2014 00:17:52 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 186112] [zfs] [panic] ZFS Panic/Solaris Assert/zap.c:479 Date: Sun, 31 Aug 2014 00:17:52 +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.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: peter@FreeBSD.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 00:17:52 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186112 --- Comment #9 from Peter Wemm --- "dedup: DDT entries 1415219, size 2676 on disk, 540 in core" -> 728MB of ram to cache this. Fortunately that's a relatively small portion of your system ram. I would still be doing a zfs set dedup=off anywhere it's on. While it won't fix the on-disk dedup corruption, at least you won't risk adding to it any more. Your system is crashing trying to parse the on-disk dedup records. That's what the *_ddt_* functions are about in the traces. I can't imagine this ending well. Does a scrub find the problem? or does the scrub trigger the assertions? -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 31 00:25:13 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34163FCE for ; Sun, 31 Aug 2014 00:25:13 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B6E01C9D for ; Sun, 31 Aug 2014 00:25:13 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7V0PCE4064912 for ; Sun, 31 Aug 2014 00:25:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 186112] [zfs] [panic] ZFS Panic/Solaris Assert/zap.c:479 Date: Sun, 31 Aug 2014 00:25: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: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ler@lerctr.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 00:25:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186112 --- Comment #10 from Larry Rosenman --- scrub triggers the assertions..... currently rsyncing the volatile stuff to the new 4TB NAS mounted via NFS.... then will blow this system up and rebuild it withOUT dedupe.... -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 31 20:47:58 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B51C7B6 for ; Sun, 31 Aug 2014 20:47:58 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1273C1892 for ; Sun, 31 Aug 2014 20:47:58 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7VKlvZ2094422 for ; Sun, 31 Aug 2014 20:47:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 186112] [zfs] [panic] ZFS Panic/Solaris Assert/zap.c:479 Date: Sun, 31 Aug 2014 20:47:58 +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.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ler@lerctr.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 20:47:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186112 --- Comment #11 from Larry Rosenman --- Rebuilding ports -- no more assertions on a non-modified kernel. Thanks Peter Wemm for the input on dedup. I think we can close this one out. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Sun Aug 31 20:49:34 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8D699C6 for ; Sun, 31 Aug 2014 20:49:34 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9FD3A18AC for ; Sun, 31 Aug 2014 20:49:34 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7VKnYpS095138 for ; Sun, 31 Aug 2014 20:49:34 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 186112] [zfs] [panic] ZFS Panic/Solaris Assert/zap.c:479 Date: Sun, 31 Aug 2014 20:49:34 +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.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ler@lerctr.org X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Aug 2014 20:49:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186112 Larry Rosenman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |Overcome By Events --- Comment #12 from Larry Rosenman --- Looks like an OLD dedup corruption/mis-feature -- rebuilding the entire system from scratch cleaned it up. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Mon Sep 1 08:00:11 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2DE0B790 for ; Mon, 1 Sep 2014 08:00:11 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0E2F114C0 for ; Mon, 1 Sep 2014 08:00:11 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8180AVM088324 for ; Mon, 1 Sep 2014 08:00:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201409010800.s8180AVM088324@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 01 Sep 2014 08:00:10 +0000 Content-Type: text/plain X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Sep 2014 08:00:11 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (5 bugs) Bug 133174: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=133174 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [msdosfs] [patch] msdosfs must support multibyte international characters in file names Bug 136470: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=136470 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [nfs] Cannot mount / in read-only, over NFS Bug 139651: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139651 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [nfs] mount(8): read-only remount of NFS volume does not work Bug 144447: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144447 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [zfs] sharenfs fsunshare() & fsshare_main() non functional Bug 155411: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155411 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-fs@FreeBSD.org Status: Needs MFC Resolution: Summary: [regression] [8.2-release] [tmpfs]: mount: tmpfs : No space left on device From owner-freebsd-fs@FreeBSD.ORG Tue Sep 2 17:24:57 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 29EFFBBB for ; Tue, 2 Sep 2014 17:24:57 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1147B1990 for ; Tue, 2 Sep 2014 17:24:57 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s82HOuM5095993 for ; Tue, 2 Sep 2014 17:24:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 189355] [zfs] zfs panic on root mount 10-stable Date: Tue, 02 Sep 2014 17:24:57 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hsn@sendmail.cz X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Sep 2014 17:24:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189355 Radim Kolar changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Issue Resolved Resolution|--- |Works As Intended -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Wed Sep 3 13:20:55 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3CEA463 for ; Wed, 3 Sep 2014 13:20:55 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 963CF1763 for ; Wed, 3 Sep 2014 13:20:55 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XPAUW-0002F6-DI for freebsd-fs@freebsd.org; Wed, 03 Sep 2014 15:20:52 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-fs@freebsd.org Date: Wed, 03 Sep 2014 15:20:51 +0200 Subject: external zfs disk keeps writing MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.2 X-Scan-Signature: 0cb660a7d4ce909c6359c48b0bded22a X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 13:20:55 -0000 Hello, I have a disk with ZFS which always writes something every 'vfs.zfs.txg.timeout' seconds. By default that is 5 seconds. If I make it 30 I see writing in gstat every 30 seconds. I only do a backup by zfs send | zfs recv hourly on this disk. So I don't understand why it still writes something every 5 seconds while I am not doing anything to this disk. How can I debug what is being written every 5 seconds? Some info: I am running FreeBSD 10-STABLE. The disk is an external disk connected by USB. ugen3.2: at usbus3 umass0: on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:4:0:-1: Attached to scbus4 da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) da0: quirks=0x2 Occasionally I have a message like this, but it does not seem to hurt anything, so it is probably unrelated. # bzgrep da0 /var/log/messages* /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 03 66 00 00 02 00 /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: (da0:umass-sim0:0:0:0): Retrying command # zpool status extern pool: extern state: ONLINE scan: scrub repaired 454K in 4h36m with 0 errors on Sat Aug 9 08:53:27 2014 config: NAME STATE READ WRITE CKSUM extern ONLINE 0 0 0 da0 ONLINE 0 0 0 errors: No known data errors I just created a zpool on da0 so there is no partition table. Regards, Ronald. From owner-freebsd-fs@FreeBSD.ORG Wed Sep 3 13:57:14 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AC2AA843 for ; Wed, 3 Sep 2014 13:57:14 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7CFE21C50 for ; Wed, 3 Sep 2014 13:57:14 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id rd18so9720414iec.27 for ; Wed, 03 Sep 2014 06:57:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iNXFS6jQKyiE881O8LlEIDhlzQZn9rr4mqbxP2I2vfY=; b=x0i8+kP/raoCFPDdSTgFTqKnl/BlZYFW3tE87uIQO8t0YXSlzmkute9HeLA+tJIoNa mMdDSXMssIfD5MKj/dOWmD/UP1E8J3nMxnqqig/EZXfTe+gNGx/6cGgecEBOGFH+Eupc o0ST17IMG3hWLwFTLScTAHh/i8ERNRzGqpgkRg64OBc19BAwAeDcy1aSJZ5oluk9TMPC pYHJtsoBtiMeV88XERxzMKOWCIpFF0q0QrBdAJRT7Nju79qkHKPJyXtuK/jZ+JMywBqb Cb6Zknda1UBoowhpoQEXNOtV/a6mNLMKw55ZtfRKagtV83ViwYyRTWm8AqrDqia4mm1w jLig== MIME-Version: 1.0 X-Received: by 10.50.20.225 with SMTP id q1mr37782099ige.36.1409752633470; Wed, 03 Sep 2014 06:57:13 -0700 (PDT) Received: by 10.107.1.19 with HTTP; Wed, 3 Sep 2014 06:57:13 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Sep 2014 14:57:13 +0100 Message-ID: Subject: Re: external zfs disk keeps writing From: Tom Evans To: Ronald Klop Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 13:57:14 -0000 On Wed, Sep 3, 2014 at 2:20 PM, Ronald Klop wrote: > Hello, > > I have a disk with ZFS which always writes something every > 'vfs.zfs.txg.timeout' seconds. By default that is 5 seconds. If I make it 30 > I see writing in gstat every 30 seconds. > I only do a backup by zfs send | zfs recv hourly on this disk. So I don't > understand why it still writes something every 5 seconds while I am not > doing anything to this disk. > > How can I debug what is being written every 5 seconds? > > > Some info: > > I am running FreeBSD 10-STABLE. The disk is an external disk connected by > USB. > > ugen3.2: at usbus3 > umass0: on usbus3 > umass0: SCSI over Bulk-Only; quirks = 0x4100 > umass0:4:0:-1: Attached to scbus4 > da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) > da0: quirks=0x2 > > Occasionally I have a message like this, but it does not seem to hurt > anything, so it is probably unrelated. > > # bzgrep da0 /var/log/messages* > /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: > (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 03 66 00 00 02 00 > /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: > (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error > /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: > (da0:umass-sim0:0:0:0): Retrying command > > # zpool status extern > pool: extern > state: ONLINE > scan: scrub repaired 454K in 4h36m with 0 errors on Sat Aug 9 08:53:27 > 2014 > config: > > NAME STATE READ WRITE CKSUM > extern ONLINE 0 0 0 > da0 ONLINE 0 0 0 > > errors: No known data errors > > I just created a zpool on da0 so there is no partition table. > zfs set atime=off extern? Cheers Tom From owner-freebsd-fs@FreeBSD.ORG Wed Sep 3 14:12:25 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4EAB375D for ; Wed, 3 Sep 2014 14:12:25 +0000 (UTC) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DE961E7C for ; Wed, 3 Sep 2014 14:12:24 +0000 (UTC) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from ) id 1XPBIM-00082d-E4; Wed, 03 Sep 2014 16:12:22 +0200 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Tom Evans" Subject: Re: external zfs disk keeps writing References: Date: Wed, 03 Sep 2014 16:12:21 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.3.2 X-Scan-Signature: 4868b52b90b9144be14ceb212c82ef23 Cc: FreeBSD FS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 14:12:25 -0000 On Wed, 03 Sep 2014 15:57:13 +0200, Tom Evans wrote: > On Wed, Sep 3, 2014 at 2:20 PM, Ronald Klop wrote: >> Hello, >> >> I have a disk with ZFS which always writes something every >> 'vfs.zfs.txg.timeout' seconds. By default that is 5 seconds. If I make >> it 30 >> I see writing in gstat every 30 seconds. >> I only do a backup by zfs send | zfs recv hourly on this disk. So I >> don't >> understand why it still writes something every 5 seconds while I am not >> doing anything to this disk. >> >> How can I debug what is being written every 5 seconds? >> >> >> Some info: >> >> I am running FreeBSD 10-STABLE. The disk is an external disk connected >> by >> USB. >> >> ugen3.2: at usbus3 >> umass0: on usbus3 >> umass0: SCSI over Bulk-Only; quirks = 0x4100 >> umass0:4:0:-1: Attached to scbus4 >> da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 >> da0: Fixed Direct Access SCSI-0 device >> da0: 40.000MB/s transfers >> da0: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) >> da0: quirks=0x2 >> >> Occasionally I have a message like this, but it does not seem to hurt >> anything, so it is probably unrelated. >> >> # bzgrep da0 /var/log/messages* >> /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: >> (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 00 03 66 00 00 02 00 >> /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: >> (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error >> /var/log/messages.0.bz2:Sep 2 16:49:45 sjakie kernel: >> (da0:umass-sim0:0:0:0): Retrying command >> >> # zpool status extern >> pool: extern >> state: ONLINE >> scan: scrub repaired 454K in 4h36m with 0 errors on Sat Aug 9 >> 08:53:27 >> 2014 >> config: >> >> NAME STATE READ WRITE CKSUM >> extern ONLINE 0 0 0 >> da0 ONLINE 0 0 0 >> >> errors: No known data errors >> >> I just created a zpool on da0 so there is no partition table. >> > > zfs set atime=off extern? > > Cheers > > Tom Yes, atime is off. Ronald. From owner-freebsd-fs@FreeBSD.ORG Wed Sep 3 17:52:43 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A168A612 for ; Wed, 3 Sep 2014 17:52:43 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8841A1CDA for ; Wed, 3 Sep 2014 17:52:43 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s83Hqhlr058709 for ; Wed, 3 Sep 2014 17:52:43 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 144234] [zfs] Cannot boot machine with recent gptzfsboot code [regression] Date: Wed, 03 Sep 2014 17:52:43 +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: 9.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jhb@FreeBSD.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: jhb@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 17:52:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=144234 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-fs@FreeBSD.org |jhb@FreeBSD.org --- Comment #8 from John Baldwin --- Created attachment 146742 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=146742&action=edit stable_10.patch Sorry, this additional patch is relative to stable/10 and should apply to 10.0 (drv.c hasn't changed in stable/10 since 10.0 was branched). This includes both of the previous patches. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-fs@FreeBSD.ORG Fri Sep 5 00:21:55 2014 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F7B0D70; Fri, 5 Sep 2014 00:21:55 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 039FD1B41; Fri, 5 Sep 2014 00:21:54 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id s850Ll7d029146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 4 Sep 2014 17:21:47 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <54090215.4080006@freebsd.org> Date: Thu, 04 Sep 2014 17:21:41 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: FreeBSD Current , fs@freebsd.org Subject: fuse libfuse and teh fuse_mount call with options 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.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Sep 2014 00:21:55 -0000 the documentation for using the fuse library seems a bit light.. I want to stop a fuse filesystem from getting cached by the buffer cache. (the data is dynamic) mount_fuse(8) says I need to add the direct-io mount option, but the mount is being done by the library call fuse_mount(). I've been hunting around for examples of how to use this argument when using the library call. the code curently looks like: [...] char *mp = arg; /* mountpoint */ struct fuse_args *farg = NULL; #ifdef DP_DEBUG /* enable fuse debugging */ struct fuse_args fa; char *argv[3]; argv[0] = "dp"; argv[1] = "-d"; argv[2] = NULL; fa.argc = 2; fa.argv = argv; fa.allocated = FALSE; farg = &fa; #endif /* DP_PROC_DEBUG */ /* unmount root (if stale) */ dp_proc_unmount(mp); /* record load time */ dp_proc_create_time = time(NULL); /* mount fuse filesystem */ fc = fuse_mount(mp, farg); if (!fc) { printk("%s: fuse_mount() failed\n", __FUNCTION__); ASSERT(!"fuse_mount failed"); return -1; } ====== dp -d seems to be the arguments to the daemon supplying data. So I'm not really seeing a place to add "-o direct-io" Our current work-around is to simply hack the fuse kernel module to just disable the calls to the buffer cache. I'd rather 'turn it off' than hack it off. documetation of this library seems really thin on the ground. As are examples. any help appreciated. Julian From owner-freebsd-fs@FreeBSD.ORG Sat Sep 6 21:40:28 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 38B467C2 for ; Sat, 6 Sep 2014 21:40:28 +0000 (UTC) Received: from quine.pinyon.org (quine.pinyon.org [65.101.5.249]) (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 124051971 for ; Sat, 6 Sep 2014 21:40:27 +0000 (UTC) Received: by quine.pinyon.org (Postfix, from userid 122) id 518D61602F1; Sat, 6 Sep 2014 14:40:21 -0700 (MST) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on quine.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Received: from feyerabend.n1.pinyon.org (feyerabend.n1.pinyon.org [10.0.10.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by quine.pinyon.org (Postfix) with ESMTPSA id 59B4E160155 for ; Sat, 6 Sep 2014 14:40:18 -0700 (MST) Message-ID: <540B7F42.5070803@pinyon.org> Date: Sat, 06 Sep 2014 14:40:18 -0700 From: "Russell L. Carter" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: pefs doesn't work as regular user Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Sep 2014 21:40:28 -0000 Greetings, So this is odd. I followed the instructions at http://www.bsdnow.tv/tutorials/pefs on one system, and as a regular user it works fine. But I try it on my laptop, and I get the following: rcarter@knuth> kldstat -m pefs Id Refs Name 27 1 pefs rcarter@knuth> mkdir ~/docs rcarter@knuth> pefs addchain -f -Z ~/docs Enter parent key passphrase: Reenter parent key passphrase: rcarter@knuth> pefs mount ~/docs ~/docs pefs mount: /home/rcarter/docs: Operation not permitted rcarter@knuth> sudo pefs mount ~/docs ~/docs rcarter@knuth> pefs unmount ~/docs pefs unmount: unmount of /usr/home/rcarter/docs failed: Operation not permitted rcarter@knuth> sudo pefs unmount ~/docs rcarter@knuth> /bin/rm -rf ~/docs rcarter@knuth> So it works as root but not as $USER. I don't see anything different about /etc/group on either system. Any ideas? Thanks, Russell