From owner-freebsd-fs@freebsd.org Mon Jan 29 13:06:18 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6FFA0EC5DA7 for ; Mon, 29 Jan 2018 13:06:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0657A71EDF for ; Mon, 29 Jan 2018 13:06:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 323D6104C6 for ; Mon, 29 Jan 2018 13:06:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0TD6HJq056989 for ; Mon, 29 Jan 2018 13:06:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0TD6Hgx056987 for freebsd-fs@FreeBSD.org; Mon, 29 Jan 2018 13:06:17 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: freebsd-fs@FreeBSD.org Subject: [Bug 225423] panic: softdep_deallocate_dependencies: dangling deps Date: Mon, 29 Jan 2018 13:06:17 +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-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: deepak.ukey@microsemi.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jan 2018 13:06:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225423 --- Comment #3 from Deepak Ukey --- (In reply to Kirk McKusick from comment #1) Thanks for the patch. I applied the patch and ran the same test but still i= am facing system crash. Please find below crash dump.=20 Device da0p1 went missing before all of the data could be written to it; ex= pect data loss. panic: devfs_fsync: vop_stdfsync failed. cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff80b24077 at kdb_backtrace+0x67 #1 0xffffffff80ad93e2 at vpanic+0x182 #2 0xffffffff80ad9253 at panic+0x43 #3 0xffffffff80985bdf at devfs_fsync+0x8f #4 0xffffffff8110cbcd at VOP_FSYNC_APV+0x8d #5 0xffffffff80bb2dfe at sched_sync+0x3be #6 0xffffffff80a90055 at fork_exit+0x85 #7 0xffffffff80f847fe at fork_trampoline+0xe Uptime: 6m4s Thanks Deepak --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jan 30 16:24:20 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 963AFED38F5 for ; Tue, 30 Jan 2018 16:24:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9D6407432E for ; Tue, 30 Jan 2018 16:24:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D2C541E9CF for ; Tue, 30 Jan 2018 16:24:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0UGOIvJ067829 for ; Tue, 30 Jan 2018 16:24:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0UGOI2N067827 for freebsd-fs@FreeBSD.org; Tue, 30 Jan 2018 16:24:18 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: freebsd-fs@FreeBSD.org Subject: [Bug 225223] "zfs rename -r" of a snapshot doesn't rename zvol snapshots' device nodes Date: Tue, 30 Jan 2018 16:24:18 +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 Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 16:24:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225223 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: asomers Date: Tue Jan 30 16:24:15 UTC 2018 New revision: 328592 URL: https://svnweb.freebsd.org/changeset/base/328592 Log: Mark zvol_misc_007_pos and zvol_misc_008_pos as expected failures PR: 225223 PR: 225200 Sponsored by: Spectra Logic Corp Changes: projects/zfsd/head/tests/sys/cddl/zfs/tests/zvol/zvol_misc/zvol_misc_test= .sh --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Jan 30 16:25:22 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B38B3ED39C4 for ; Tue, 30 Jan 2018 16:25:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 52FE074482 for ; Tue, 30 Jan 2018 16:25:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id A83371E9D1 for ; Tue, 30 Jan 2018 16:25:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0UGPLiI069563 for ; Tue, 30 Jan 2018 16:25:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0UGPLeJ069562 for freebsd-fs@FreeBSD.org; Tue, 30 Jan 2018 16:25:21 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: freebsd-fs@FreeBSD.org Subject: [Bug 225200] "zfs promote" of a zvol doesn't rename device nodes for snapshots Date: Tue, 30 Jan 2018 16:25:21 +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 Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jan 2018 16:25:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225200 --- Comment #1 from commit-hook@freebsd.org --- A commit references this bug: Author: asomers Date: Tue Jan 30 16:24:15 UTC 2018 New revision: 328592 URL: https://svnweb.freebsd.org/changeset/base/328592 Log: Mark zvol_misc_007_pos and zvol_misc_008_pos as expected failures PR: 225223 PR: 225200 Sponsored by: Spectra Logic Corp Changes: projects/zfsd/head/tests/sys/cddl/zfs/tests/zvol/zvol_misc/zvol_misc_test= .sh --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Jan 31 08:01:50 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24953EE18B5 for ; Wed, 31 Jan 2018 08:01:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 31C587883E for ; Wed, 31 Jan 2018 08:01: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 539B526CA2 for ; Wed, 31 Jan 2018 08:01:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0V81mGw039936 for ; Wed, 31 Jan 2018 08:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0V81m1N039935 for freebsd-fs@FreeBSD.org; Wed, 31 Jan 2018 08:01:48 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223803] zio_done() panic on system with cache devices Date: Wed, 31 Jan 2018 08:01: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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: demis@yandex.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 08:01:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223803 --- Comment #9 from Demis --- (In reply to Andriy Gapon from comment #6) I'm update system to uname -imrs FreeBSD 11.1-STABLE amd64 And apply whithout errors patch. svn info /usr/src Path: /usr/src Working Copy Root Path: /usr/src URL: svn://svn.freebsd.org/base/stable/11 Relative URL: ^/stable/11 Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 328212 Node Kind: directory Schedule: normal Last Changed Author: kp Last Changed Rev: 328210 Last Changed Date: 2018-01-21 02:46:03 +0300 (=D0=B2=D1=81, 21 =D1=8F=D0=BD= =D0=B2. 2018) Not so fast for get result. On FreeBSD 10.3 amd64 list of previos panic in my case: -rw------- 1 root wheel 24761 20 May 2016 core.txt.5 -rw------- 1 root wheel 300884 9 Feb 2017 core.txt.6 -rw------- 1 root wheel 329938 27 Aug 03:37 core.txt.7 -rw------- 1 root wheel 337428 15 Nov 03:23 core.txt.8 Now system uninteruble work uptime 10:56 up 7 days, 16:20, 2 users, load averages: 5,09 5,09 5,08 It is necessary to wait two three months of continuous work. Thanks for your work. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Jan 31 18:46:00 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F402EDBD5F for ; Wed, 31 Jan 2018 18:46:00 +0000 (UTC) (envelope-from mi+b@aldan.algebra.com) Received: from symbion.zaytman.com (symbion.zaytman.com [64.112.176.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "symbion", Issuer "Narawntapu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1E0E172F75 for ; Wed, 31 Jan 2018 18:45:59 +0000 (UTC) (envelope-from mi+b@aldan.algebra.com) Received: from narawntapu.narawntapu (pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28]) by symbion.zaytman.com (8.15.2/8.15.2) with ESMTPS id w0VIVb0U063313 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 31 Jan 2018 13:31:37 -0500 (EST) (envelope-from mi+b@aldan.algebra.com) X-Authentication-Warning: symbion.zaytman.com: Host pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28] claimed to be narawntapu.narawntapu Received: from [127.0.0.1] (localhost [127.0.0.1]) by narawntapu.narawntapu (8.15.2/8.15.2) with ESMTP id w0VIVag0094994 for ; Wed, 31 Jan 2018 13:31:36 -0500 (EST) (envelope-from mi+b@aldan.algebra.com) X-Authentication-Warning: narawntapu.narawntapu: Host localhost [127.0.0.1] claimed to be [127.0.0.1] To: freebsd-fs@FreeBSD.org From: "Mikhail T." Subject: Need help with sysutils/fusefs-smbnetfs Message-ID: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> Date: Wed, 31 Jan 2018 13:31:35 -0500 User-Agent: Firefox MIME-Version: 1.0 Content-Language: uk X-DCC-Etherboy-Metrics: narawntapu 1002; IP=ok Body=1 Fuz1=1 Fuz2=1 X-Spam-Status: No, score=-2.9 required=7.5 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on narawntapu.narawntapu Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 18:46:00 -0000 Hello! I've recently become a user, and then the maintainer of the fuse-smbnetfs port. With the mount_smbfs becoming increasingly obsolete, the port seems like the only solution for accessing Windows shares from a FreeBSD system. The problem is very poor performance. The software uses Samba's libsmbclient and thus should be capable of throughput comparable to that of smbclient. Unfortunately, the same files I can get here at about 20MB/second with smbclient, can only be accessed at about 500KB/s with smbnetfs. If I use the "direct_io" flag to mount, the read bandwidth jumps to 5-8MB/s, which represents an impressive gain, but is still far below smbclient's performance. The very fact, that the "direct_io" flag makes such a profound difference, made me think, the software's interface with our FUSE implementation may be at fault... The upstream developer primarily works with Linux -- and is not very responsive at any rate. Can any of the FreeBSD's FUSE-developers take a look at the port -- the codebase is not very large -- and suggest any optimizations? Feel free to contact me directly with any ideas and/or patches. Thank you. Yours, -mi From owner-freebsd-fs@freebsd.org Wed Jan 31 20:20:12 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C83C8EDFB12 for ; Wed, 31 Jan 2018 20:20:12 +0000 (UTC) (envelope-from mqudsi@neosmart.net) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 66A1C76644 for ; Wed, 31 Jan 2018 20:20:12 +0000 (UTC) (envelope-from mqudsi@neosmart.net) Received: by mail-ot0-x22c.google.com with SMTP id 73so5500975oti.12 for ; Wed, 31 Jan 2018 12:20:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=neosmart.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C+RTu+l4umaITIHuNPgS7YWCih3g3+JZBKZNRI+jt1I=; b=dZRq/ZSScp5S9frNU95AIlIlJM44yIb/5I/ugW2423mcC53CVIXziTD7bOXiJ1yyeK u7Pgnnp3rB/kkmxzQhp89DJteKdHvP9Im/6u+gOqrs92oLDAnemH09wqtD/CPjRag5DQ l1pu8ho6Fer3biRAPSC6rLRVUn7VtfrGBYwvs= 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=C+RTu+l4umaITIHuNPgS7YWCih3g3+JZBKZNRI+jt1I=; b=ax7tXQXVRH8wpHOcmTnKzYaKGj24aNzrvo5XMKXm+hn8gwAMjHZR+qWnGwuaMM6ZvH tI5LxZsRG7dV8q+R3xxC+sWIo/wZAxvn7g/Pt1vpQbL79QcFPbnDnzpx/uMXMWOvchT8 TQ/WQHNFn2/bGqmIy1iGr3XlefgBPej8gGPtOmqdbg2WNlpjQEmH7wBRxBF3pnlzYYCw JHYFuK6ionaUEUC31TBFYddxAYXmzHphBG8j4l0OKJqnC7Re7OPt68uvRd0aGuTfcgvz 25g0Y9CewaGER/oM0aG1JMMiMH6IijWDwn9AuoIb3gW87V5paBDj/P0Y6NcNZmJbwcKo STLQ== X-Gm-Message-State: AKwxytf+nNJhqy6vIZwc+EaKgjqzTUXtOnpr7MBc5f16M7PiU7WJJpdZ 2yIhOf9vXWh77xiUiAp0q3+YD7x93S5veENyn9GrQOpx X-Google-Smtp-Source: AH8x227NrxaMo161SOP1JByHT1CDlDpJx/OCSA8jK1e5XjxQGfB75d+UNHEmXb79F3UpngpvYa9D/y0nsc3a5pxlrJ0= X-Received: by 10.157.58.116 with SMTP id j107mr23875945otc.238.1517430011670; Wed, 31 Jan 2018 12:20:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.61.230 with HTTP; Wed, 31 Jan 2018 12:19:51 -0800 (PST) In-Reply-To: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> From: Mahmoud Al-Qudsi Date: Wed, 31 Jan 2018 14:19:51 -0600 Message-ID: Subject: Re: Need help with sysutils/fusefs-smbnetfs To: "Mikhail T." Cc: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 20:20:12 -0000 On Wed, Jan 31, 2018 at 12:31 PM, Mikhail T. wrote: > The upstream developer primarily works with Linux -- and is not very > responsive at any rate. Can any of the FreeBSD's FUSE-developers take a look > at the port -- the codebase is not very large -- and suggest any > optimizations? How does the performance vary with changes to samba_max_rw_block_size? I only took a cursory glance at the upstream code (ugh, sourceforge) but it acquires a mutex to lock the samba context for each loop in read/write. I could be wrong (never worked with smb code before!) but from what I can see in the `get_ctx` function, it doesn't seem that the context needs to be shared at all: it looks like a new context can instead be obtained for each transfer, (not chunk) eliminating the need to lock and unlock repeatedly in a loop. Mahmoud Al-Qudsi NeoSmart Technologies From owner-freebsd-fs@freebsd.org Thu Feb 1 01:36:17 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1856ECC3C3 for ; Thu, 1 Feb 2018 01:36:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F37E82AFC for ; Thu, 1 Feb 2018 01:36:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 920C8104ED for ; Thu, 1 Feb 2018 01:36:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w111aGUL080392 for ; Thu, 1 Feb 2018 01:36:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w111aGuq080391 for freebsd-fs@FreeBSD.org; Thu, 1 Feb 2018 01:36:16 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: freebsd-fs@FreeBSD.org Subject: [Bug 225423] panic: softdep_deallocate_dependencies: dangling deps Date: Thu, 01 Feb 2018 01:36:16 +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-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 01:36:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225423 --- Comment #4 from Kirk McKusick --- Created attachment 190238 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D190238&action= =3Dedit 10-current patch for lost disk panic Please try this patch on your 10-current system. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Feb 1 08:48:44 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23C3CED23E4 for ; Thu, 1 Feb 2018 08:48:44 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout02.t-online.de (mailout02.t-online.de [194.25.134.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B2D167F8E8 for ; Thu, 1 Feb 2018 08:48:43 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd35.aul.t-online.de (fwd35.aul.t-online.de [172.20.27.145]) by mailout02.t-online.de (Postfix) with SMTP id 0E84141B5888; Thu, 1 Feb 2018 09:48:36 +0100 (CET) Received: from Stefans-MBP-LAN.fritz.box (XjqZbqZbZh9UdN4DSttCJbaDNrb0FbR3h9DZ210kVocK6NGCAIg8UvkkgJpENL+Qhx@[87.151.209.224]) by fwd35.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1ehAXe-1ipV200; Thu, 1 Feb 2018 09:48:22 +0100 Subject: Re: Need help with sysutils/fusefs-smbnetfs To: "Mikhail T." References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> From: Stefan Esser Cc: freebsd-fs@freebsd.org Message-ID: Date: Thu, 1 Feb 2018 09:48:22 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: XjqZbqZbZh9UdN4DSttCJbaDNrb0FbR3h9DZ210kVocK6NGCAIg8UvkkgJpENL+Qhx X-TOI-MSGID: 8f87cb29-84f5-4f1e-a908-12ed2bca3974 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 08:48:44 -0000 Am 31.01.18 um 19:31 schrieb Mikhail T.: > Hello! > > I've recently become a user, and then the maintainer of the fuse-smbnetfs > port. With the mount_smbfs becoming increasingly obsolete, the port seems like > the only solution for accessing Windows shares from a FreeBSD system. > > The problem is very poor performance. The software uses Samba's libsmbclient > and thus should be capable of throughput comparable to that of smbclient. > Unfortunately, the same files I can get here at about 20MB/second with > smbclient, can only be accessed at about 500KB/s with smbnetfs. > > If I use the "direct_io" flag to mount, the read bandwidth jumps to 5-8MB/s, > which represents an impressive gain, but is still far below smbclient's > performance. > > The very fact, that the "direct_io" flag makes such a profound difference, > made me think, the software's interface with our FUSE implementation may be at > fault... Our FUSE kernel code lacks a number of features offered by Linux. This can be tested by file systems (at compile time, by checking the FUSE kernel version in fuse_common.h and at run-time by querying for capabilities of the kernel code, see FUSE_CAP_*). IIRC, FreeBSD does not provide FUSE_CAP_WRITEBACK_CACHE, for example (but that should not affect read performance as much as you noticed). > The upstream developer primarily works with Linux -- and is not very > responsive at any rate. Can any of the FreeBSD's FUSE-developers take a look > at the port -- the codebase is not very large -- and suggest any optimizations? Did you test with version 3 of the FUSE library? The port should be converted to that version, anyway, since development of version 2 has stopped. The developer and maintainer of libfuse3 has made some effort to get it working on FreeBSD (e.g. installed FreeBSD in a VM for debugging), even though he works on Linux only, in general. You can contact him at: Nikolaus Rath It might be possible to speed up ports that use libfuse3 by adding some of the features that are disabled due to lack of kernel support (to the kernel) - but I know that some need changes to system call semantics that we probably do not want to implement in FreeBSD (e.g. openat(O_PATH), but that one should not be the cause of any performance problems you see). > Feel free to contact me directly with any ideas and/or patches. Sorry, I have no specific ideas or patches to offer. You should identify the bottlenecks (with libfuse3) and check, whether they are due to missing kernel features or sub-optimal FreeBSD support in libfuse3. Nikolaus will probably accept changes to libfuse3 that improve performance on FreeBSD, since he is interested on seeing it work well on other platforms than Linux. Regards, STefan From owner-freebsd-fs@freebsd.org Thu Feb 1 19:08:21 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3597CEE61AB for ; Thu, 1 Feb 2018 19:08:21 +0000 (UTC) (envelope-from mi+b@aldan.algebra.com) Received: from symbion.zaytman.com (symbion.zaytman.com [64.112.176.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "symbion", Issuer "Narawntapu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C9BEF7E899; Thu, 1 Feb 2018 19:08:20 +0000 (UTC) (envelope-from mi+b@aldan.algebra.com) Received: from narawntapu.narawntapu (pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28]) by symbion.zaytman.com (8.15.2/8.15.2) with ESMTPS id w11J8Dtk067260 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 14:08:13 -0500 (EST) (envelope-from mi+b@aldan.algebra.com) X-Authentication-Warning: symbion.zaytman.com: Host pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28] claimed to be narawntapu.narawntapu Received: from [127.0.0.1] (localhost [127.0.0.1]) by narawntapu.narawntapu (8.15.2/8.15.2) with ESMTP id w11J8BmL009829; Thu, 1 Feb 2018 14:08:11 -0500 (EST) (envelope-from mi+b@aldan.algebra.com) X-Authentication-Warning: narawntapu.narawntapu: Host localhost [127.0.0.1] claimed to be [127.0.0.1] Subject: Re: Need help with sysutils/fusefs-smbnetfs To: Stefan Esser Cc: freebsd-fs@freebsd.org, brendan+freebsd@bbqsrc.net References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> From: "Mikhail T." Message-ID: <2aea2d83-7c73-0965-b3be-2964a548823d@aldan.algebra.com> Date: Thu, 1 Feb 2018 14:08:11 -0500 User-Agent: Firefox MIME-Version: 1.0 In-Reply-To: Content-Language: uk X-DCC-dmv.com-Metrics: narawntapu 1095; Body=3 Fuz1=3 Fuz2=3 X-Spam-Status: No, score=-2.9 required=7.5 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on narawntapu.narawntapu Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 19:08:21 -0000 2/1/2018 3:48 AM, Stefan Esser пише: > > Did you test with version 3 of the FUSE library? The port should be > converted to that version, anyway, since development of version 2 has > stopped. > I just committed the changes necessary to build with fuse3, should the user so desire or should the default fuse-version change. However, I can not report any obvious advantages from using it at this time. Worse, because the direct_io option -- despite being documented in mount_fusefs(8) -- is not supported by fuse3, the read-throughput is now back down to hundreds of kilobytes per second... As you may remember, by using direct_io I was able to go up to 8MB/second with fuse2 (although smbclient itself could read at 20MB/s). Yours, -mi From owner-freebsd-fs@freebsd.org Thu Feb 1 19:35:32 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 701AEEE7C9B for ; Thu, 1 Feb 2018 19:35:32 +0000 (UTC) (envelope-from mi+b@aldan.algebra.com) Received: from symbion.zaytman.com (symbion.zaytman.com [64.112.176.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "symbion", Issuer "Narawntapu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B83680645; Thu, 1 Feb 2018 19:35:31 +0000 (UTC) (envelope-from mi+b@aldan.algebra.com) Received: from narawntapu.narawntapu (pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28]) by symbion.zaytman.com (8.15.2/8.15.2) with ESMTPS id w11JZTYM067329 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 1 Feb 2018 14:35:29 -0500 (EST) (envelope-from mi+b@aldan.algebra.com) X-Authentication-Warning: symbion.zaytman.com: Host pool-108-53-87-28.nwrknj.fios.verizon.net [108.53.87.28] claimed to be narawntapu.narawntapu Received: from [127.0.0.1] (localhost [127.0.0.1]) by narawntapu.narawntapu (8.15.2/8.15.2) with ESMTP id w11JZQuN010348; Thu, 1 Feb 2018 14:35:27 -0500 (EST) (envelope-from mi+b@aldan.algebra.com) X-Authentication-Warning: narawntapu.narawntapu: Host localhost [127.0.0.1] claimed to be [127.0.0.1] Subject: fusefs and /etc/fstab To: Stefan Esser Cc: freebsd-fs@freebsd.org, brendan+freebsd@bbqsrc.net References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> From: "Mikhail T." Message-ID: <42ad9c4b-9017-0955-a550-521f9e2d933d@aldan.algebra.com> Date: Thu, 1 Feb 2018 14:35:26 -0500 User-Agent: Firefox MIME-Version: 1.0 In-Reply-To: Content-Language: uk X-DCC-dmv.com-Metrics: narawntapu 1095; Body=3 Fuz1=3 Fuz2=3 X-Spam-Status: No, score=-2.9 required=7.5 tests=ALL_TRUSTED,BAYES_00, HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on narawntapu.narawntapu Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Feb 2018 19:35:32 -0000 For people trying to use fstab to mount fusefs filesystem(s), there is a problem -- the daemons expecting one argument after the options (the mount-point), are confused by there being two arguments: the "special" and the mount-point. The mount_fusefs(8) recommends using "auto" for the "special" (first field of the fstab), but that breaks too: fuse: bad mount point `auto': No such file or directory I first thought, this problem is specific to smbnetfs, but the program simply uses FUSE_ARGS_INIT(argc, argv) and otherwise relies on the libfuse library to process the command-line. The trick I found to work is to put one of the mount options into the first field: -oallow_other  /smb fusefs rw,failok,uid=105,late,mountprog=/opt/bin/smbnetfs but that's just a hack, of course. Perhaps, our libfusefs ports can be modified to, upon encountering two arguments remaining after the options, to either silently ignore the first one at all times, or only ignore it, if it says "auto"? Alternatively, maybe, mount_fusefs needs to strip the "special" off before invoking the specified daemon? -mi From owner-freebsd-fs@freebsd.org Fri Feb 2 10:27:06 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0ED80ECE7E7 for ; Fri, 2 Feb 2018 10:27:06 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id AD63284F09 for ; Fri, 2 Feb 2018 10:27:05 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (203-206-128-220.perm.iinet.net.au [203.206.128.220]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0P3I003A1QSAK500@hades.sorbs.net> for freebsd-fs@freebsd.org; Fri, 02 Feb 2018 02:36:12 -0800 (PST) Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... From: Michelle Sullivan To: Mike Tancsa Cc: "freebsd-fs@freebsd.org" References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> <54DCAC29.8000301@sorbs.net> Message-id: <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> Date: Fri, 02 Feb 2018 21:26:56 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 In-reply-to: <54DCAC29.8000301@sorbs.net> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 10:27:06 -0000 Michelle Sullivan wrote: > Michelle Sullivan wrote: >> So far (few hours in) zfs import -fFX has not faulted with this image... >> it's running out of memory currently about 16G of 32G- however 9.2-P15 >> kernel died within minutes... out of memory (all 32G and swap) so am >> more optimistic at the moment... Fingers Crossed. >> > And the answer: > > 11-STABLE on a USB stick. > > Remove the drive that was replacing the hotspare (ie the replacement > drive for the one that initially died) > zpool import -fFX storage > zpool export storage > > reboot back to 9.x > zpool import storage > re-insert drive replacement drive. > reboot > > Gotta thank people for this again, saved me again this time on a non-FreeBSD system this time (with a lot of using a modified recoverdisk for OSX - thanks PSK@)... Lost 3 disks out of a raidz2 and 2 more had read errors on some sectors.. don't know how much (if any) data I've lost but at least it's not a rebuild from back up of all 48TB.. Thanks again. -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@freebsd.org Fri Feb 2 10:43:09 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEF8CECF741 for ; Fri, 2 Feb 2018 10:43:08 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (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 60529859A1 for ; Fri, 2 Feb 2018 10:43:08 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id 143so11550172wma.5 for ; Fri, 02 Feb 2018 02:43:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=xNYVaePy82AebynkmyDBL5p7ifd5U3qn9Wec0xXI6c0=; b=W2uOqVdBrlDzcCo1OMZzQIHkteOplmBCNO5jkUH5bptjJ4xuvqksmnUynPI8T1F4BO C5l5WXCicXNmDzWHb4k0O9x6RvSJ6R+WyF1GywIzPYPHytciHnez28X48th0NQOGByZ0 /4UYegfhRGuuDui7N2P2gzgnNw85ZmKY4XX7ZzZVneOzpmFTB/c18cZUMOvm7KB+ce5c O2N7/cs8tExT3PO2xH0vxIAw6aOSSWShfB/DAj1YUBidUxUQYFLH+nkf/WcEftpEmQHx jXrg/bEVQ6oxkcIkeFqKGwz8ilvAUJetEWitCHHS5PQqML8KCXeON1TAnKp5+vhC3cRq WP7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=xNYVaePy82AebynkmyDBL5p7ifd5U3qn9Wec0xXI6c0=; b=ZlP6As5w2d4Htsv4ovyb9EHPL1ETxP83G4FYSGwP2NwTW6T+Zg3OLDjxnHeg42+zt3 OvsLYnm4CB8AwslxP8RoC3h6TvNwnZAEG1FrY4NL6uM1bobKmMhJXQJznR7Php60kv3T uCGLIl87L04MSZRDw2RGWKx9uDiGQnqVF3yhUVLunojk2yqjFQ+l3NvjhlsEmPCtZwTC LPfVhMAHw9srQm+47OShXFqfqkZmCB5mD9jOCZzlhz2T1jixO5ZLqNW/AgThXcyQkHWW vV4kZFqxbzk9sOBHMosawTqsf6IfGaKzW6KOR2L4IPlDJ4TYqsAvKPCGpYT3Eyz2P39e B3Pg== X-Gm-Message-State: AKwxytdl/Xlg5Cag1vdLbVJfURiV5WT1Znw/N0ghUXbOf3jXwvzjwHDP 6G5WxE2kBr11miwCXvTt8Psj9ilD X-Google-Smtp-Source: AH8x226GMeGGp9aZm8i3sgIJK4i+SGLOl0PccrRNnzfA7i+s2TrOzhvOpOyyPxnZOmskSSK8NQLNgw== X-Received: by 10.28.109.83 with SMTP id i80mr31146185wmc.89.1517568186871; Fri, 02 Feb 2018 02:43:06 -0800 (PST) Received: from bens-mac.home (LFbn-MAR-1-467-113.w2-15.abo.wanadoo.fr. [2.15.58.113]) by smtp.gmail.com with ESMTPSA id 104sm2921492wrl.74.2018.02.02.02.43.06 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 02 Feb 2018 02:43:06 -0800 (PST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... From: Ben RUBSON In-Reply-To: <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> Date: Fri, 2 Feb 2018 11:43:04 +0100 Content-Transfer-Encoding: 7bit Message-Id: <8282375D-5DDC-4294-A69C-03E9450D9575@gmail.com> References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> <54DCAC29.8000301@sorbs.net> <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> To: "freebsd-fs@freebsd.org" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 10:43:09 -0000 On 02 Feb 2018 11:26, Michelle Sullivan wrote: Hi Michelle, > Michelle Sullivan wrote: >> Michelle Sullivan wrote: >>> So far (few hours in) zfs import -fFX has not faulted with this image... >>> it's running out of memory currently about 16G of 32G- however 9.2-P15 >>> kernel died within minutes... out of memory (all 32G and swap) so am >>> more optimistic at the moment... Fingers Crossed. >>> >> And the answer: >> >> 11-STABLE on a USB stick. >> >> Remove the drive that was replacing the hotspare (ie the replacement >> drive for the one that initially died) >> zpool import -fFX storage >> zpool export storage >> >> reboot back to 9.x >> zpool import storage >> re-insert drive replacement drive. >> reboot > Gotta thank people for this again, saved me again this time on a > non-FreeBSD system this time (with a lot of using a modified recoverdisk > for OSX - thanks PSK@)... Lost 3 disks out of a raidz2 and 2 more had > read errors on some sectors.. don't know how much (if any) data I've lost > but at least it's not a rebuild from back up of all 48TB.. What about the root-cause ? Sounds like you had 5 disks dying at the same time ? Do you periodically run long smart tests ? Zpool scrubs ? Thx, Ben From owner-freebsd-fs@freebsd.org Fri Feb 2 10:51:15 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD11EECFDE0 for ; Fri, 2 Feb 2018 10:51:14 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id 8750985E20 for ; Fri, 2 Feb 2018 10:51:14 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (203-206-128-220.perm.iinet.net.au [203.206.128.220]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0P3I003A8RWJK500@hades.sorbs.net> for freebsd-fs@freebsd.org; Fri, 02 Feb 2018 03:00:26 -0800 (PST) Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... To: Ben RUBSON , "freebsd-fs@freebsd.org" References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> <54DCAC29.8000301@sorbs.net> <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> <8282375D-5DDC-4294-A69C-03E9450D9575@gmail.com> From: Michelle Sullivan Message-id: <73dd7026-534e-7212-a037-0cbf62a61acd@sorbs.net> Date: Fri, 02 Feb 2018 21:51:01 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 In-reply-to: <8282375D-5DDC-4294-A69C-03E9450D9575@gmail.com> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 10:51:15 -0000 Ben RUBSON wrote: > On 02 Feb 2018 11:26, Michelle Sullivan wrote: > > Hi Michelle, > >> Michelle Sullivan wrote: >>> Michelle Sullivan wrote: >>>> So far (few hours in) zfs import -fFX has not faulted with this >>>> image... >>>> it's running out of memory currently about 16G of 32G- however 9.2-P15 >>>> kernel died within minutes... out of memory (all 32G and swap) so am >>>> more optimistic at the moment... Fingers Crossed. >>>> >>> And the answer: >>> >>> 11-STABLE on a USB stick. >>> >>> Remove the drive that was replacing the hotspare (ie the replacement >>> drive for the one that initially died) >>> zpool import -fFX storage >>> zpool export storage >>> >>> reboot back to 9.x >>> zpool import storage >>> re-insert drive replacement drive. >>> reboot >> Gotta thank people for this again, saved me again this time on a >> non-FreeBSD system this time (with a lot of using a modified >> recoverdisk for OSX - thanks PSK@)... Lost 3 disks out of a raidz2 >> and 2 more had read errors on some sectors.. don't know how much (if >> any) data I've lost but at least it's not a rebuild from back up of >> all 48TB.. > > What about the root-cause ? 3 disks died whilst the server was in transit from Malta to Australia (and I'm surprised that was all considering the state of some of the stuff that came out of the container - have a 3kva UPS that is completely destroyed despite good packing.) > Sounds like you had 5 disks dying at the same time ? Turns out that one of the 3 that had 'red lights on' had bad sectors, the other 2 were just excluded by the BIOS... I did a byte copy onto new drives found no read errors so put them back in and forced them online. The other 1 had 78k of bytes unreadable so new disk went in and an convinced the controller that it was the same disk as the one it replaced, the export/import produced 2 more disks unrecoverable read errors that nothing had flagged previously, so byte copied them onto new drives and the import -fFX is currently working (5 hours so far)... > Do you periodically run long smart tests ? Yup (fully automated.) > Zpool scrubs ? > Both servers took a zpool scrub before they were packed into the containers... the second one came out unscathed... but then most stuff in the second container came out unscathed unlike the first.... Regards, -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@freebsd.org Fri Feb 2 16:12:06 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3CDD1EE14A0 for ; Fri, 2 Feb 2018 16:12:06 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (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 9ED8571AFE for ; Fri, 2 Feb 2018 16:12:05 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id g1so13687075wmg.2 for ; Fri, 02 Feb 2018 08:12:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=dBa/yMdx6UX1aeD9NcSfriEjh6/EApfZa0CM0crQLzs=; b=Wb9emGNi6q8y0ooORDvnp/bWimKNU3uZNz+oEKCcDEQ2bKE0P27lb6SSoEQutXiMZb dc+aD+Q/1gtM38pgFap3zyKYdYygJOME7Z4LiO1JnzkyZkn9o+KS802TZ4Qn5M0TOs4P kzrUb9GQLSosZRfMdenkgCoWwdUwyBPsk2OZOegPkLopLszLd9hF2pTv2kIzBJZR/yMj KfAhKCYUDV+KCw3tY1ul4RWF2Inuh/Ov7lbtV31ua2/lJV9SuYCizW3oTLMgsSNc6e6j CogxwKXj+KUjnbP2AxH1JIEQMPbj+s1mwxs8POYsLGEhLyUWEyM0eXn1+E96UAL5+JYw xWfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=dBa/yMdx6UX1aeD9NcSfriEjh6/EApfZa0CM0crQLzs=; b=iq5pHWVDrw04P3q9GbIqZdwKHIa8yE9dXQtmNyuPzDi64NYQuZ17CX+u/R6X12pYei 8IayZpYnFyc61L2X/8zldpExOTNRap0QZna/RaqyMYuHlPCWgL+wTCDPVX3gSjUXo6yx a5Wny+IMSHzhx39vj7EhKfVQhUIVbp8QN7X/N3Bk8LeGi0fbpxic087UkrY6BkjIClix c1Z3biVfKBE2/Otxpp1PmnrJUYE5ApfMO2IhSfwI+yGV9IoAC9gaNkYMJgdp/0fXaDty zR4AjfFGqwv9SLcRQ/ngNv5X1wBGwRGjm0NH4IENF2kTgyXzMLO1c6Bvj2HZRRPutbbw S9iQ== X-Gm-Message-State: AKwxytdkf+v/s2+q6MHDZOJT5xORdEvhXSbsmXCo/8/yhDTJOUYVanQa BrFq0fRMFvYPowoDS+jMSNWaF5ol X-Google-Smtp-Source: AH8x224Y7FCrhjfVWAZ1wV9iZSpm6gd12q0sMtAtEgCGCU8qOhtwR9mcu4x7hh+yrk2iKxYtYP/DCA== X-Received: by 10.28.150.86 with SMTP id y83mr23361250wmd.42.1517587924429; Fri, 02 Feb 2018 08:12:04 -0800 (PST) Received: from bens-mac.home (LFbn-MAR-1-467-113.w2-15.abo.wanadoo.fr. [2.15.58.113]) by smtp.gmail.com with ESMTPSA id b9sm1202524wmc.14.2018.02.02.08.12.02 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 02 Feb 2018 08:12:03 -0800 (PST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... From: Ben RUBSON In-Reply-To: <73dd7026-534e-7212-a037-0cbf62a61acd@sorbs.net> Date: Fri, 2 Feb 2018 17:12:01 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> <54DCAC29.8000301@sorbs.net> <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> <8282375D-5DDC-4294-A69C-03E9450D9575@gmail.com> <73dd7026-534e-7212-a037-0cbf62a61acd@sorbs.net> To: "freebsd-fs@freebsd.org" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 16:12:06 -0000 On 02 Feb 2018 11:51, Michelle Sullivan wrote: > Ben RUBSON wrote: >> On 02 Feb 2018 11:26, Michelle Sullivan wrote: >> >> Hi Michelle, >> >>> Michelle Sullivan wrote: >>>> Michelle Sullivan wrote: >>>>> So far (few hours in) zfs import -fFX has not faulted with this >>>>> image... >>>>> it's running out of memory currently about 16G of 32G- however 9.2-P15 >>>>> kernel died within minutes... out of memory (all 32G and swap) so am >>>>> more optimistic at the moment... Fingers Crossed. >>>> And the answer: >>>> >>>> 11-STABLE on a USB stick. >>>> >>>> Remove the drive that was replacing the hotspare (ie the replacement >>>> drive for the one that initially died) >>>> zpool import -fFX storage >>>> zpool export storage >>>> >>>> reboot back to 9.x >>>> zpool import storage >>>> re-insert drive replacement drive. >>>> reboot >>> Gotta thank people for this again, saved me again this time on a >>> non-FreeBSD system this time (with a lot of using a modified >>> recoverdisk for OSX - thanks PSK@)... Lost 3 disks out of a raidz2 and >>> 2 more had read errors on some sectors.. don't know how much (if any) >>> data I've lost but at least it's not a rebuild from back up of all >>> 48TB.. >> >> What about the root-cause ? > > 3 disks died whilst the server was in transit from Malta to Australia > (and I'm surprised that was all considering the state of some of the > stuff that came out of the container - have a 3kva UPS that is completely > destroyed despite good packing.) >> Sounds like you had 5 disks dying at the same time ? > > Turns out that one of the 3 that had 'red lights on' had bad sectors, the > other 2 were just excluded by the BIOS... I did a byte copy onto new > drives found no read errors so put them back in and forced them online. > The other 1 had 78k of bytes unreadable so new disk went in and an > convinced the controller that it was the same disk as the one it > replaced, the export/import produced 2 more disks unrecoverable read > errors that nothing had flagged previously, so byte copied them onto new > drives and the import -fFX is currently working (5 hours so far)... > >> Do you periodically run long smart tests ? > > Yup (fully automated.) > >> Zpool scrubs ? > > Both servers took a zpool scrub before they were packed into the > containers... the second one came out unscathed... but then most stuff in > the second container came out unscathed unlike the first.... What a story ! Thanks for the details. So disks died because of the carrier, as I assume the second unscathed server was OK... Heads must have scratched the platters, but they should have been parked, so... Really strange. Hope you'll recover your whole pool. Ben From owner-freebsd-fs@freebsd.org Fri Feb 2 17:24:07 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1188EEE5253 for ; Fri, 2 Feb 2018 17:24:07 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [46.17.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6DCEF75D48; Fri, 2 Feb 2018 17:24:05 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.15.2/8.15.2) with ESMTP id w12HDB2F014059; Fri, 2 Feb 2018 17:13:11 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id w12HC1lW012698; Fri, 2 Feb 2018 17:12:01 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id w12HC1m8012695; Fri, 2 Feb 2018 17:12:01 GMT Date: Fri, 2 Feb 2018 17:12:01 GMT Message-Id: <201802021712.w12HC1m8012695@higson.cam.lispworks.com> From: Martin Simmons To: "Mikhail T." CC: se@freebsd.org, freebsd-fs@freebsd.org, brendan+freebsd@bbqsrc.net In-reply-to: <42ad9c4b-9017-0955-a550-521f9e2d933d@aldan.algebra.com> (mi+b@aldan.algebra.com) Subject: Re: fusefs and /etc/fstab References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> <42ad9c4b-9017-0955-a550-521f9e2d933d@aldan.algebra.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 17:24:07 -0000 >>>>> On Thu, 1 Feb 2018 14:35:26 -0500, Mikhail T said: > > For people trying to use fstab to mount fusefs filesystem(s), there is a > problem -- the daemons expecting one argument after the options (the > mount-point), are confused by there being two arguments: the "special" > and the mount-point. > > The mount_fusefs(8) recommends using "auto" for the "special" (first > field of the fstab), but that breaks too: > > fuse: bad mount point `auto': No such file or directory Yes, but mount doesn't run mount_fusefs when processing /etc/fstab. > I first thought, this problem is specific to smbnetfs, but the program > simply uses FUSE_ARGS_INIT(argc, argv) and otherwise relies on the > libfuse library to process the command-line. > > The trick I found to work is to put one of the mount options into the > first field: > > -oallow_other  /smb fusefs > rw,failok,uid=105,late,mountprog=/opt/bin/smbnetfs > > but that's just a hack, of course. > > Perhaps, our libfusefs ports can be modified to, upon encountering two > arguments remaining after the options, to either silently ignore the > first one at all times, or only ignore it, if it says "auto"? I think the problem is that /opt/bin/smbnetfs is a fuse daemon, not a FreeBSD mountprog. You need a mountprog that will run /opt/bin/smbnetfs with the correct arguments (c.f. mount.fuse on Linux). > Alternatively, maybe, mount_fusefs needs to strip the "special" off > before invoking the specified daemon? It does, but as noted above, it is not used when processing /etc/fstab. __Martin From owner-freebsd-fs@freebsd.org Fri Feb 2 17:50:27 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99210EE63FC for ; Fri, 2 Feb 2018 17:50:27 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (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 270F676B57 for ; Fri, 2 Feb 2018 17:50:27 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-io0-x22e.google.com with SMTP id f89so23761180ioj.4 for ; Fri, 02 Feb 2018 09:50:27 -0800 (PST) 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=OX3Kyvlg0vgF7BCBRiIea3jIIs2V8uth3h3/1L5SIrs=; b=O1GcSW3WFLROrHgNQEcjCaoYa5XXQgxv6XUABdeCCu30OykEk0e7jIzFdsFkq8hsOW UcT5W+fuHLNM8UsbMUsKzVl62zYLanduk9bSM4J1tKgIt7bMM+gTeo/XlGXHeQj70mKI ZKdB2CdNkopT8rkuDyBaq7+c3qA6/5uoi86NQprDQ75+BQMNep19I4cEfFCVXY6LdgMf Mk+AlsQCRFPwUSIxzGeg1U8hvdfV2AZ/di4uBmkAYGK0RTdHNyuOelklrUa+2ecZ0CdC PDLl8yuIUgPNfn/0wHqTjvNC/+inVrvSVy3Fksi2zETCoCnxx3NDzJhGEEyv1E2xIpyA ohAw== 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=OX3Kyvlg0vgF7BCBRiIea3jIIs2V8uth3h3/1L5SIrs=; b=Z1S7sjbE6Lbj9D3LqgGiBRZar2yvEKusbTD4o56x1tyFVvjFt72eZE8oKlXRi9tceM ZRREvpYOBINl3AaZzUiQTW1Qk92TCSdbMEKptO0j10HUL3SUtJGN+PKC6vq644hhqGvU k/r8JyaAKfpY1ZxchjwDoTy4fKEh3CbN4dNxjo0vQF3agfpAoZzSVgjnyH/qKveoo7eD A21NptQtxE1Lc0VXWv/v+Gl29RenNRT9O7R6277/HWcfbLCpTfxE5GzUaJYoixMrMaqp Eae2S2KbJwGV/SkjinCKexwJnoiywPRpcfseCHFUfaItYwy7bqiTWlTZya1JbfbTj6wV 9F7Q== X-Gm-Message-State: AKwxytcpj8H+JOBE5BuYFa4ng2t89ka90HsTVZZjbu3BbrlRaw6ozcA0 z/R+3irZkDnM9+DxBcHpkyvV0Csmo8yC9GeZSHnpXQ== X-Google-Smtp-Source: AH8x226sOX5ehDd0fTBZ0uZ4Zqh2C2gBssCLIk3Q6DVmdIdLJJv0xBVmKiF8VtDeEUHTqbFBGw5KF0C0AwZUo3v7d4s= X-Received: by 10.107.170.81 with SMTP id t78mr24887745ioe.98.1517593826298; Fri, 02 Feb 2018 09:50:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.156.70 with HTTP; Fri, 2 Feb 2018 09:50:25 -0800 (PST) In-Reply-To: <201802021712.w12HC1m8012695@higson.cam.lispworks.com> References: <8868a37f-90ad-a271-2295-bf67164fad19@aldan.algebra.com> <42ad9c4b-9017-0955-a550-521f9e2d933d@aldan.algebra.com> <201802021712.w12HC1m8012695@higson.cam.lispworks.com> From: Adam Vande More Date: Fri, 2 Feb 2018 11:50:25 -0600 Message-ID: Subject: Re: fusefs and /etc/fstab To: Martin Simmons Cc: "Mikhail T." , freebsd-fs , brendan+freebsd@bbqsrc.net Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 17:50:27 -0000 On Fri, Feb 2, 2018 at 11:12 AM, Martin Simmons wrote: > >>>>> On Thu, 1 Feb 2018 14:35:26 -0500, Mikhail T said: > > > > For people trying to use fstab to mount fusefs filesystem(s), there is a > > problem -- the daemons expecting one argument after the options (the > > mount-point), are confused by there being two arguments: the "special" > > and the mount-point. > > > > The mount_fusefs(8) recommends using "auto" for the "special" (first > > field of the fstab), but that breaks too: > > > > fuse: bad mount point `auto': No such file or directory > > Yes, but mount doesn't run mount_fusefs when processing /etc/fstab. > You can use mountprog option. -- Adam From owner-freebsd-fs@freebsd.org Fri Feb 2 20:49:02 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5DD3CEC9246 for ; Fri, 2 Feb 2018 20:49:02 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [72.12.213.40]) by mx1.freebsd.org (Postfix) with ESMTP id 06A457FA29 for ; Fri, 2 Feb 2018 20:49:01 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from isux.com (203-206-128-220.perm.iinet.net.au [203.206.128.220]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0P3J003GGJKZK500@hades.sorbs.net> for freebsd-fs@freebsd.org; Fri, 02 Feb 2018 12:58:13 -0800 (PST) Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... To: Ben RUBSON , "freebsd-fs@freebsd.org" References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> <54DCAC29.8000301@sorbs.net> <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> <8282375D-5DDC-4294-A69C-03E9450D9575@gmail.com> <73dd7026-534e-7212-a037-0cbf62a61acd@sorbs.net> From: Michelle Sullivan Message-id: <027070fb-f7b5-3862-3a52-c0f280ab46d1@sorbs.net> Date: Sat, 03 Feb 2018 07:48:58 +1100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48 In-reply-to: X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 20:49:02 -0000 Ben RUBSON wrote: > On 02 Feb 2018 11:51, Michelle Sullivan wrote: > >> Ben RUBSON wrote: >>> On 02 Feb 2018 11:26, Michelle Sullivan wrote: >>> >>> Hi Michelle, >>> >>>> Michelle Sullivan wrote: >>>>> Michelle Sullivan wrote: >>>>>> So far (few hours in) zfs import -fFX has not faulted with this >>>>>> image... >>>>>> it's running out of memory currently about 16G of 32G- however >>>>>> 9.2-P15 >>>>>> kernel died within minutes... out of memory (all 32G and swap) so am >>>>>> more optimistic at the moment... Fingers Crossed. >>>>> And the answer: >>>>> >>>>> 11-STABLE on a USB stick. >>>>> >>>>> Remove the drive that was replacing the hotspare (ie the replacement >>>>> drive for the one that initially died) >>>>> zpool import -fFX storage >>>>> zpool export storage >>>>> >>>>> reboot back to 9.x >>>>> zpool import storage >>>>> re-insert drive replacement drive. >>>>> reboot >>>> Gotta thank people for this again, saved me again this time on a >>>> non-FreeBSD system this time (with a lot of using a modified >>>> recoverdisk for OSX - thanks PSK@)... Lost 3 disks out of a raidz2 >>>> and 2 more had read errors on some sectors.. don't know how much >>>> (if any) data I've lost but at least it's not a rebuild from back >>>> up of all 48TB.. >>> >>> What about the root-cause ? >> >> 3 disks died whilst the server was in transit from Malta to Australia >> (and I'm surprised that was all considering the state of some of the >> stuff that came out of the container - have a 3kva UPS that is >> completely destroyed despite good packing.) >>> Sounds like you had 5 disks dying at the same time ? >> >> Turns out that one of the 3 that had 'red lights on' had bad sectors, >> the other 2 were just excluded by the BIOS... I did a byte copy onto >> new drives found no read errors so put them back in and forced them >> online. The other 1 had 78k of bytes unreadable so new disk went in >> and an convinced the controller that it was the same disk as the one >> it replaced, the export/import produced 2 more disks unrecoverable >> read errors that nothing had flagged previously, so byte copied them >> onto new drives and the import -fFX is currently working (5 hours so >> far)... >> >>> Do you periodically run long smart tests ? >> >> Yup (fully automated.) >> >>> Zpool scrubs ? >> >> Both servers took a zpool scrub before they were packed into the >> containers... the second one came out unscathed... but then most >> stuff in the second container came out unscathed unlike the first.... > > What a story ! Thanks for the details. > > So disks died because of the carrier, as I assume the second unscathed > server was OK... Pretty much. > Heads must have scratched the platters, but they should have been > parked, so... Really strange. > You'd have thought... though 2 of the drives look like it was wear and wear issues (the 2 not showing red lights) just not picked up on the periodic scrub.... Could be that the recovery showed that one up... you know - how you can have an array working fine, but one disk dies then others fail during the rebuild because of the extra workload. > Hope you'll recover your whole pool. So do I, it was my build server, everything important backed up with multiple redundancies except for the build VMs.. it'd take me about 4 weeks to rebuild it if I have to put it all back from backups and rebuild the build VMs.. but hey at least I can rebuild it unlike many with big servers. :P That said, the import -fFX is still running (and it is actually running) so it's still scanning/rebuilding the meta data. Michelle -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-fs@freebsd.org Fri Feb 2 22:34:13 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49FBDECFE0F for ; Fri, 2 Feb 2018 22:34:13 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (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 BE5BB84A73 for ; Fri, 2 Feb 2018 22:34:12 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x232.google.com with SMTP id 41so22573561wrc.9 for ; Fri, 02 Feb 2018 14:34:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=gMU4+OzDDLF+KypMzKKV3Cmy0yjHxnMZ16FgnXu6UjA=; b=YFZoyPIO6Y+o0uECV1gzT+npRlvVYGV1XNVJOtH9GX9zMUjg9BMbcC5zlolvDz3oIU Dku2h9CLeKshTfsVpkHICEgG+COK+ZVAei+XET19jtEIFToCMawFq0UtLGbqjg/u6Mo+ spRc8uPfwowHvCZ8uhf0eXmklIGV9+OVM/n9+UcR2NBx6U6/Zz+3zQTNSuXQxAet4EQe MOXjZiRO8dRNPMtzDlW7Ui51wYuWlyy1Aipbyuvl+iJaUh9a16r9CSVdIyK0pbKDluTe cwML5xy42GId1JJMBGAd2C6nnzi+mDwgJ0PeQDKPXhJ5AYs/P1qDIC4XcP46ii+xvITf Ha5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=gMU4+OzDDLF+KypMzKKV3Cmy0yjHxnMZ16FgnXu6UjA=; b=Q8o+KSLMow4p+Gr8FAsiJZ007zDyos6hSny2rWW/JOkN7xLuq09FGx4njPDe2Lq6E1 nyWgB3h+e5ww97DGZubJ2Mg76bGjHoBVrF5JUZ3RuFwponHFlC9A46GYCT+48LjuVtXM amVW+gJiNQ51VtZ7Xj9WHH3rU+4D8FE02wLhiOZ8/HDxbAvN5UquBcGCflW5ckUsNaI+ C2+JruZvVBm33yPAF5TjTwn4H5wbCQ0iNk9/lDhdWsxP6rRFF57C1xVeKLFVGieMaTrX oGm3Dn1hRS0fZSf34z7kvZfQgeeZjCqcFR1DklMR4TOk93979ec3kXkuNG0qCUUOjIYa 4b8w== X-Gm-Message-State: AKwxytdv8Zq0y4cpQ/i5WtHAerrcoUt4t+am6A0ovQ+9YgOC/lM3178D 6ckS2Hkx+iGP5Ji54eAKPqAfJomd X-Google-Smtp-Source: AH8x2275LZsvNlb//8ICEKvR8ibJlTBFPW+lpuigsScLuIN1WciKuzL2vO3SV9j1kVrv893zOWhRSQ== X-Received: by 10.223.164.23 with SMTP id d23mr19117424wra.72.1517610851278; Fri, 02 Feb 2018 14:34:11 -0800 (PST) Received: from bens-mac-1.home (LFbn-MAR-1-467-113.w2-15.abo.wanadoo.fr. [2.15.58.113]) by smtp.gmail.com with ESMTPSA id 81sm1529673wmi.26.2018.02.02.14.34.10 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 02 Feb 2018 14:34:10 -0800 (PST) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS pool faulted (corrupt metadata) but the disk data appears ok... From: Ben RUBSON In-Reply-To: <027070fb-f7b5-3862-3a52-c0f280ab46d1@sorbs.net> Date: Fri, 2 Feb 2018 23:34:10 +0100 Content-Transfer-Encoding: 7bit Message-Id: <42C31457-1A84-4CCA-BF14-357F1F3177DA@gmail.com> References: <54D3E9F6.20702@sorbs.net> <54D41608.50306@delphij.net> <54D41AAA.6070303@sorbs.net> <54D41C52.1020003@delphij.net> <54D424F0.9080301@sorbs.net> <54D47F94.9020404@freebsd.org> <54D4A552.7050502@sorbs.net> <54D4BB5A.30409@freebsd.org> <54D8B3D8.6000804@sorbs.net> <54D8CECE.60909@freebsd.org> <54D8D4A1.9090106@sorbs.net> <54D8D5DE.4040906@sentex.net> <54D8D92C.6030705@sorbs.net> <54D8E189.40201@sorbs.net> <54D924DD.4000205@sorbs.net> <54DCAC29.8000301@sorbs.net> <9c995251-45f1-cf27-c4c8-30a4bd0f163c@sorbs.net> <8282375D-5DDC-4294-A69C-03E9450D9575@gmail.com> <73dd7026-534e-7212-a037-0cbf62a61acd@sorbs.net> <027070fb-f7b5-3862-3a52-c0f280ab46d1@sorbs.net> To: "freebsd-fs@freebsd.org" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 22:34:13 -0000 On 02 Feb 2018 21:48, Michelle Sullivan wrote: > Ben RUBSON wrote: > >> So disks died because of the carrier, as I assume the second unscathed >> server was OK... > > Pretty much. > >> Heads must have scratched the platters, but they should have been >> parked, so... Really strange. > > You'd have thought... though 2 of the drives look like it was wear and > wear issues (the 2 not showing red lights) just not picked up on the > periodic scrub.... Could be that the recovery showed that one up... you > know - how you can have an array working fine, but one disk dies then > others fail during the rebuild because of the extra workload. Yes... To try to mitigate this, when I add a new vdev to a pool, I spread the new disks I have among the existing vdevs, and construct the new vdev with the remaining new disk(s) + other disks retrieved from the other vdevs. Thus, when possible, avoiding vdevs with all disks at the same runtime. However I only use mirrors, applying this with raid-Z could be a little bit more tricky... Ben