From owner-freebsd-fs@freebsd.org Sun Aug 6 12:20:41 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 57EF8DD6F61; Sun, 6 Aug 2017 12:20:41 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (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 DE2B884098; Sun, 6 Aug 2017 12:20:40 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x244.google.com with SMTP id y67so5910509wrb.3; Sun, 06 Aug 2017 05:20:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=/9vm2Ww536n0+zZlxkVqpDUc0DX3cJmtsFknpqQMaU0=; b=CQS6PLi68D/SSOXo39/G+Y7idPcfLvR7fkd9tHrnCNEDcdghsGTT5D38zdwgws6sZK PBy3zydR+4CxGaApsAY76Uv/cLMixXr3eZU503iSkAf3Y49HA+EE9fI8yehL8JgZElRp N/TdgX/7osh3pLylgowOulWnuivmlLjqxuZ/An043j2UNLPJ1iVfOrJW4uZchXWhT76I 1GBp+UEDPfXFLYMOJyZV/LpKC3k0ksXLi2h2HU2B5DC7+xjDNFNKb4eWWZ4at1qRyvmf Txi18hFhoIDhF7/HgOJrNpLHcYOK1iuvl3BxGjT0N4DxC6SsGy2tFrUlooD6XO22/ed1 CU3Q== 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:cc :content-transfer-encoding:message-id:references:to; bh=/9vm2Ww536n0+zZlxkVqpDUc0DX3cJmtsFknpqQMaU0=; b=QieCdY+YNlNlJIxWylO/bwcpDjr8K6NimmuoAQZ1FQCGOWRiV+zc/xEG2sIQujWg2k ltxnMRTfkJ7LEDJKIGFd7UOsZHWbExHcPtF1lRKVkMMQ6BiFQmv81BBH69V6dzX1DICp xBmDW5wD4GOdmKaiewqungq3ULsqguJr8MyDt07W3CmOeCoYLeZPxPlhRIdSvSJPFJ1f IA/QGicBC+l1bfRAwb5ZNdsEt94PvJW0bmFK6CIHfpa61++d93jFJCx9UiPsjlDVcV/v fpcElagmPn1qDl6J5QSWPI/i6ZWCwPVFgVipU0nTyKE8m+c/nAL02A0CUJ1G8/V1PIcg qsAw== X-Gm-Message-State: AIVw1112dZZyLMFtvQ5fHcR/A/LlG2R09wT2gkVNocbxoyZl/pV8nTk6 mERtzFakg86Dxs7RKuY= X-Received: by 10.223.139.219 with SMTP id w27mr5640921wra.146.1502022038470; Sun, 06 Aug 2017 05:20:38 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id h83sm6810095wmf.32.2017.08.06.05.20.37 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 06 Aug 2017 05:20:37 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> Date: Sun, 6 Aug 2017 14:20:36 +0200 Cc: freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> References: <87y3r0ankb.fsf@vostro.rath.org> <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Aug 2017 12:20:41 -0000 > On 03 Aug 2017, at 22:22, Julian Elischer wrote: >=20 > On 3/8/17 7:38 pm, Nikolaus Rath wrote: >> Hello, >>=20 >> I am the upstream maintainer of libfuse. I'd like to refresh / = improve >> the FreeBSD support in libfuse. My goal is for libfuse not to require >> any FreeBSD specific patches. >=20 > Hi, great to hear from you! > at $JOB we use libfuse and We have always worried that we don't really > have anyone in FreeBSD that really has fuse as a priority. Glad to hear from Nikolaus too, seeing that efforts are taken to keep libfuse FreeBSD compatible out of the box ! For sure this is great ! I also hugely use fuse, so having it to work correctly (at least = bug-free) is mandatory for me. > Rick Maclem has looked at it a little, as have a few people (see the = commit logs) > but generally as long as it more or less works, people tend to steer > clear of it. >=20 > For us libfuse "just worked" so we haven't touched it. > We had to touch the kernel part of fuse a little so remove some overly = restrictive > permission checks, and fix some issues to do with page boundaries = (from memory) > but nothing in the library. I've also reported a few bugs which were in kernel, and have been = corrected thanks to the great FreeBSD community. Fuse kernel support lacks some features, such as entry_timeout / = attr_timeout (reported), but it then concerns kernel, not libfuse. Thx ! Ben= From owner-freebsd-fs@freebsd.org Sun Aug 6 17:40:22 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C31D4DC0668 for ; Sun, 6 Aug 2017 17:40:22 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 95007680E0 for ; Sun, 6 Aug 2017 17:40:21 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BD91B20AC3 for ; Sun, 6 Aug 2017 13:40:20 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 06 Aug 2017 13:40:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=d1ZTRcZHKAQSR3lipfiql6CB8RVE2bH5QI/NZ13swHc=; b=E7wNqAME BryQgMRfKKgyiv6hYRJNlHzNWnctcJ7Tu7OrTPXvMcc4w5xah/5d30xItZJF5IOF g4yoW6RAQmFqE9pN/YSKSwjWO8HAv5BKd8ahFm29KS9MPN9N3GbGyg47v+kOVIQC lyalOJYlF2Zxykay0S5Fk+TZ9O4MxrpIZ3s8aclrE+73KD+4mlfN+j2uQ1oqsQro PE1FiKYoz2IHqgta35b2Fhnc+ovyfDuwvVXZNUlRixO45mieelLn6UURgHDNvHRS hZHyNABO44hSQ+9yPLiFiVf3z5VWuKrIfss1LAH8NX7G3KAXP8puhAyRTuDMUIwQ ZYTjvhIe/ZGFWQ== X-ME-Sender: X-Sasl-enc: K8P/5qgdYD5pOsYdj+w24qipjhIWmwzyIUu8VDlh7eAx 1502041220 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 7DA27245AD for ; Sun, 6 Aug 2017 13:40:20 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id A0146115 for ; Sun, 6 Aug 2017 17:40:19 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 539DD1029B0; Sun, 6 Aug 2017 19:40:18 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Sun, 06 Aug 2017 19:40:18 +0200 In-Reply-To: <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> (Ben RUBSON's message of "Sun, 6 Aug 2017 14:20:36 +0200") Message-ID: <87poc8tx19.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Aug 2017 17:40:22 -0000 On Aug 06 2017, Ben RUBSON wrote: >> On 03 Aug 2017, at 22:22, Julian Elischer wrote: >>=20 >> On 3/8/17 7:38 pm, Nikolaus Rath wrote: >>> Hello, >>>=20 >>> I am the upstream maintainer of libfuse. I'd like to refresh / improve >>> the FreeBSD support in libfuse. My goal is for libfuse not to require >>> any FreeBSD specific patches. >>=20 >> Hi, great to hear from you! >> at $JOB we use libfuse and We have always worried that we don't really >> have anyone in FreeBSD that really has fuse as a priority. > > Glad to hear from Nikolaus too, seeing that efforts are taken to keep > libfuse FreeBSD compatible out of the box ! For sure this is great ! > > I also hugely use fuse, so having it to work correctly (at least > bug-free) is mandatory for me. Would you mind testing the newest libfuse release then? Thanks, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Sun Aug 6 21:00:43 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 590C5DC926E for ; Sun, 6 Aug 2017 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4F58D6D613 for ; Sun, 6 Aug 2017 21:00:43 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v76L01a4085505 for ; Sun, 6 Aug 2017 21:00:43 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201708062100.v76L01a4085505@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 06 Aug 2017 21:00:43 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Aug 2017 21:00:43 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic New | 217062 | for file systems mounted with -o noexec, exec=off Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Aug 7 16:11:20 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91C21DB3283 for ; Mon, 7 Aug 2017 16:11:20 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay07.ispgateway.de (smtprelay07.ispgateway.de [134.119.228.101]) (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 5A353723B7 for ; Mon, 7 Aug 2017 16:11:20 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from [78.35.164.162] (helo=fabiankeil.de) by smtprelay07.ispgateway.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1dejfm-00078G-W2 for freebsd-fs@freebsd.org; Mon, 07 Aug 2017 17:10:27 +0200 Date: Mon, 7 Aug 2017 17:10:28 +0200 From: Fabian Keil To: Subject: [ZFS] Potential silent data corruption when receiving incremental stream with block size change on receiving side Message-ID: <20170807165118.72bde0a3@fabiankeil.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/lY=k_bwa_GISGVRQQ=iLx5/"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Aug 2017 16:11:20 -0000 --Sig_/lY=k_bwa_GISGVRQQ=iLx5/ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable The problem described in: https://github.com/zfsonlinux/zfs/issues/6224 is reproducible on FreeBSD-based systems. The reproducer script doesn't work as is, but a slightly modified version of it does: https://www.fabiankeil.de/tmp/reproduce-zfsonlinux-bug-6224.sh I've reproduced the problem on a system based on 11-STABLE r322045 but suspect that CURRENT is affected as well. While the Github issue is titled "Silent corruption in incremental send without -L flag with large block pool" I only became aware of the ZFSonLinux bug after discovering silent data loss after receiving an incremental stream that was sent with the -L flag: [fk@test-vm ~]$ hd /usr/test/src/sbin/camcontrol/camcontrol.c 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |..............= ..| * 0003ea10 [fk@test-vm ~]$ sudo zdb -ddddddd -bbbbbbb rpool/test/src $(stat -f '%i' /u= sr/test/src/sbin/camcontrol/camcontrol.c) Dataset rpool/test/src [ZPL], ID 550, cr_txg 67575, 704M, 78457 objects, ro= otbp DVA[0]=3D<0:254bfb000:1000> DVA[1]=3D<0:3803b7000:1000> [L0 DMU objset= ] sha256 uncompressed LE contiguous unique double size=3D800L/800P birth=3D= 67755L/67755P fill=3D78457 cksum=3Dfb0fd08b71ffb3f8:e14c2e477498cdc4:482244= 0c7db2cccc:9fa4961bce0031b6 Object lvl iblk dblk dsize lsize %full type 100844 2 128K 251K 0 251K 0.00 ZFS plain file (K=3Din= herit) (Z=3Dinherit) 168 bonus System attributes dnode flags: USED_BYTES USERUSED_ACCOUNTED=20 dnode maxblkid: 0 path /sbin/camcontrol/camcontrol.c uid 1001 gid 1001 atime Sat Jul 8 18:41:59 2017 mtime Sat Jul 8 18:41:59 2017 ctime Sat Jul 8 18:41:59 2017 crtime Sat Jul 8 18:41:59 2017 gen 609632 mode 100644 size 256529 parent 44643 links 1 pflags 40800000004 Indirect blocks: 0 L1 HOLE [L1 ZFS plain file] size=3D20000L birth=3D67755L segment [0000000000000000, 000000000003ec00) size 251K In case of my incremental /usr/src transfer the data corruption is only reproducible when not setting the -L flag so blindly omitting the flag is not a reliable workaround. While I hope that this is a recent regression I didn't have time to bisect it yet. Fabian --Sig_/lY=k_bwa_GISGVRQQ=iLx5/ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCWYiC5AAKCRAFiohV/3dU nY9tAKCGQ3JYx1sstSUneSH6PIKtOcWPVACfRUBa7ohw5IKyP7LkOgEWj6W121E= =o0Oy -----END PGP SIGNATURE----- --Sig_/lY=k_bwa_GISGVRQQ=iLx5/-- From owner-freebsd-fs@freebsd.org Tue Aug 8 07:23:37 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1D12DC7A7A; Tue, 8 Aug 2017 07:23:37 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C2A573506; Tue, 8 Aug 2017 07:23:36 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. (net206-94.perm.ertelecom.ru [46.146.206.94] (may be forged)) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v787NSZW037580 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 8 Aug 2017 12:23:29 +0500 (YEKT) (envelope-from emz@norma.perm.ru) Subject: Re: a strange and terrible saga of the cursed iSCSI ZFS SAN To: freebsd-fs@freebsd.org References: <1bd10b1e-0583-6f44-297e-3147f6daddc5@norma.perm.ru> Cc: freebsd-stable@FreeBSD.org From: "Eugene M. Zheganin" Message-ID: Date: Tue, 8 Aug 2017 12:23:28 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <1bd10b1e-0583-6f44-297e-3147f6daddc5@norma.perm.ru> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spamd-Result: default: False [1.50 / 25.00] BAYES_HAM(-3.00)[100.00%] RBL_SPAMHAUS_PBL(2.00)[94.206.146.46.zen.spamhaus.org : 127.0.0.10] HFILTER_HOSTNAME_UNKNOWN(2.50)[] DMARC_NA(0.00)[norma.perm.ru] MIME_GOOD(-0.10)[text/plain] R_DKIM_NA(0.00)[] R_SPF_SOFTFAIL(0.00)[~all] MID_RHS_MATCH_FROM(0.00)[] RECEIVED_SPAMHAUS(0.00)[94.206.146.46.zen.spamhaus.org] RCPT_COUNT_2(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] FROM_HAS_DN(0.00)[] TO_DN_NONE(0.00)[] FROM_EQ_ENVFROM(0.00)[] RCVD_COUNT_1(0.00)[] ONCE_RECEIVED(0.10)[] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 2.81 X-Rspamd-Queue-ID: v787NSZW037580 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 07:23:37 -0000 On 05.08.2017 22:08, Eugene M. Zheganin wrote: > Hi, > > > I got a problem that I cannot solve just by myself. I have a iSCSI zfs > SAN system that crashes, corrupting it's data. I'll be short, and try > to describe it's genesis shortly: > > 1) autumn 2016, SAN is set up, supermicro server, external JBOD, > sandisk ssds, several redundant pools, FreeBSD 11.x (probably release, > don't really remember - see below). > > 2) this is working just fine until early spring 2017 > > 3) system starts to crash (various panics): > > panic: general protection fault > panic: page fault > panic: Solaris(panic): zfs: allocating allocated > segment(offset=6599069589504 size=81920) > panic: page fault > panic: page fault > panic: Solaris(panic): zfs: allocating allocated > segment(offset=8245779054592 size=8192) > panic: page fault > panic: page fault > panic: page fault > panic: Solaris(panic): zfs: allocating allocated > segment(offset=1792100934656 size=46080) > > 4) we memtested it immidiately, no problems found. > > 5) we switch sandisks to toshibas, we switch also the server to an > identical one, JBOD to an identical one, leaving same cables. > > 6) crashes don't stop. > > 7) we found that field engineers physically damaged (sic!) the SATA > cables (main one and spare ones), and that 90% of the disks show ICRC > SMART errors. > > 8) we replaced the cable (brand new HP one). > > 9) ATA SMART errors stopped increasing. > > 10) crashes continue. > > 11) we decided that probably when ZFS was moved over damaged cables > between JBODs it was somehow damaged too, so now it's panicking > because of that. so we wiped the data completely, reinitialized the > SAN system and put it back into the production. we even dd'ed each > disk with zeroes (!) - just in case. Important note: the data was > imported using zfs send from another, stable system that is runing in > production in another DC. > > 12) today we got another panic. > > btw the pools look now like this: > > > # zpool status -v > pool: data > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://illumos.org/msg/ZFS-8000-8A > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > data ONLINE 0 0 62 > raidz1-0 ONLINE 0 0 0 > da2 ONLINE 0 0 0 > da3 ONLINE 0 0 0 > da4 ONLINE 0 0 0 > da5 ONLINE 0 0 0 > da6 ONLINE 0 0 0 > raidz1-1 ONLINE 0 0 0 > da7 ONLINE 0 0 0 > da8 ONLINE 0 0 0 > da9 ONLINE 0 0 0 > da10 ONLINE 0 0 0 > da11 ONLINE 0 0 0 > raidz1-2 ONLINE 0 0 62 > da12 ONLINE 0 0 0 > da13 ONLINE 0 0 0 > da14 ONLINE 0 0 0 > da15 ONLINE 0 0 0 > da16 ONLINE 0 0 0 > > errors: Permanent errors have been detected in the following files: > > data/userdata/worker208:<0x1> > > pool: userdata > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://illumos.org/msg/ZFS-8000-8A > scan: none requested > config: > > NAME STATE READ WRITE CKSUM > userdata ONLINE 0 0 216K > mirror-0 ONLINE 0 0 432K > gpt/userdata0 ONLINE 0 0 432K > gpt/userdata1 ONLINE 0 0 432K > > errors: Permanent errors have been detected in the following files: > > userdata/worker36:<0x1> > userdata/worker30:<0x1> > userdata/worker31:<0x1> > userdata/worker35:<0x1> > > 12) somewhere between p.5 and p.10 the pool became deduplicated (not > directly connected to the problem, just for production reasons). > > > So, concluding: we had bad hardware, we replaced EACH piece (server, > adapter, JBOD, cable, disks), and crashes just don't stop. We have 5 > another iSCSI SAN systems, almost fully identical that don't crash. > Crashes on this particular system began when it was running same set > of versions that stable systems. > > So far my priority version is that something was broken in the iSCSI+zfs stack somewhere between r310734 (most recent version on my SAN systems that works) and r320056 (probably earlier, but r320056 is the first revision with documented crash). So I downgraded back to r310734 (from a 11.1-RELEASE, which is affected, if I'm right). Some things speak pro this version: - the system was stable pre-spring 2017, before the upgrade happened - zfs corruption happens _only_ on the pools that the iSCSI is serving from, no corruption happens on the zfs pools that have nothing to do with providing zvils as iSCSI targets (and this seems to be the most convincing point). - the faulty hardware was changed. though it was changed to a identical hardware, BUT I have the very same set of identical hardware working in almost identical environment under r310734 in another DC. so far I'm not sure, because only 20 hours passed since the downgrade. However, if the system will be stable for more than a week (was never stable that long on recent revisions), it will prove I'm right and I'll file the PR. Thanks. Eugene. From owner-freebsd-fs@freebsd.org Tue Aug 8 07:26:19 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E510CDC7F86 for ; Tue, 8 Aug 2017 07:26:19 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 6E98F737EE for ; Tue, 8 Aug 2017 07:26:19 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x236.google.com with SMTP id f21so9454954wrf.5 for ; Tue, 08 Aug 2017 00:26:19 -0700 (PDT) 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=RCmFBKRoVkQp1W7lctS4uWCQsMhNlUjvOGhpWc8hL6Y=; b=iMKa5IieJNUmZJz1ZSuqryX7vmywhfklrz+dDERxJIDOZlhljpCCRFa6Zodlfyo5SP t+K5bnJ8fLWNtmapRfgdy3721wXD6x4icD8ueGlPGSKyDEr7Gr1Gdct5WUdCwTcunzOs J21X51p4KYD3u6cuX4LwtYqRVQtFA/V6uowS3Kus3rir0UBHuFHviGf1DRbp2sjZeY9t z8nUC4V9U7KIGMUU2lqHRMx4yJUlwBtM0Utna6XIMuUuT9njwLii+YC3tOiZst5YtmHZ 818t4YY0DZwb9yki/rl+JXzla89c2tOcEZJtFwWUoIEinJgd+XMbEHc12w+Mr1pd2tKt bZrA== 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=RCmFBKRoVkQp1W7lctS4uWCQsMhNlUjvOGhpWc8hL6Y=; b=b4vpA7T+nSWZK7NTJdK3H2fdnmxKyIiB6QwvAT/KsxsXhyJIXK1f3nQ08oaVtq8mCd xfHLRk2tmTCICuO+/LQ6VZ5SKm+DDe3PaqEsO1cYKsD69fv5qli64pIRBY+lX9CIadTo +O/FGnKOZ2DYga4zf0StmQVxwZ07BPnXl7gZGCVIGBHrLjSoizPGBVw89OcQPKoWCg1k PzQZYRk94rqxGsQLuFS2kL0GplnubYdo+Jsr+IsG8qDGj9FPslnQFQT79WO215Osynfs 34J0JRsHBbMZuk1F5Zh/w2y7Bh3YUsx3HfrkZeZSeV3c0L4G4GzuXN2YikSNsOkZJxIm RYdA== X-Gm-Message-State: AHYfb5jS81khD20OmSu4tuWx7oTd+EE8j0b2RbliyYEMynGbfF1pQJAT f3RueCwip7WTrbF1xCg= X-Received: by 10.223.135.214 with SMTP id c22mr2408303wrc.263.1502177177365; Tue, 08 Aug 2017 00:26:17 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id v41sm444850wrc.65.2017.08.08.00.26.16 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 08 Aug 2017 00:26:16 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87poc8tx19.fsf@vostro.rath.org> Date: Tue, 8 Aug 2017 09:26:15 +0200 Content-Transfer-Encoding: 7bit Message-Id: <91E457A2-2DE9-4EAB-B5B2-3EF304254DE2@gmail.com> References: <87y3r0ankb.fsf@vostro.rath.org> <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> <87poc8tx19.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 07:26:20 -0000 > On 06 Aug 2017, at 19:40, Nikolaus Rath wrote: > > On Aug 06 2017, Ben RUBSON wrote: >>> On 03 Aug 2017, at 22:22, Julian Elischer wrote: >>> >>> On 3/8/17 7:38 pm, Nikolaus Rath wrote: >>>> Hello, >>>> >>>> I am the upstream maintainer of libfuse. I'd like to refresh / improve >>>> the FreeBSD support in libfuse. My goal is for libfuse not to require >>>> any FreeBSD specific patches. >>> >>> Hi, great to hear from you! >>> at $JOB we use libfuse and We have always worried that we don't really >>> have anyone in FreeBSD that really has fuse as a priority. >> >> Glad to hear from Nikolaus too, seeing that efforts are taken to keep >> libfuse FreeBSD compatible out of the box ! For sure this is great ! >> >> I also hugely use fuse, so having it to work correctly (at least >> bug-free) is mandatory for me. > > Would you mind testing the newest libfuse release then? I just tested to compile it out of the box, it seems to fail : https://benrubson.github.io/fuse.log Note that we are still running 2.9(.5) version on FreeBSD : http://www.freshports.org/sysutils/fusefs-libs/ Ben From owner-freebsd-fs@freebsd.org Tue Aug 8 08:02:32 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BE50DCA0FC for ; Tue, 8 Aug 2017 08:02:32 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1BB4874DD6 for ; Tue, 8 Aug 2017 08:02:32 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by freefall.freebsd.org (Postfix, from userid 1235) id 626F213D1B; Tue, 8 Aug 2017 08:02:31 +0000 (UTC) Date: Tue, 8 Aug 2017 10:02:31 +0200 From: Baptiste Daroussin To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD Message-ID: <20170808080231.2chm2cz2qdcgvj2a@ivaldir.net> References: <87y3r0ankb.fsf@vostro.rath.org> <20170803115705.agsg6dm745dsriab@ivaldir.net> <87shh8ad5x.fsf@vostro.rath.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="a4kkuerbt3m2ggdn" Content-Disposition: inline In-Reply-To: <87shh8ad5x.fsf@vostro.rath.org> User-Agent: NeoMutt/20170609 (1.8.3) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 08:02:32 -0000 --a4kkuerbt3m2ggdn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 03, 2017 at 05:23:06PM +0200, Nikolaus Rath wrote: > On Aug 03 2017, Baptiste Daroussin wrote: > > On Thu, Aug 03, 2017 at 01:38:28PM +0200, Nikolaus Rath wrote: > >> Hello, > >>=20 > >> I am the upstream maintainer of libfuse. I'd like to refresh / improve > >> the FreeBSD support in libfuse. My goal is for libfuse not to require > >> any FreeBSD specific patches. > >>=20 > [...] > >> Personally, I don't use FreeBSD and I don't have an easy way to test on > >> FreeBSD either. So I would appreciate any input. > > > > I can help you testing if you need, do not hesitate to bother me :) >=20 > Thanks for the pull request! I've merged it and applied some extra > fixups on top that seemed right to me. It would be great if you could > give it a shot. >=20 > Code is at https://github.com/libfuse/libfuse, master branch. Note that the pull request was made testing with meson+ninja, I bet this is= the direction you are taking, (deprecating autotools?) I got one issue left to = build out of box, something is generating a target which calls cp with GNU cp only option, but I couldn't figure out what was doing it. Note that I can locally patch it to use gcp (GNU cp from coreutils) if needed. But knowing what is generating it would be better so I can maybe patch it to have a compatible usage of cp ? Best regards, Bapt --a4kkuerbt3m2ggdn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlmJcAgACgkQY4mL3PG3 PlrpuQ/+NLAcO7zfcow6ZF/GmvPBoTGPVw20DzhzCOdNIYagG4fwwvHxv4Gs0Nt8 tROvh6RQvbPTOpv6LfKusacnSJGNhfEqSko0MRIjGrA2sIcj/c9cHnuFrWS2lXwo hSa/YgLYhk9m0v/A2VZaYL32tXceEqj71O2ik+8XEfAW7De+OKVrMAWUH+6xQpOx 7Owr/igTjsZtLqVkML27L6mykZXSFTLJgkBZN7xTX5L0oF4kbRmTKOgCeqLit5UL OpiOdxcsiv2P8hxMwXhkHamSBKJ6BEmAK1NNgSpnbNsJTvZt9zyUrN/YlhW0LKet 5qdh7iHLLy+7q2WgjHlNR4JMe6R2Co6X8Fqn33alUD1dUQXNWgpayiUTVdKpGgan pgDGUWr9/t/TNqUMvionALmQUcQHhh7aSWZ5CfwCLs8EHPX9WRE77Yjzg+isy3QV EwL/ULMgTtriX6DkGicTy5TQ0mTRsiWn8VdVnmz/JGfRWy+CT3XzjVBaAzopUXTx KhfDHAWRLtbISeUMXZr2XwZyGiT2NugOfhkiyYePYhCmkLGPxrxCxEuKxdRtt9b0 D2b1uq73qSkIKtOI4H8YfPWYfmqvDFqokUTbKSK8YQdyezR1WJoR6sDl98Cb9zay yo6JrReJnFC0gwH2vDjnDugN7Yl45H5CegS0riycluTyAq8UcI8= =855R -----END PGP SIGNATURE----- --a4kkuerbt3m2ggdn-- From owner-freebsd-fs@freebsd.org Tue Aug 8 11:08:48 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3620DD4011 for ; Tue, 8 Aug 2017 11:08:48 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 760117FE26 for ; Tue, 8 Aug 2017 11:08:47 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3F56120A70 for ; Tue, 8 Aug 2017 07:08:46 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 08 Aug 2017 07:08:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=LdeiXde4TBS1RZWByDsBe9uRSGRZctxi/lsr4FKdqhg=; b=NK70MDfd U1zAOLo+EoQ+fZCxD1XpSY5Mj7mm3m8GG3TlJfiVhZYV/QqMVi7r6RNfFaFAuA/N 18DdQUHH7g/FFM0kUuqumhtFVG0tcW7EqdwYkB1sexj6QFwUr16h2sNTaHb51Ofc I+vL7PMnoTzJ+aRdIhtQTEv7u1Zc+0m7IWNFpAIyv1+jLmUHIUxWnekVfqML2KV5 aUubp0JnN40SrENTtVGnnSbttCIfCdOCOLFZ9zOZ2TatsYgDYGYnKF/kMVyOWjbl f1ndqxv+PXEYjMPFZndQKb/q6V8Tz6q0mIk0/yIGug7jAIBgwBJhOTkXOtKDfNIR 3WU9ZyrL+OQlNA== X-ME-Sender: X-Sasl-enc: uCTgrLYYZhLimr5U2+3uXl5wFUjj8+YmBCBUPUSLqBkU 1502190525 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id ECAA57E4EA for ; Tue, 8 Aug 2017 07:08:45 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id B57E03E79 for ; Tue, 8 Aug 2017 11:08:44 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 10863102B9A; Tue, 8 Aug 2017 13:08:43 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <20170803115705.agsg6dm745dsriab@ivaldir.net> <87shh8ad5x.fsf@vostro.rath.org> <20170808080231.2chm2cz2qdcgvj2a@ivaldir.net> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Tue, 08 Aug 2017 13:08:43 +0200 In-Reply-To: <20170808080231.2chm2cz2qdcgvj2a@ivaldir.net> (Baptiste Daroussin's message of "Tue, 8 Aug 2017 10:02:31 +0200") Message-ID: <87valywc3o.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 11:08:48 -0000 On Aug 08 2017, Baptiste Daroussin wrote: > On Thu, Aug 03, 2017 at 05:23:06PM +0200, Nikolaus Rath wrote: >> On Aug 03 2017, Baptiste Daroussin wrote: >> > On Thu, Aug 03, 2017 at 01:38:28PM +0200, Nikolaus Rath wrote: >> >> Hello, >> >>=20 >> >> I am the upstream maintainer of libfuse. I'd like to refresh / improve >> >> the FreeBSD support in libfuse. My goal is for libfuse not to require >> >> any FreeBSD specific patches. >> >>=20 >> [...] >> >> Personally, I don't use FreeBSD and I don't have an easy way to test = on >> >> FreeBSD either. So I would appreciate any input. >> > >> > I can help you testing if you need, do not hesitate to bother me :) >>=20 >> Thanks for the pull request! I've merged it and applied some extra >> fixups on top that seemed right to me. It would be great if you could >> give it a shot. >>=20 >> Code is at https://github.com/libfuse/libfuse, master branch. > > Note that the pull request was made testing with meson+ninja, I bet this = is the > direction you are taking, (deprecating autotools?) Yes. > I got one issue left to build > out of box, something is generating a target which calls cp with GNU cp o= nly > option, but I couldn't figure out what was doing it. Note that I can loca= lly > patch it to use gcp (GNU cp from coreutils) if needed. > > But knowing what is generating it would be better so I can maybe patch it= to > have a compatible usage of cp ? Well, what option is it? I think the only usage of cp is for "building" the tests (which just involves copying the Python scripts). Currently this uses -fPu. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Tue Aug 8 11:11:59 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9E5F2DD438D for ; Tue, 8 Aug 2017 11:11:59 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 705B580227 for ; Tue, 8 Aug 2017 11:11:59 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C1EFA20AC1 for ; Tue, 8 Aug 2017 07:11:57 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 08 Aug 2017 07:11:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=cXPT9LAAssaOWuLn0MmEd4YPwCzwsJkbOysFZBDYq3A=; b=RVc/9n1C NkoyG7nO65K4ODML/Iu4C+qhAzt6Z13CEH5jPa6xo4PxRtmhlwzou6v9jFoh2otX xcUwD2HpQiYwUzR2vVsGH/q7nKwigCg0mTH3X/fj060OChTLW9Hs+hp7Jbzekg+E BU7xgMAZKI4O5Ma44UEPCFM6rlgIq7+FoU2OZi1RprSoHiXnCHq7nqtGO0Qy8DKu QW5HPzrTkAeNq+zj7r9+01D2oUGFezZgzmjIDcFACyjsTUJe3QzmOA+jCMfypify Pg1m2BKbHcpKds0cFSz/OYC7YN52mK/xpd6JQ2aOwk53dV9iR9w7seEZvBySULv2 Nwubj2BHErbbaw== X-ME-Sender: X-Sasl-enc: 495StVhEuQ+JlTrLYnITwYlihX2mq8XEQyDbpQr5GS1Z 1502190717 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 7DDF2240AF for ; Tue, 8 Aug 2017 07:11:57 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 9EBACD5 for ; Tue, 8 Aug 2017 11:11:56 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id EC105102B9A; Tue, 8 Aug 2017 13:11:54 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> <87poc8tx19.fsf@vostro.rath.org> <91E457A2-2DE9-4EAB-B5B2-3EF304254DE2@gmail.com> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Tue, 08 Aug 2017 13:11:54 +0200 In-Reply-To: <91E457A2-2DE9-4EAB-B5B2-3EF304254DE2@gmail.com> (Ben RUBSON's message of "Tue, 8 Aug 2017 09:26:15 +0200") Message-ID: <87shh2wbyd.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 11:11:59 -0000 On Aug 08 2017, Ben RUBSON wrote: >> On 06 Aug 2017, at 19:40, Nikolaus Rath wrote: >>=20 >> On Aug 06 2017, Ben RUBSON wrote: >>>> On 03 Aug 2017, at 22:22, Julian Elischer wrote: >>>>=20 >>>> On 3/8/17 7:38 pm, Nikolaus Rath wrote: >>>>> Hello, >>>>>=20 >>>>> I am the upstream maintainer of libfuse. I'd like to refresh / improve >>>>> the FreeBSD support in libfuse. My goal is for libfuse not to require >>>>> any FreeBSD specific patches. >>>>=20 >>>> Hi, great to hear from you! >>>> at $JOB we use libfuse and We have always worried that we don't really >>>> have anyone in FreeBSD that really has fuse as a priority. >>>=20 >>> Glad to hear from Nikolaus too, seeing that efforts are taken to keep >>> libfuse FreeBSD compatible out of the box ! For sure this is great ! >>>=20 >>> I also hugely use fuse, so having it to work correctly (at least >>> bug-free) is mandatory for me. >>=20 >> Would you mind testing the newest libfuse release then? > > I just tested to compile it out of the box, it seems to fail : > https://benrubson.github.io/fuse.log So what fails is just one of the examples, that's good news. Worst case we can disable it. Can I browse the FreeBSD manpages for fstatat() and openat() somewhere? Maybe there are equivalent flags that I could use. > > Note that we are still running 2.9(.5) version on FreeBSD : > http://www.freshports.org/sysutils/fusefs-libs/ Yeah. I hope I can help you to provide libfuse3 as well. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Tue Aug 8 11:19:35 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D228DD4A7D for ; Tue, 8 Aug 2017 11:19:35 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::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 93E4080B71 for ; Tue, 8 Aug 2017 11:19:34 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x22c.google.com with SMTP id f21so11631904wrf.5 for ; Tue, 08 Aug 2017 04:19:34 -0700 (PDT) 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=eqOMt1Zxh9v3/Zo1FslGKxstG+RFd2geiebBRkuboGA=; b=A239nuUg9Mh0jvizEmD5vHzHQZ6nP5eaL3NmUsunBJYjThvcBHzbhZtRXpwkH6bEem t8QLSAcx9lMFUm/jEtgJeu7LMo7ncpr0TZzZEhapjEwCfsUsteX1gwaMMNO4/ZmDkQD/ 3sd6h5DNlSG4hcu4y50xnibmOIYUVAYcam16T/3HS1PcxLDk30WfhsbLo6aQ7wxpGsVI I3X5nRr1cTVxUM2vBHXGKtC2gBIDFI7gqNsoCMvpIbs4I8NBO+qp39/ReDPySl7oG2c4 X3/W0f3S+zsJ1i1oSlHaTwNBSB6uCSxo7K8cNQET9//7LMF9Dro1BhkGGBpCLd02fVoN NHlQ== 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=eqOMt1Zxh9v3/Zo1FslGKxstG+RFd2geiebBRkuboGA=; b=lzG7zq2n2/R90NGmoGjqMoFYxjfIpUpc0M0JBrgB6FWpDvRFpiYHHA7eghFscK5x2i 8g/+pVTTNv1sMbarJXpwTtUCqgadBp+67/do35dM7kjAUxZcLimd08CEMz3rKU2T1bYi LaLnae8CE8HBavXUPhFBqi1P48hv2j5umHPA9yLxrbVkHpQ3dbigAoHWHXKDUHU+Rr+l 4T7/NudRni7MrZOzwQH1lB4wnE7lfzU1ZoK608eJoPtF8yBwlkyEOUF8ZTW2h2mRgELS iFcq21jG6futQ1nMf3zUOFkKHPgOWDZBjpa7HWi2CK98q5i/hRZeJt2LSX5YmNWj5vxh YUgA== X-Gm-Message-State: AHYfb5i4zaRC7+VRbHn1mCqCS1wh3iKdVdb67tyl76FFqbBr0c2bQH4/ 8pp27ZjBBqeMHNYGB/I= X-Received: by 10.223.147.97 with SMTP id 88mr2705479wro.226.1502191172753; Tue, 08 Aug 2017 04:19:32 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id n184sm1246209wme.33.2017.08.08.04.19.31 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 08 Aug 2017 04:19:32 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87shh2wbyd.fsf@vostro.rath.org> Date: Tue, 8 Aug 2017 13:19:30 +0200 Content-Transfer-Encoding: 7bit Message-Id: <1DB955A4-FAB1-408B-8BCA-7CB88C156111@gmail.com> References: <87y3r0ankb.fsf@vostro.rath.org> <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> <87poc8tx19.fsf@vostro.rath.org> <91E457A2-2DE9-4EAB-B5B2-3EF304254DE2@gmail.com> <87shh2wbyd.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 11:19:35 -0000 > On 08 Aug 2017, at 13:11, Nikolaus Rath wrote: > > On Aug 08 2017, Ben RUBSON wrote: >>> On 06 Aug 2017, at 19:40, Nikolaus Rath wrote: >>> >>> On Aug 06 2017, Ben RUBSON wrote: >>>>> On 03 Aug 2017, at 22:22, Julian Elischer wrote: >>>>> >>>>> On 3/8/17 7:38 pm, Nikolaus Rath wrote: >>>>>> Hello, >>>>>> >>>>>> I am the upstream maintainer of libfuse. I'd like to refresh / improve >>>>>> the FreeBSD support in libfuse. My goal is for libfuse not to require >>>>>> any FreeBSD specific patches. >>>>> >>>>> Hi, great to hear from you! >>>>> at $JOB we use libfuse and We have always worried that we don't really >>>>> have anyone in FreeBSD that really has fuse as a priority. >>>> >>>> Glad to hear from Nikolaus too, seeing that efforts are taken to keep >>>> libfuse FreeBSD compatible out of the box ! For sure this is great ! >>>> >>>> I also hugely use fuse, so having it to work correctly (at least >>>> bug-free) is mandatory for me. >>> >>> Would you mind testing the newest libfuse release then? >> >> I just tested to compile it out of the box, it seems to fail : >> https://benrubson.github.io/fuse.log > > So what fails is just one of the examples, that's good news. Worst case > we can disable it. Can I browse the FreeBSD manpages for fstatat() and > openat() somewhere? Maybe there are equivalent flags that I could use. I just dumped them : https://benrubson.github.io/openat.txt https://benrubson.github.io/fstatat.txt Ben From owner-freebsd-fs@freebsd.org Tue Aug 8 12:17:12 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D797DD8CC6 for ; Tue, 8 Aug 2017 12:17:12 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout09.t-online.de (mailout09.t-online.de [194.25.134.84]) (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 624A3635 for ; Tue, 8 Aug 2017 12:17:12 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd17.aul.t-online.de (fwd17.aul.t-online.de [172.20.27.64]) by mailout09.t-online.de (Postfix) with SMTP id 6F7884249257 for ; Tue, 8 Aug 2017 14:17:04 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (XND7pYZJrhb6hN0fWJvLF7TTU0wnO7a78ukX+Cw64LkWcorDeL7ie35FCDCKGApZKB@[84.154.116.31]) by fwd17.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1df3RY-2Rmzo00; Tue, 8 Aug 2017 14:17:04 +0200 Subject: Re: State of FUSE on FreeBSD To: freebsd-fs@freebsd.org References: <87y3r0ankb.fsf@vostro.rath.org> <39c45819-2754-ed73-a0e7-681969f58de7@freebsd.org> <5C15DFF5-661E-47ED-B84B-6BE477A2DE5C@gmail.com> <87poc8tx19.fsf@vostro.rath.org> <91E457A2-2DE9-4EAB-B5B2-3EF304254DE2@gmail.com> <87shh2wbyd.fsf@vostro.rath.org> From: Stefan Esser Message-ID: <877f208a-d6ec-2236-b2e8-f86c9b1b87df@freebsd.org> Date: Tue, 8 Aug 2017 14:17:02 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <87shh2wbyd.fsf@vostro.rath.org> Content-Type: text/plain; charset=windows-1252 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-ID: XND7pYZJrhb6hN0fWJvLF7TTU0wnO7a78ukX+Cw64LkWcorDeL7ie35FCDCKGApZKB X-TOI-MSGID: f4b73826-1d0a-4da6-8eb8-10a653c49b02 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 12:17:12 -0000 Am 08.08.17 um 13:11 schrieb Nikolaus Rath: > So what fails is just one of the examples, that's good news. Worst case > we can disable it. Can I browse the FreeBSD manpages for fstatat() and > openat() somewhere? Maybe there are equivalent flags that I could use. https://www.freebsd.org/cgi/man.cgi?query=fstatat https://www.freebsd.org/cgi/man.cgi?query=openat Regards, STefan From owner-freebsd-fs@freebsd.org Tue Aug 8 22:03:55 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3A6DDD341C for ; Tue, 8 Aug 2017 22:03:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E098F75909 for ; Tue, 8 Aug 2017 22:03:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v78M3tYO001732 for ; Tue, 8 Aug 2017 22:03:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219457] ZFS ARC eviction & system hangup Date: Tue, 08 Aug 2017 22:03:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vsasjason@gmail.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: version Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 22:03:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219457 Anton Sayetsky changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.3-RELEASE |11.1-RELEASE --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Aug 8 22:07:12 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9768DD371B for ; Tue, 8 Aug 2017 22:07:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A825275BC8 for ; Tue, 8 Aug 2017 22:07:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v78M7Cte007209 for ; Tue, 8 Aug 2017 22:07:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219457] ZFS ARC eviction & system hangup Date: Tue, 08 Aug 2017 22:07:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: vsasjason@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org 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: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Aug 2017 22:07:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219457 Anton Sayetsky changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Overcome By Events --- Comment #16 from Anton Sayetsky --- Looks like I can't reproduce this anymore after updating to releng/11.1 I still can observe a problem with ARC eviction to minimum size, but system= at least doesn't hang now. So its time to try again patches from #187594 & D7538. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 10 15:15:24 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CEE3DD550B for ; Thu, 10 Aug 2017 15:15:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A958641AF for ; Thu, 10 Aug 2017 15:15:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7AFFO5H065560 for ; Thu, 10 Aug 2017 15:15:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221077] Boot from ZFS fails following freebsd-update Date: Thu, 10 Aug 2017 15:15:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: allanjude@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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 15:15:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 --- Comment #6 from Allan Jude --- It is not clear, are you booting from ZFS or UFS? It looks like your / is on UFS, and you should not have installed gptzfsboo= t, but gptboot --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 10 15:29:01 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68FDADD5A8C for ; Thu, 10 Aug 2017 15:29:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 57E9664DA3 for ; Thu, 10 Aug 2017 15:29:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7AFT0TV098726 for ; Thu, 10 Aug 2017 15:29:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221077] Boot from ZFS fails following freebsd-update Date: Thu, 10 Aug 2017 15:29:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bacon4000@gmail.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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Aug 2017 15:29:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 --- Comment #7 from Jason Bacon --- The problem occurred when booting from ZFS. Since I had to get this system back online and reliable ASAP, I backed it up and reinstalled with a UFS boot partition. I had a similar issue twice on another system booting from ZFS a couple yea= rs ago, but it was easily worked around by recreating the contents of /boot. = That little hack didn't work this time. As I mentioned, I will continue to boot from ZFS on some of my development systems and "hope" the problem returns so we can properly diagnose it. I'll add that the problem seems to occur after particularly heavy writes to= the pool, if 3 times qualifies as a pattern. In this case, I had just installed a few hundred ports from source. In the previous case, I had done an rsync backup to the system from another server I was upgrading. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 11 05:38:56 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77E9ADC2D30 for ; Fri, 11 Aug 2017 05:38:56 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254:10::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 37B701CF4 for ; Fri, 11 Aug 2017 05:38:56 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]) (authenticated bits=0) by hydra.pix.net (8.16.0.19/8.15.2) with ESMTPSA id v7B5cld8035087 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Fri, 11 Aug 2017 01:38:54 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Received: from magrathea.distal.com (magrathea.distal.com [IPv6:2001:470:e24c:200:ea06:88ff:feca:960e]) (authenticated bits=0) by mail.distal.com (8.15.2/8.15.2) with ESMTPSA id v7B5ci1k078228 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Aug 2017 01:38:45 -0400 (EDT) (envelope-from cross+freebsd@distal.com) From: Chris Ross Content-Type: multipart/signed; boundary="Apple-Mail=_1D3F2DAA-63D3-44F2-A91F-0614A480169E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Subject: ZFS: Device names in a raidz1 pool after changing controllers Date: Fri, 11 Aug 2017 01:38:43 -0400 Message-Id: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com> To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]); Fri, 11 Aug 2017 01:38:45 -0400 (EDT) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 05:38:56 -0000 --Apple-Mail=_1D3F2DAA-63D3-44F2-A91F-0614A480169E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I=E2=80=99m moving one of my systems from the on-board SATA controller = to a SATA/SAS controller. A side effect of the first experiement, of = moving half of the SATA drives onto the new controller, is that they = went from being named =E2=80=9Cada2=E2=80=9D and =E2=80=9Cada3=E2=80=9D = to being =E2=80=9Cda0=E2=80=9D and =E2=80=9Cda1=E2=80=9D. ZFS, happily, just coped with this. But, the raidz1 pool that was = spread across parts of disks on both sides, now looks like: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1p4 ONLINE 0 0 0 diskid/DISK-WOL240261932p1 ONLINE 0 0 0 diskid/DISK-WOL240261922p1 ONLINE 0 0 0 (where before, the second and third components were ada2p1 and ada3p1). 1) Is it possible to rename how zpool lists these disk identifiers? 2) If so, is there consensus on whether device names or diskid are = =E2=80=9Cbetter=E2=80=9D, perhaps simply =E2=80=9Cmore recommended"? In = a way, I=E2=80=99d like an idea how to tell which disk in the enclosure = is which device in the pool, which I think diskid would make harder=E2=80=A6= Thanks. - Chris --Apple-Mail=_1D3F2DAA-63D3-44F2-A91F-0614A480169E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJZjULkAAoJEPFBDnXvoNg0JhIP/jkoj5C+Ro+kHEs3xZ0HFrsy xrCYgft/uk69jlWNDEF+bhG99sb6OIPrvu2ltVaYlVNX3j7PyyBY8O0u/Og32mx3 wxhJvp7ALrNY6ioKdQjtbIrgjF+6JHZt2vIGoLJDG6DQ/C/G6OGP9c6zrJ0QKG3D p7nZ7X3yR47Dty9RDf2Xrr6UKlDlRsr0AdY5JVBppv3QtsdyqYQql7X3LgD52x2D n9lXbUwJXNN11vGtcgHfbI9tY8uU5wzMNdxyDThEs6+Y3+5rMk5MvYm9XHdP7l55 8nbmvhroBa8IJjZlhxrpb9K6Oj0swqXXxKzvczZ307HDjIuwVrYAmhL6rv7uJonV a3LC4UyZUTqYvUYp/I1bFQgI140Wa18VZYjHVCQylUvqKOYZyqiLsfywHitZJ2RV lRxziU/zRNvVHUy5TlSwPrhzXldhKTzS8JRN5HAb07YhhOwRkm6ZWbQVtNkfrhSp 4FNxBP55I97VTOjaQ5moaM5RkkyR3oXpegte1fm9WhyVkV5mMRo7Wl990kLuWQl0 6FAYh4YLPncN65baZRibNue3Fw/G3Q93Bj1grpjBP30l3jNnGp9u+/nZCEmbsvzF er7F4WYEEVUQ72XV6NyxVW5KoVjVzvU/KYPk/IAgyl2cMToOz/wf0og+jyY4JRYP X6HhzzFKnmd1bM/8O5jH =QezY -----END PGP SIGNATURE----- --Apple-Mail=_1D3F2DAA-63D3-44F2-A91F-0614A480169E-- From owner-freebsd-fs@freebsd.org Fri Aug 11 06:28:30 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 607A9DC563C; Fri, 11 Aug 2017 06:28:30 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru [IPv6:2a00:7540:1::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.norma.perm.ru", Issuer "Vivat-Trade UNIX Root CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BB5953538; Fri, 11 Aug 2017 06:28:29 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from bsdrookie.norma.com. (net206-94.perm.ertelecom.ru [46.146.206.94] (may be forged)) by elf.hq.norma.perm.ru (8.15.2/8.15.2) with ESMTPS id v7B6SMEH008220 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 11 Aug 2017 11:28:23 +0500 (YEKT) (envelope-from emz@norma.perm.ru) To: freebsd-fs@freebsd.org Cc: freebsd-stable From: "Eugene M. Zheganin" Subject: zfs listing and CPU Message-ID: Date: Fri, 11 Aug 2017 11:28:21 +0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spamd-Result: default: False [1.50 / 25.00] RBL_SPAMHAUS_PBL(2.00)[94.206.146.46.zen.spamhaus.org : 127.0.0.10] HFILTER_HOSTNAME_UNKNOWN(2.50)[] BAYES_HAM(-3.00)[99.99%] DMARC_NA(0.00)[norma.perm.ru] MIME_GOOD(-0.10)[text/plain] R_DKIM_NA(0.00)[] R_SPF_SOFTFAIL(0.00)[~all] MID_RHS_MATCH_FROM(0.00)[] RECEIVED_SPAMHAUS(0.00)[94.206.146.46.zen.spamhaus.org] TO_DN_SOME(0.00)[] RCPT_COUNT_2(0.00)[] TO_MATCH_ENVRCPT_ALL(0.00)[] FROM_HAS_DN(0.00)[] FROM_EQ_ENVFROM(0.00)[] RCVD_COUNT_1(0.00)[] ONCE_RECEIVED(0.10)[] X-Rspamd-Server: localhost X-Rspamd-Scan-Time: 0.93 X-Rspamd-Queue-ID: v7B6SMEH008220 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 06:28:30 -0000 Hi, Why does the zfs listing eat so much of the CPU ? last pid: 47151; load averages: 3.97, 6.35, 6.13 up 1+23:21:18 09:15:13 146 processes: 3 running, 142 sleeping, 1 waiting CPU: 0.0% user, 0.0% nice, 30.5% system, 0.3% interrupt, 69.2% idle Mem: 44M Active, 360M Inact, 37G Wired, 25G Free ARC: 32G Total, 14G MFU, 17G MRU, 312M Anon, 803M Header, 523M Other Swap: 32G Total, 185M Used, 32G Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 11 root 32 155 ki31 0K 512K CPU0 0 1104.1 2666.23% idle 0 root 9880 -16 - 0K 154M swapin 11 314.0H 281.29% kernel 13 root 3 -8 - 0K 48K gread 0 20.9H 28.71% geom 47114 root 1 20 0 40432K 3840K db->db 4 0:05 26.84% zfs 47099 root 1 20 0 40432K 3840K zio->i 17 0:05 26.83% zfs 47106 root 1 20 0 40432K 3840K db->db 21 0:05 26.81% zfs 47150 root 1 20 0 40432K 3428K db->db 13 0:03 26.31% zfs 47141 root 1 20 0 40432K 3428K zio->i 28 0:03 26.31% zfs 47135 root 1 20 0 40432K 3312K g_wait 9 0:03 25.51% zfs 4 root 7 -16 - 0K 112K - 20 975:01 19.73% cam 5 root 2494 -8 - 0K 39952K arc_re 18 20.2H 18.58% zfskern 12 root 65 -60 - 0K 1040K WAIT 0 17.8H 15.64% intr 22 root 2 -16 - 0K 32K psleep 3 66:34 7.31% pagedaemon 590 root 10 -16 - 0K 160K - 21 177:02 2.96% ctl [...] This is from winter 2017 11-STABLE (r310734), one of the 'zfs'es is cloning, and all the others are 'zfs list -t all'. I have like 25 gigs of free RAM, do I have any chance of speeding this up using may be some caching or some sysctl tuning ? We are using a simple ZFS web API that may issue concurrent or sequential listing requests, so as you can see they sometimes do stack. Thanks. Eugene. From owner-freebsd-fs@freebsd.org Fri Aug 11 06:40:05 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6793DC631D for ; Fri, 11 Aug 2017 06:40:05 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (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 AD8CC3C85 for ; Fri, 11 Aug 2017 06:40:04 +0000 (UTC) (envelope-from satan@ukr.net) Received: from satan by hell.ukr.net with local ID 1dg3NT-0007vH-KE ; Fri, 11 Aug 2017 09:24:59 +0300 Date: Fri, 11 Aug 2017 09:24:59 +0300 From: Vitalij Satanivskij To: Chris Ross Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Device names in a raidz1 pool after changing controllers Message-ID: <20170811062459.GA30374@hell.ukr.net> References: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 06:40:06 -0000 Hello for disabling diskid kern.geom.label.disk_ident.enable="0" same for gptid kern.geom.label.gptid.enable="0" same for gpt label kern.geom.label.gpt.enable="0" In /boot/loader.conf Just choose how you prefer And if tank isn't boot pool you can export and import with -d option to choose which naming of devices to use (eg /dev/gpt /dev/diskid etc) Chris Ross wrote: CR> CR> I’m moving one of my systems from the on-board SATA controller to a SATA/SAS controller. A side effect of the first experiement, of moving half of the SATA drives onto the new controller, is that they went from being named “ada2” and “ada3” to being “da0” and “da1”. CR> CR> ZFS, happily, just coped with this. But, the raidz1 pool that was spread across parts of disks on both sides, now looks like: CR> CR> NAME STATE READ WRITE CKSUM CR> tank ONLINE 0 0 0 CR> raidz1-0 ONLINE 0 0 0 CR> ada1p4 ONLINE 0 0 0 CR> diskid/DISK-WOL240261932p1 ONLINE 0 0 0 CR> diskid/DISK-WOL240261922p1 ONLINE 0 0 0 CR> CR> (where before, the second and third components were ada2p1 and ada3p1). CR> CR> 1) Is it possible to rename how zpool lists these disk identifiers? CR> 2) If so, is there consensus on whether device names or diskid are “better”, perhaps simply “more recommended"? In a way, I’d like an idea how to tell which disk in the enclosure is which device in the pool, which I think diskid would make harder… CR> CR> Thanks. CR> CR> - Chris CR> From owner-freebsd-fs@freebsd.org Fri Aug 11 08:09:29 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DB76DCA12B for ; Fri, 11 Aug 2017 08:09:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1B37665E3B for ; Fri, 11 Aug 2017 08:09:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7B89SLs039157 for ; Fri, 11 Aug 2017 08:09:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219760] ZFS iSCSI w/ Win10 Initiator Causes pool corruption Date: Fri, 11 Aug 2017 08:09:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emz@norma.perm.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: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 08:09:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219760 emz@norma.perm.ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emz@norma.perm.ru --- Comment #6 from emz@norma.perm.ru --- I observed similar behaviour on one of my SAN systems. In my opinion, iSCSI + zfs is broken somewhere between r310734 and r320056. Symptoms: - random fatal trap 12 panics. - random general protection faults panics - random "Solaris(panic): zfs: allocating allocated segment" panics - zfs pool corruption that happens ONLY on pools that serve the zvols as iS= CSI target devices - zfs pool corruption happening _on the fly_, without system panicking. - no zfs corruption is happening of the zfs pools not serving the devices f= or the iSCSI targets. I have 7 SAN systems running this setup. No system more recent than r310734= is showing that behaviour. The only system more recent than r310734 (at least r320056, and until 11.1-RELEASE) was affected by this, and became healthy w= hen downgraded to r310734 (r310734 was chosen simply because it's the most rece= nt revision on all of the 7). First I had the strong impression that we had a hardware problem. Memtest86+ found no problems. We found multiple SNART ATA errors that were caused by t= he bad cabling, and that seemed to be the rooy cause for the moment, but after switching to a new cable (and also to a new HBA, new server and new enclosu= re) the problem hasn't vanished. It was solved only after the downgrade to the r310734. The SAN system is up and running for 48 hours already without pool corruption (which usually happened withing first 12 hours of running) and without panics (which usually happened within first 24 hours). Unfortunately, I have no crashdumps, because the mpr(4) blocks crashdump collecting (see the discussion in the freebsd-scsi@). I have only the backtraces from serial-over-ethernet IPMI, which I will attach here. Problem initial description: https://lists.freebsd.org/pipermail/freebsd-fs/2017-August/025099.html --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 11 08:18:23 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87055DCA9A1 for ; Fri, 11 Aug 2017 08:18:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 72AE4663EB for ; Fri, 11 Aug 2017 08:18:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7B8INAg063840 for ; Fri, 11 Aug 2017 08:18:23 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219760] ZFS iSCSI w/ Win10 Initiator Causes pool corruption Date: Fri, 11 Aug 2017 08:18:23 +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-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emz@norma.perm.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: 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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 08:18:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219760 --- Comment #7 from emz@norma.perm.ru --- Created attachment 185276 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D185276&action= =3Dedit backtraces showing the issue These are panic backtraces collected within one month from the affected sys= tem, running multiple revisions affected up to 11.1. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 11 08:59:59 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0BB2AD94363 for ; Fri, 11 Aug 2017 08:59:59 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2F3867E32 for ; Fri, 11 Aug 2017 08:59:58 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A6C3820B14 for ; Fri, 11 Aug 2017 04:59:56 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 04:59:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=NCoaT9HjqAA1c+0vsNXKtaR1YGJXJMaO4KCL2GotCO8=; b=NXlx3PwF o+56bTDZRu2jaLkxHN5062BMz9tr6v1Emvu5rt6BFIAqHaGaG/QaqflqVk2dC57l 9YIIYSh07etj7UcG/HDLns04oHN1sGjILXnXHbShFRQJyyr0PmMt2HjZOHE2woFw 2ZjF59BMxmHlWe36afHJbnAFMAyAwJrs47DVqqu9MRGXhx6MsuVKwAw/NKoiFHf4 X5L/ARdoYzQIatyqR7oXFfugoRd95ZNkhT8KUxtdM1VZNwfiwzU25XQYkRQtlEJ9 lWfXwxWpkUlE7+jMCi6LVU60WHByYeV6xs18jYoUUDxDfsLFBXZvZYdCPoyOoLbH rH/G5i2WkWttJA== X-ME-Sender: X-Sasl-enc: A+iE1B2aCH/yQ+i6Cn0tR9q6ipyJhRJHpSthRjp/rRJN 1502441996 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 640A17E300 for ; Fri, 11 Aug 2017 04:59:56 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 5A7A7D6 for ; Fri, 11 Aug 2017 08:59:55 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id D597C102E49; Fri, 11 Aug 2017 10:59:53 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 10:59:53 +0200 In-Reply-To: <87y3r0ankb.fsf@vostro.rath.org> (Nikolaus Rath's message of "Thu, 03 Aug 2017 13:38:28 +0200") Message-ID: <87efsifpiu.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 08:59:59 -0000 On Aug 03 2017, Nikolaus Rath wrote: > Hello, > > I am the upstream maintainer of libfuse. I'd like to refresh / improve > the FreeBSD support in libfuse. My goal is for libfuse not to require > any FreeBSD specific patches. [...] Stefan kindly helped me setup a FreeBSD VM, and libfuse is now compiling nicely. However, there is one problem: I am not able to mount any filesystems. The error is always: # example/hello /mnt fuse: failed to open fuse device: No such file or directory Do I need to do anything special to enable FUSE support in FreeBSD? Thanks, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 09:01:23 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1524CD946E1 for ; Fri, 11 Aug 2017 09:01:23 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::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 9BD4D681A9 for ; Fri, 11 Aug 2017 09:01:22 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x234.google.com with SMTP id 33so11159110wrz.4 for ; Fri, 11 Aug 2017 02:01:22 -0700 (PDT) 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=3OjBipwaUCCXsBCn4WA2GKo04UV4Y36HgkXtVQ/BEQY=; b=apNy6UpfqvhKWScGjRCmOUfrzAbB8aujBFFr5/zSey2fZsfcOatNwKLMAyMgaH+oOU U/kpdDq1IIhioAYlmEyoRqew51me/QkxELxYo0QuSeawoWPEg4ALyCZDDb/9iyQsbOze cU0pUqzERuiPAeUM+I4i4QKacLHf3V3Dvwo90I1m1dVsUnqB/DZbDoB5TgPOgZ7gTd/T YUS6tLPWWdBjNzK6l9TjUe7TX7WPGtQU0Vqur8bnf++K0VnIQ7WZsUCckUM2V15WXXv8 E5/88i1MPRHsmNHeuLUKsgSADT34xP8w8Fjz+xLFI+TgJtM8EvJ5sXuWfQNVzu78jpWo 5P5w== 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=3OjBipwaUCCXsBCn4WA2GKo04UV4Y36HgkXtVQ/BEQY=; b=geXI9j0eKlc9IT2CxWRjteHJH4H+x5rqJqzwNsUZR9hS+AI8DasCJHac4M+p0BKBnJ pcAfsSF5N3MkAfcSdrKRt/ze6JJtwO4UsfHb1u9L/ACOf5yZB0grPo05LSX0Nfv5Ur5m O0ZgdjB9yUlJAu74GWNWgpdB4SDxO/13Wm2z8ar+APsLVTcDGWV/37F1SIpaxhMtsPhQ oawCUdJdRjOI/edtYdf6ngPMF7bl+62I9DF5OULHXJ7MJUmeUT/b9RgCCz9Efjgywfd4 U8zyRfjbpH3QMkUCF/j9+DwgGSeIaDYTzOum3ZOGx/XFhOPz51OES6GGXrSsnGLEy8OX +D2g== X-Gm-Message-State: AHYfb5jbyWIAZJbItgHHD9MavhfbneAx4xmsEWvpK/WZS5quo+QA3B2Y oiFhNoTS9vQDqJYwhx8= X-Received: by 10.223.131.130 with SMTP id 2mr12188900wre.51.1502442080016; Fri, 11 Aug 2017 02:01:20 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id z9sm489314wrz.0.2017.08.11.02.01.19 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 02:01:19 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87efsifpiu.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 11:01:17 +0200 Content-Transfer-Encoding: 7bit Message-Id: References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 09:01:23 -0000 > On 11 Aug 2017, at 10:59, Nikolaus Rath wrote: > > On Aug 03 2017, Nikolaus Rath wrote: >> Hello, >> >> I am the upstream maintainer of libfuse. I'd like to refresh / improve >> the FreeBSD support in libfuse. My goal is for libfuse not to require >> any FreeBSD specific patches. > [...] > > Stefan kindly helped me setup a FreeBSD VM, and libfuse is now compiling > nicely. > > However, there is one problem: I am not able to mount any > filesystems. The error is always: > > # example/hello /mnt > fuse: failed to open fuse device: No such file or directory > > Do I need to do anything special to enable FUSE support in FreeBSD? Hi Nikolaus, Certainly you need to load fuse module : kldload fuse Ben From owner-freebsd-fs@freebsd.org Fri Aug 11 09:03:05 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9F833D949B8 for ; Fri, 11 Aug 2017 09:03:05 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (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 32C3468331 for ; Fri, 11 Aug 2017 09:03:05 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id t201so37112857wmt.1 for ; Fri, 11 Aug 2017 02:03:05 -0700 (PDT) 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=01ubHVZQkpo3uEXVNdnEku0Ob1mNKAYY06KAl6+XpwE=; b=SCKPkdooSdsOAeCBvV+48aMN+rK/VseJVpdioAsFFKRGd7UbFJVOh999wZ4o0NdgI/ 9CwkALGLkKswb8H1CUjylRTDSl0C7ShexFh+9HOVojwp9nQR+/cqlkeJ73mk2+2ClHCu rM1Ww1ID/9dxx9RT4/PtkFDlYMV+ojdP5j0JK3XvnyuOHlzqt/JsO2gIGJU9je78OfrR 0PkbjYm25Q1uMB4xZaPi8q7Uz3hWQBHE9BWbPfOC05hSm82tcqUldPJXIiczQPbpF1lp CEtG9Ljt6HO+ihD/+6H1StUg0ld7xcYzOKVFyeynCkx9lap3gsRXZL8STTNQ+WjbJxJd WDKw== 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=01ubHVZQkpo3uEXVNdnEku0Ob1mNKAYY06KAl6+XpwE=; b=RM/Lw+XSm4Mfc2SygXP1kk+7hZ1nneFoSQfxeIzGOOx/+XPKYOyUZjn/FGqTdx8S7M xqM/j/7k0ZoblxAN/froLXxy0+d7YsdFsuTLwXeoClzCT/ZQErzBlDVZm57T/dKAmaQp 5DIuzMDihkmGYQY1M5hWnKfuK9uWQOq0UO13X6MMeXEvId4ttSh+UwAKQPjiYePMXobR FRwOteLTkQIe4FkKe8Bxi6/xkCxAz/oAcY5AfZlQ8x+4yO7BI3saTFydMwXeH5RafP+o JjLShc3/iDgjrksRatbWUNpdbLSXSKt6aONDf3lfBxxk7fCNfe7Uogli6+183r77ThZ3 q8yA== X-Gm-Message-State: AHYfb5iHpavEvAJynlP7XRiybpf1E5B5hBImRrHDAbFu5OgchR8b/xAK OJqwI+rv/dCgGkCThPc= X-Received: by 10.28.143.206 with SMTP id r197mr8814666wmd.69.1502442183449; Fri, 11 Aug 2017 02:03:03 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id w65sm638363wme.6.2017.08.11.02.03.02 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 02:03:02 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: Date: Fri, 11 Aug 2017 11:03:01 +0200 Content-Transfer-Encoding: 7bit Message-Id: <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 09:03:05 -0000 > On 11 Aug 2017, at 11:01, Ben RUBSON wrote: > >> >> On 11 Aug 2017, at 10:59, Nikolaus Rath wrote: >> >> On Aug 03 2017, Nikolaus Rath wrote: >>> Hello, >>> >>> I am the upstream maintainer of libfuse. I'd like to refresh / improve >>> the FreeBSD support in libfuse. My goal is for libfuse not to require >>> any FreeBSD specific patches. >> [...] >> >> Stefan kindly helped me setup a FreeBSD VM, and libfuse is now compiling >> nicely. >> >> However, there is one problem: I am not able to mount any >> filesystems. The error is always: >> >> # example/hello /mnt >> fuse: failed to open fuse device: No such file or directory >> >> Do I need to do anything special to enable FUSE support in FreeBSD? > > Hi Nikolaus, > > Certainly you need to load fuse module : > kldload fuse And you can add the following to /boot/loader.conf : fuse_load="YES" So that it will be automatically loaded at boot time. Ben From owner-freebsd-fs@freebsd.org Fri Aug 11 09:15:03 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66EF9DB553D for ; Fri, 11 Aug 2017 09:15:03 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 38EDE688B5 for ; Fri, 11 Aug 2017 09:15:03 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2E69120C2C for ; Fri, 11 Aug 2017 05:15:02 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 05:15:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=W/HQzgjYa2ybgpGL3PHTp312/XVhfKYGCOxt1xfC734=; b=BuduL4P+ P4WyW+S+lzucXNHiC7ruf2wjI51u6YdLYBGIAothKpnYmeY1JP4YmILGMaqbFQLA yb04m91cqVe9tPe+kEdlFAvA+pr8IBOyp39v8EBw9D29cxbpiNN3TIeyxFODfyRr OtUu1DBLXKBTceH0lzGJRBkYKgWFmvLyhrXZFBzwcsLcQGphAosubjL3YLsj+ZMV WRCmeLX93IwY3tPvjAjkNFjKH4eQuOgEkVT93KiqcH3Z3EQsIbSwOFwk6ZiM39Ed xrkYeBP/OR76Xf5/hZTD3w+ZgtVid7e7vhdLyH1ml0Om+6jMqJeq5Ja7dGBLFD/2 j0EpFOLzxb2mkQ== X-ME-Sender: X-Sasl-enc: LKFUaQ8ohiKhyPdl26YuZ6sTHMXMIMbleZOXsSKMa9Mt 1502442901 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id DF70B24442 for ; Fri, 11 Aug 2017 05:15:01 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id D386CD6 for ; Fri, 11 Aug 2017 09:14:54 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 710D9102E49; Fri, 11 Aug 2017 11:14:28 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 11:14:28 +0200 In-Reply-To: <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> (Ben RUBSON's message of "Fri, 11 Aug 2017 11:03:01 +0200") Message-ID: <87bmnmfouj.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 09:15:03 -0000 On Aug 11 2017, Ben RUBSON wrote: >> On 11 Aug 2017, at 11:01, Ben RUBSON wrote: >>=20 >>>=20 >>> On 11 Aug 2017, at 10:59, Nikolaus Rath wrote: >>>=20 >>> On Aug 03 2017, Nikolaus Rath wrote: >>>> Hello, >>>>=20 >>>> I am the upstream maintainer of libfuse. I'd like to refresh / improve >>>> the FreeBSD support in libfuse. My goal is for libfuse not to require >>>> any FreeBSD specific patches. >>> [...] >>>=20 >>> Stefan kindly helped me setup a FreeBSD VM, and libfuse is now compiling >>> nicely. >>>=20 >>> However, there is one problem: I am not able to mount any >>> filesystems. The error is always: >>>=20 >>> # example/hello /mnt >>> fuse: failed to open fuse device: No such file or directory >>>=20 >>> Do I need to do anything special to enable FUSE support in FreeBSD? >>=20 >> Hi Nikolaus, >>=20 >> Certainly you need to load fuse module : >> kldload fuse > > And you can add the following to /boot/loader.conf : > fuse_load=3D"YES" > > So that it will be automatically loaded at boot time. Ok.. some progress. Now it fails with: # example/hello /mnt mount_fusefs: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /mnt= : No such file or directory fuse: failed to mount file system: No error: 0 Anyone know what this might mean? Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 09:24:18 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C3FDDB5F64 for ; Fri, 11 Aug 2017 09:24:18 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 1E7146931B for ; Fri, 11 Aug 2017 09:24:18 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id y43so11398836wrd.3 for ; Fri, 11 Aug 2017 02:24:18 -0700 (PDT) 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=6tw9pdc5TCz1wZ5Sw85ego+BnMA9g/EeWmm6Ho21Bug=; b=WD4S3Je0bx003sOo9mcl6s5VnHrWl9R7X1mg/ZWkL14dMPtqj8Aphw4qLh7xxPlQey hBcTo2IiY9dbQqjm7luWwrRsaU+NBAb8+n02QK0yGw/p3y/7fgiLvUyQZDK4idc9x03b Oo5+y/1ufdFCROsM4CnQaexhTHDGO3EInRbOrhE0KPP1qctAmX/FX7HVVWFw/xpCG34/ zw68AJ/Sk2DY89I3eSraxaQM8hxNWM7VSylBOszgx9hzL3Ts45h2KxoD78PoJyXmzRMR uBA3bbRorWeM21f76kuZhGYUVi+ookecdyNCYADF1xLGU1VAWf556nbIUUBzqy6IiBHc Fmmg== 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=6tw9pdc5TCz1wZ5Sw85ego+BnMA9g/EeWmm6Ho21Bug=; b=F9J+4YJMuDGOGsaRc+o3yNM7p3vD3qSrdEjIR6vc0Mdb1I8biXLVBfJEIDkhOTYo9t 9UNH0Jlk/xwGvLGG2to+I03knxJBvrguS6EiEjiMqRGQ4fSYpLGkrbjy7oApj5HK3OGL qy3BeadKUbajLIoLb6p6WSTraZO3zjF8LBjsRSwUBuwhwM60lbkrTwj3c1Pm00Rb9sBw ozX0hF3Lm/Ic4loLWO+ubbhQEJWgcTrcEUnzXmPBuj9MOZNP4Af77WBqterjzKoQJQIX 6bAUqpPWx0X3Mvavu97VLm+86//0uAkswfktCBDV6vGUbK9bMIldc1M1YfQ/bOayYwNI Fq5A== X-Gm-Message-State: AHYfb5i6y4BZbzlsgAhsqTFph9UbeKhsQzfalqSEVzToKlvdQhyZLMxN nAPlZMHKQNW5nBcTAOY= X-Received: by 10.223.169.131 with SMTP id b3mr11638835wrd.126.1502443456204; Fri, 11 Aug 2017 02:24:16 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id k46sm452667wre.1.2017.08.11.02.24.15 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 02:24:15 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87bmnmfouj.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 11:24:14 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 09:24:18 -0000 > On 11 Aug 2017, at 11:14, Nikolaus Rath wrote: >=20 > On Aug 11 2017, Ben RUBSON wrote: >>> On 11 Aug 2017, at 11:01, Ben RUBSON wrote: >>>=20 >>>>=20 >>>> On 11 Aug 2017, at 10:59, Nikolaus Rath wrote: >>>>=20 >>>> On Aug 03 2017, Nikolaus Rath wrote: >>>>> Hello, >>>>>=20 >>>>> I am the upstream maintainer of libfuse. I'd like to refresh / = improve >>>>> the FreeBSD support in libfuse. My goal is for libfuse not to = require >>>>> any FreeBSD specific patches. >>>> [...] >>>>=20 >>>> Stefan kindly helped me setup a FreeBSD VM, and libfuse is now = compiling >>>> nicely. >>>>=20 >>>> However, there is one problem: I am not able to mount any >>>> filesystems. The error is always: >>>>=20 >>>> # example/hello /mnt >>>> fuse: failed to open fuse device: No such file or directory >>>>=20 >>>> Do I need to do anything special to enable FUSE support in FreeBSD? >>>=20 >>> Hi Nikolaus, >>>=20 >>> Certainly you need to load fuse module : >>> kldload fuse >>=20 >> And you can add the following to /boot/loader.conf : >> fuse_load=3D"YES" >>=20 >> So that it will be automatically loaded at boot time. >=20 > Ok.. some progress. Now it fails with: >=20 > # example/hello /mnt > mount_fusefs: = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /mnt: No such = file or directory > fuse: failed to mount file system: No error: 0 >=20 > Anyone know what this might mean? Same result with libfuse from sysutils/fusefs-libs ?= From owner-freebsd-fs@freebsd.org Fri Aug 11 10:42:46 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ADA69DC4DA7 for ; Fri, 11 Aug 2017 10:42:46 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7F54A6C39D for ; Fri, 11 Aug 2017 10:42:45 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4B21920B03 for ; Fri, 11 Aug 2017 06:42:44 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 06:42:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=gJyeuqxC5vIN5FEz/wRGTSdfp1PSYX9nGfeLr8EyuEE=; b=HutlE/Qg FsMxIcYjphjjDx2q5kJaS9eqXDuQl9Vrz46w6hFxngtkRja1CiPQ8NIG680FctKx LOtLGy3dVNLKtCpVHIMpYUTV9B9kcRRiv3tUHdfDqKtFyexvA4NG0/fKw8PeV6RR WL0plyJqwnhA/muG47NPPdzwpQAapBx6R0/DzT7IjFLl4L7fTIn8V3ruHEHmImj/ /VnwzRnVUZIKrhbpt0P40jkxToPDhY5+S+H95Fmb3noQwQUkqdxfzKBE0hRyr/ZT T5LNPeDqeMLpV1rgVdj+I/vOYqq/FBzQEmHE5vRRGQJ9gU+D2BeHauJyBJ+5WtW7 U4l1w+ameI0u2A== X-ME-Sender: X-Sasl-enc: +rsgoV8fbCuXr+PTNE+h9fFguYAHKqRAkp3c88BRW86a 1502448164 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 07DB77E6AD for ; Fri, 11 Aug 2017 06:42:44 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 1209A110 for ; Fri, 11 Aug 2017 10:42:43 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id A85CD102E49; Fri, 11 Aug 2017 12:42:41 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 12:42:41 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 11:24:14 +0200") Message-ID: <878tiqfkri.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 10:42:46 -0000 On Aug 11 2017, Ben RUBSON wrote: >> # example/hello /mnt >> mount_fusefs: >> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >> on /mnt: No such file or directory >> fuse: failed to mount file system: No error: 0 >>=20 >> Anyone know what this might mean? > > Same result with libfuse from sysutils/fusefs-libs ? I don't know. Please keep in mind that I'm not a FreeBSD user. I want to help get libfuse to run under FreeBSD, but I do not want to spend much time learning FreeBSD. I don't know how to install sysutils/fusefs-libs, and if I know how to install it, I most likely still wouldn't know how to test it (no idea how to find out if it comes with example filesystems, or where it installs them). In other words, I'll help as much as I can on the libfuse side, but unless there's some activity from FreeBSD users, I will not be able to get things to run out of the box on FreeBSD. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 10:58:16 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2CD1DC5BF2 for ; Fri, 11 Aug 2017 10:58:16 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 81EA16CB77 for ; Fri, 11 Aug 2017 10:58:16 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id t138so6044241wmt.4 for ; Fri, 11 Aug 2017 03:58:16 -0700 (PDT) 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=dWjkgecQLjd3qrF5sr+vSOoeEs58tAVD+7grwHiGkLE=; b=Jn4elbCzWj/uP3vFYzFiz/+KPaNzsYoTm4oGIzQtp+6hOSGV24Zz+66xPFxrpgmsxt ry2yUsVsUzWBb1mE4Hu4p+XRKv4eGFjq/05YRx0RchWRYpzbirFkIrO9BW/rb7shpS6K 6YnSHWqKVEyJPFH3jbRVCo/nnrxZ6rUZWovjzMIegd5wDffxe0gTpD26unYMrILXMIUK 0cMjkrbhvYYNtS4qL6k1fnkvUfv8OZL9aYzELsWryR6UtqCnT48KG5crjFWgVBp8MFgh CYYd+TPBJpgDimTmKBeG7SDn0b/b+oWCNQPYL1iCqadj7GwPCoaN8lDho1qs4Ny3HQnG XDug== 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=dWjkgecQLjd3qrF5sr+vSOoeEs58tAVD+7grwHiGkLE=; b=F2nRluBfT69dD6DamjdoUiJkWdidwztoInTW8uhed2ORRZ425N23z6V1ZQroa/de3j qEHBqmokKh3pdr3UcSoMn/PilcNUWo7HF5P/FJ0NQkuqqsDoFiOGuVnJ9hf52n2XJki3 gH5ZSGfIUTgNZGP9EA/lI0JOa1X4dSUNfH7fsfgA9QFcRYH7plt62VRbFErGGc8jBYAm BSapkjczDvhtAR1ZquVnGXLtZWx1eLtc/FBGEk9tX50f47DMtXpJ6HMMsA61L/TCox4B eMUnxKvmCAC4mmENkEVqP9DpKSbgn+yw+ITlwR4WzcdRVlWoptdpRyd8g9nQDd5kUmve xYSA== X-Gm-Message-State: AHYfb5jo20RyItRX+TPeShaMU9UBFknA3r8B6IU3BZZMMZMwmcpj6rK4 IrL0lQEzuLTrmTE/w6jnSQ== X-Received: by 10.28.125.195 with SMTP id y186mr9798503wmc.37.1502449094147; Fri, 11 Aug 2017 03:58:14 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id h190sm134606wmd.4.2017.08.11.03.58.13 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 03:58:13 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <878tiqfkri.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 12:58:12 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 10:58:17 -0000 > On 11 Aug 2017, at 12:42, Nikolaus Rath wrote: >=20 > On Aug 11 2017, Ben RUBSON wrote: >>> # example/hello /mnt >>> mount_fusefs: >>> = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>> on /mnt: No such file or directory >>> fuse: failed to mount file system: No error: 0 >>>=20 >>> Anyone know what this might mean? >>=20 >> Same result with libfuse from sysutils/fusefs-libs ? >=20 > I don't know. Please keep in mind that I'm not a FreeBSD user. I want = to > help get libfuse to run under FreeBSD, but I do not want to spend much > time learning FreeBSD. >=20 > I don't know how to install sysutils/fusefs-libs, and if I know how to > install it, I most likely still wouldn't know how to test it (no idea > how to find out if it comes with example filesystems, or where it > installs them). Then, you can list available fuse packages : # pkg search fusefs You can install one of them : # pkg install fusefs-encfs It will automatically install required dependencies, so it will install = fusefs-libs. This could be a first step to be sure Fuse correctly works on your test = machine. Then you are certainly interested on how fusefs-libs is packaged on = FreeBSD. So, let's get the ports tree : # portsnap fetch extract # portsnap fetch update And let's go to fusefs-libs port : # cd /usr/ports/sysutils/fusefs-libs Here you have the package files. You can see the build required dependencies : # make build-depends-list You can install them using pkg if you want, to avoid compiling them : # make build-depends-list | cut -c 12- | xargs pkg install -y Let's get all port files : # make extract Let's apply patches : # make patch Let's build : # make build Let's install : # make install (or make reinstall if it has already been installed = before, by pkg for example) Let's clean everything # make clean Here is a quick howto on how it works with FreeBSD. Of course feel free to ask ! Ben= From owner-freebsd-fs@freebsd.org Fri Aug 11 11:01:01 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33C8FDC5E68 for ; Fri, 11 Aug 2017 11:01:01 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout08.t-online.de (mailout08.t-online.de [194.25.134.20]) (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 E9EFF6CE65 for ; Fri, 11 Aug 2017 11:01:00 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd18.aul.t-online.de (fwd18.aul.t-online.de [172.20.26.244]) by mailout08.t-online.de (Postfix) with SMTP id B263041D647E; Fri, 11 Aug 2017 13:00:51 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (GWwSNBZ1whvPDS4u0k+Go3ficAaYmZrvJdKUXu31JweMxKsmn9a0pVoxDVvJOxWg67@[84.154.108.129]) by fwd18.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dg7gQ-3OzSca0; Fri, 11 Aug 2017 13:00:50 +0200 Subject: Re: State of FUSE on FreeBSD To: Nikolaus Rath References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> From: Stefan Esser Cc: freebsd-fs@freebsd.org Message-ID: Date: Fri, 11 Aug 2017 13:00:50 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <878tiqfkri.fsf@vostro.rath.org> Content-Type: text/plain; charset=windows-1252 Content-Language: de-DE Content-Transfer-Encoding: 7bit X-ID: GWwSNBZ1whvPDS4u0k+Go3ficAaYmZrvJdKUXu31JweMxKsmn9a0pVoxDVvJOxWg67 X-TOI-MSGID: 4d270a1f-fa26-4f10-880b-ca6318bf6abb X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 11:01:01 -0000 Am 11.08.17 um 12:42 schrieb Nikolaus Rath: > On Aug 11 2017, Ben RUBSON wrote: >>> # example/hello /mnt >>> mount_fusefs: >>> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>> on /mnt: No such file or directory >>> fuse: failed to mount file system: No error: 0 >>> >>> Anyone know what this might mean? >> >> Same result with libfuse from sysutils/fusefs-libs ? > > I don't know. Please keep in mind that I'm not a FreeBSD user. I want to > help get libfuse to run under FreeBSD, but I do not want to spend much > time learning FreeBSD. > > I don't know how to install sysutils/fusefs-libs, and if I know how to > install it, I most likely still wouldn't know how to test it (no idea > how to find out if it comes with example filesystems, or where it > installs them). Hi Nikolaus, I have offered support via phone and can only repeat that offer now ;-) In order to install any port, you csan follow the steps outlined in an earlier mail: # mkdir /usr/ports # cd /usr/ports # svnlite co https://svn.FreeBSD.org/ports/head /usr/ports # cd sysutils/fusefs-libs # make install The supported filesystems can then be installed in the same way, e.g.: # cd /usr/ports/sysutils/fusefs-ext4fuse # make install To reinstall: # make reinstall > In other words, I'll help as much as I can on the libfuse side, but > unless there's some activity from FreeBSD users, I will not be able to > get things to run out of the box on FreeBSD. You've got my phone number ... Regards, STefan From owner-freebsd-fs@freebsd.org Fri Aug 11 11:05:30 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E9E3DC631B for ; Fri, 11 Aug 2017 11:05:30 +0000 (UTC) (envelope-from nikolaus@rath.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44D6B6D0AA; Fri, 11 Aug 2017 11:05:29 +0000 (UTC) (envelope-from nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 85E5120B47; Fri, 11 Aug 2017 07:05:28 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 07:05:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=kuIu0d IuMEcEr0lzGIZJQl/XX/mJ4s02Np41VXgTplo=; b=idzT4uEOOcSnyehBsEHZqw 7zhNTcc5cEeTBFo9/wV/WGMPPb5JV5wuPwVjDgbKirYcdLbF0VZgRlsvQ4Pdu3Q3 d5O4kfgmZM4OD55vkqABpuEWHjEEFiZi1K/96xEjarpNKAKEKmAzBsfgZn1DoW9I eWjtgY7pBmSlQI3vHS3brCjacbtthpu9g2pZOjan7tzgs+WRR+l24t8KePmFofbr j6x4d4bcCqCZ66RbQ1FdIOKy18Xn0MvDAVPePrmsA54L6X0/QMnu5BsLpK7vQ8pF tH8LRgiLIx2PMpPKxNnl27WXaNAlkS81Enn0yToaqqvkHJ8H/5EnTR2c7r1N14hw == X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 6AD7D9571C; Fri, 11 Aug 2017 07:05:28 -0400 (EDT) Message-Id: <1502449528.2708965.1070242424.56D90DEB@webmail.messagingengine.com> From: Nikolaus Rath To: Stefan Esser Cc: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-33d44821 Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 13:05:28 +0200 In-Reply-To: X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 11:05:30 -0000 Hi Stefan, On Fri, Aug 11, 2017, at 13:00, Stefan Esser wrote: > > I don't know. Please keep in mind that I'm not a FreeBSD user. I want to > > help get libfuse to run under FreeBSD, but I do not want to spend much > > time learning FreeBSD. > >=20 > > I don't know how to install sysutils/fusefs-libs, and if I know how to > > install it, I most likely still wouldn't know how to test it (no idea > > how to find out if it comes with example filesystems, or where it > > installs them). >=20 > Hi Nikolaus, >=20 > I have offered support via phone and can only repeat that offer now ;-) >=20 > In order to install any port, you csan follow the steps outlined in an > earlier mail: [...] Yes you did, and I very much appreciate that. But as I said, I don't actually *want* to learn to use FreeBSD. Neither on my own by studying the web, nor with instructions by email or phone. If the FreeBSD community is interested in getting libfuse in a better shape, then I'd like to see someone install the master branch, try to compile it, and answers questions like the above on their own. No hard feelings if no one is interested in that. But please understand that in that case I'd rather invest my time in something else as well. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 11:24:31 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4FB8EDC75AC for ; Fri, 11 Aug 2017 11:24:31 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 214226DC23 for ; Fri, 11 Aug 2017 11:24:30 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7F0E420B14 for ; Fri, 11 Aug 2017 07:24:29 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 07:24:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=0tvdJgyHMus2EnHrzhr5R4XT8+1ojUgeIbMSVrg/maA=; b=RhyynDKK uPSnorwINOPsNgWtXlvAYET1zGLNZIwj7BjsCq4kGbUfmMSDzUFfHwJs7wKVK2K/ ZyJ555wU3vj3IVi929j2rU/EazEsminKAwPtJ/aIY1llz3O0tiXjpi1wIEk7kqzI WMIAdRQmiUm6lSZW7eX9halbdesDGMP7cLuG1U8L/RbYxm/piJIxz1Q2DnHLhu14 /rrOk2kY0DIvrWPBxM4j8gfwuXxOZuWe9ZvAE/IIgcLc3SgcFWvDnOjRW0uIBxOW TlZg7EuBiAo1doV6k9AUHbXWmUd/UpLru6dCdXYystsJdvgocixOCytP0uzW4g1N 0LtxfizJIn6hzQ== X-ME-Sender: X-Sasl-enc: wwQbTFTbMjxmwXKUdFulcPZ4WasRkTE7NHsaZPjmD/cl 1502450669 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 2F9D97E881 for ; Fri, 11 Aug 2017 07:24:29 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 0A693110 for ; Fri, 11 Aug 2017 11:24:28 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id F219E102E49; Fri, 11 Aug 2017 13:24:21 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 13:24:21 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 11:24:14 +0200") Message-ID: <8760dufiu2.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 11:24:31 -0000 >> Ok.. some progress. Now it fails with: >>=20 >> # example/hello /mnt >> mount_fusefs: >> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >> on /mnt: No such file or directory >> fuse: failed to mount file system: No error: 0 >>=20 >> Anyone know what this might mean? > > Same result with libfuse from sysutils/fusefs-libs ? No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something of the BSD-specific mount code wasn't merged correctly? Here's the pull request that I merged: https://github.com/libfuse/libfuse/p= ull/189 Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 11:51:19 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D1FFDDC8DE9 for ; Fri, 11 Aug 2017 11:51:19 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 627596EA18 for ; Fri, 11 Aug 2017 11:51:19 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id m85so39989225wma.0 for ; Fri, 11 Aug 2017 04:51:19 -0700 (PDT) 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=ZFtb/VZPMJJlb2zbnP3gzwPQPgKBx5SLmagYzOx7XqA=; b=lKu48mxnOUSiGhQ5LQmdd7VjLwc05PGwZpbD12UO4d4JrpA52aSs92mxpW2y2hel/c BFlQ3gEHNhmUhi74tIC2D/8U55XPfbb7wX5AJSfBKITS04RAHDHCQLPVdZ32DOnM2+mn zOVz68HlwBwebzLv2Dbch9UEB5QOMVdWZJoi3gRErckHkH4shR+FwCtd+GqRi0ApeluY kQjfcfk8yHj5I3NKdPegElEluib+qtiGzZWfy2apLsYUTJlcSmahrcaYPn31tpOihf+I AykmUKDfwvm8VPybwtJZ/uCJ2R27KNDZ64nbb73hjWdU7RAaqnf5qcHzC4k25o6Ecl31 8B+g== 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=ZFtb/VZPMJJlb2zbnP3gzwPQPgKBx5SLmagYzOx7XqA=; b=WoqiTlGzRaNzF8jThADXSib/sTWk3RTgB3kbWRChXxvndIltQmTtdE1QPsiAI7xghI VWkvO7j74oO10mYGubBrOgfdXPjpOV60aflq266rpbwcXNJuLp7TcCFRAtcOfgV4rWe3 oF5x7vCCye/auNXDcvwpp8bk6ZssJxmebB8aYNTl2d8JDAFCQ5owqsn9nW4Y/B/purtE vjZXXIYmqq6jZmYkkqpsZk7nWy+lIuiLk7qQqFnYN4xpv863sZBGoFjoldjZG3xaogy3 OK1Vc1MjT4XD0+UTTbpNtoNBa6uoj/T1bejTJ4+U+TGY9gPMccRYCLD2gh87OXfuYQ4P PPqA== X-Gm-Message-State: AHYfb5jSZByUylB+0xFz8LXTpcJLYRlunWhoW6OH6qYQ6tCPCrt/t9E8 +IxRdjkcPPrhcbJklag+Mg== X-Received: by 10.28.159.133 with SMTP id i127mr8787768wme.172.1502452277487; Fri, 11 Aug 2017 04:51:17 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id 12sm1116548wmy.44.2017.08.11.04.51.16 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 04:51:16 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <8760dufiu2.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 13:51:15 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 11:51:19 -0000 > On 11 Aug 2017, at 13:24, Nikolaus Rath wrote: >=20 >>> Ok.. some progress. Now it fails with: >>>=20 >>> # example/hello /mnt >>> mount_fusefs: >>> = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>> on /mnt: No such file or directory >>> fuse: failed to mount file system: No error: 0 >>>=20 >>> Anyone know what this might mean? >>=20 >> Same result with libfuse from sysutils/fusefs-libs ? >=20 > No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something of = the > BSD-specific mount code wasn't merged correctly? >=20 > Here's the pull request that I merged: = https://github.com/libfuse/libfuse/pull/189 Current patches can be found in this dir : # cd /usr/ports/sysutils/fusefs-libs/files (do not forget to run the 2 portsnap commands of my previous mail before = if you did not run them yet) As far as I can see, these patches and PR189 are the same. However there were new commits after PR189, perhaps you should test the = lib at this point ? = https://github.com/libfuse/libfuse/tree/8f3c800e151d8d8844d851344f85f6baa3= ac2d8f Sounds like mount_fusefs does not get a correct name (ZZZZZZZZZZ*). Ben= From owner-freebsd-fs@freebsd.org Fri Aug 11 13:33:50 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBF39DCF111 for ; Fri, 11 Aug 2017 13:33:50 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8FE19721FA for ; Fri, 11 Aug 2017 13:33:49 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9272720C8E for ; Fri, 11 Aug 2017 09:33:48 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 09:33:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=mZhykabVL2NeRgx31Bry7ryDuAaMUM6z1NiltTbn/H4=; b=HqrJoVRT ISuRZ5r50vsA8h/AobrBp421uKCMN3yZiMxM8ZpoBYN0AupV9Q2ecaNEUCh/xtaQ Yl0DjH1sYyz9OBE24V4PnIdlrfCY60tu8fADIOnloeW4EgYsLRuij0mLyCIEwCXP cUINwBEicIQ2xue42P7feQbpb4ZLqlrfKx3EhHPHUZYWJ1YLlEdAlQabd6UeaD64 X8J+/g3aBQ8Qab4j1mTykqQbKUAko9S2vS84quoAEMFWYvBvgOU42n8JlhyWB0mX N4JStlziyeGZb1j7yIH8CkWEwEXylXvVAX4SDoZ/SXzu8ezN110/5OF+eHLSjpaj RoJYfiBVQhS3JQ== X-ME-Sender: X-Sasl-enc: 5pPDqP+54GfMTgbk8kdOP6Awo3+eRJ4w5s840BqW97pX 1502458428 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 49A9E7F987 for ; Fri, 11 Aug 2017 09:33:48 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 63FAF110 for ; Fri, 11 Aug 2017 13:33:47 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id C59F3102E4A; Fri, 11 Aug 2017 15:33:45 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 15:33:45 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 12:58:12 +0200") Message-ID: <87378yfcue.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 13:33:51 -0000 On Aug 11 2017, Ben RUBSON wrote: > Then, you can list available fuse packages : > # pkg search fusefs Hmm. What should I make of this? [root@ ~]# pkg search fusefs pkg: Repository FreeBSD missing. 'pkg update' required pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeB= SD.sqlite) failed: No such file or directory pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/meta.txz: No route to h= ost pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/packagesite.txz: No rou= te to host But: root@ ~]# ping pkg.FreeBSD.org PING pkgmir.geo.FreeBSD.org (149.20.1.201): 56 data bytes 92 bytes from 192.168.20.1: Dest Unreachable, Bad Code: 9 Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 8719 0 0000 3f 01 88a3 192.168.20.103 149.20.1.201=20 Thanks! -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 13:36:34 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEC72DCF43A for ; Fri, 11 Aug 2017 13:36:34 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x236.google.com (mail-wr0-x236.google.com [IPv6:2a00:1450:400c:c0c::236]) (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 79629723AA for ; Fri, 11 Aug 2017 13:36:34 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x236.google.com with SMTP id v105so13659716wrb.0 for ; Fri, 11 Aug 2017 06:36:34 -0700 (PDT) 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=d+B86GOLrdbqXYcy4ea288aTd4JkF6hQXXQwV1qt9+0=; b=Egyp1MTjaHEqLeMfUQQT/1nhs3b+JViO51rHGm+kHR3iUi6tzysfEs7wzrKC0g0Efx G/24MkK4kmxoGLYzFS2z1QE+X38ue+wfpw1OTh6wZAKX6GImj3I5Xy/P+6aelH5V5gBF bKQiW1wNctDFG7E9PDIk5vt2uMv8vNmpLQn3JaxkQetX4gQv07ZgRYQZv3rEhoNrXQ23 TogmaGBnU/kSg33vddPI+M/LrvimxC3BNkiotwWJh754RNOy3oYMR6bScaKhX7OhoQs/ mw5Sp0O8PaEbmBhsMdJIv4RcZsufJVV1sr3JB0W6uRZeigJdnDdkmhWQ4BYdBzylpQE5 cXTw== 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=d+B86GOLrdbqXYcy4ea288aTd4JkF6hQXXQwV1qt9+0=; b=K2lufQb7KWyal/PIJilHlCM/9oBJIAaaS+x4oSOjKPeN9X2nzxoItEegSWeqoaMDOw pDcmUmlMjrYSzs14hbbasmhvW7cG9T7RaIG71bS3pSad9/mXamKuKohSiEhlE46ZREDJ xmaB2wOagaOqxrEKz3oVxBWgDyFUpX2qAFpn8IAAuTbhPj/g7mPjTNv2x837ZZH8fx63 1kZkrXP+jG/+Ghpf6dYkDjbBsfyQSrf466zW2UTPFDJvBlurDNGSpZt9p8yZsum0xmpo ZtznxHZoF0owZ/mgOeRDVURtHeJP2SmqEsG6bl1WpCfnLRcl4Uo4/w88J79l5qvKst5j yrWg== X-Gm-Message-State: AHYfb5jCiiK2h7Y3HoAgW7EezMwc7u48cgXDqDnGbZF0keWzJL7BDeZc 82nf1iZJ1L+SVxFiggA= X-Received: by 10.223.139.89 with SMTP id v25mr10792142wra.248.1502458592485; Fri, 11 Aug 2017 06:36:32 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id l2sm1007264wmi.31.2017.08.11.06.36.31 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 06:36:31 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87378yfcue.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 15:36:30 +0200 Content-Transfer-Encoding: 7bit Message-Id: <6DA3B651-FA49-4A54-A484-651AED848132@gmail.com> References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> <87378yfcue.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 13:36:34 -0000 > On 11 Aug 2017, at 15:33, Nikolaus Rath wrote: > > On Aug 11 2017, Ben RUBSON wrote: >> Then, you can list available fuse packages : >> # pkg search fusefs > > Hmm. What should I make of this? > > [root@ ~]# pkg search fusefs > pkg: Repository FreeBSD missing. 'pkg update' required Ah yes sorry, my mistake, run "pkg update" first, so that FreeBSD will download the packages list. Ben From owner-freebsd-fs@freebsd.org Fri Aug 11 13:40:36 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36A91DCF77B for ; Fri, 11 Aug 2017 13:40:36 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0640372590 for ; Fri, 11 Aug 2017 13:40:35 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0D85020B08 for ; Fri, 11 Aug 2017 09:40:35 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 09:40:35 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=qe4MALNTHPJNueIRxcsX5qH4x8qmaHg5ueY9ah1ltJU=; b=GAMF75MR 6WeQsFDnuP1oCgdGBnPFzOR0OGYt78V11X3nUmE1/jFpbYTKq3hTubFlhDk8bVZe H1qWu96g1HR8VrmtHtkWWLwlK7s53OTLKM3wyFisZzE+crMYp8fZSmHz6lJyFtao l6Dq4HX5rkpbmZmKADTHDnarbUDY4lz4dDEdpGM89iAuZFqgzY4Wh122i1gaxqxY uq0Bn0wWoDHKPw6yLGmJ9jnTEenJ54TDkfxESFJlzYxGrgAZnVjmlBu9n//r1nSB HA2OaFhpf5CDfUJltawxM4PnqrX7Hy675IOa9A+4BuUl0AZCgqeTVa+iwp4k413C uGJzJY1Gfslc7Q== X-ME-Sender: X-Sasl-enc: mkqaniFlFByJ73+mf06EED8xyOfM49FB8UiDb2j5yDeO 1502458834 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id C6FD0240A4 for ; Fri, 11 Aug 2017 09:40:34 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id CBC9C110 for ; Fri, 11 Aug 2017 13:40:33 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 23D66102E4A; Fri, 11 Aug 2017 15:40:32 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> <1502449528.2708965.1070242424.56D90DEB@webmail.messagingengine.com> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 15:40:32 +0200 In-Reply-To: <1502449528.2708965.1070242424.56D90DEB@webmail.messagingengine.com> (Nikolaus Rath's message of "Fri, 11 Aug 2017 13:05:28 +0200") Message-ID: <87zib6dxyn.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 13:40:36 -0000 On Aug 11 2017, Nikolaus Rath wrote: > If the FreeBSD community is interested in getting libfuse in a better > shape, then I'd like to see someone install the master branch, try to > compile it, and answers questions like the above on their own. It would be *really* great if someone else could give this a shot. I just heard from Stefan that he gets a very different error message than the one I got: > FUSE library version: 3.1.1 > nullpath_ok: 0 > unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 30231 > INIT: 7.8 > flags=3D0x00000000 > max_readahead=3D0x00010000 > fuse: error: filesystem requested capabilites that are not supported by > kernel, aborting: 0x10 > unique: 1, error: -92 (Protocol error), outsize: 16 This is something I could fix. But the message that I got doesn't tell me anything at all. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 13:42:34 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6510EDCFAC2 for ; Fri, 11 Aug 2017 13:42:34 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3514C728A4 for ; Fri, 11 Aug 2017 13:42:34 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8598D20CFF for ; Fri, 11 Aug 2017 09:42:32 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 09:42:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=F1DtxDXU1DErJr1OZI8XjRZ+f6qqXzPKCZAp1S4Y0fw=; b=lgcdgd0A a1UFHzQIIXXTZ0QI0bbJj5bt8fOCIPackmGf9j9w3MlBohpEjd4lKenQYz2l1Zyb hLV23LvnzgNMoUXSflaxz7CPX5i2fqNXlRUvB3lsj++0Vzml5aOMipmYuK7W9JIG 3Jx+FrdHuv3LQJiyWS0BOnNmEWYIqzFpeF2b0Ha1UeOiMOlJ0KAbngNHvwp8JKvf 6e35HZZtW8RuN5svRpxuWi3afQUG6NuI3mKxwF7VAa2uE68RFkCZvnEV56c+QApw AIiIYecxvE4dCpWvLXNPENPu9RGkkDsECSey/YpC07yAOTMpTbAowB8TD6w4LcX4 kYhrsXdpJV+fkw== X-ME-Sender: X-Sasl-enc: 8/y51WvCsNBzPDjGP2wywRpZlAO+MNxDO/fvgMMFlggh 1502458952 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 4920724442 for ; Fri, 11 Aug 2017 09:42:32 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 58410110 for ; Fri, 11 Aug 2017 13:42:31 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id D3224102E4A; Fri, 11 Aug 2017 15:42:29 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 15:42:29 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 12:58:12 +0200") Message-ID: <87wp6adxve.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 13:42:34 -0000 On Aug 11 2017, Ben RUBSON wrote: > Then, you can list available fuse packages : > # pkg search fusefs Similarly: [root@ ~]# pkg update Updating FreeBSD repository catalogue... pkg: Repository FreeBSD load error: access repo file(/var/db/pkg/repo-FreeB= SD.sqlite) failed: No such file or directory pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/meta.txz: No route to h= ost repository FreeBSD has no meta file, using default settings pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/packagesite.txz: No rou= te to host Unable to update repository FreeBSD Error updating repositories! [root@ ~]# ping pkg.FreeBSD.org PING pkgmir.geo.FreeBSD.org (149.20.1.201): 56 data bytes 92 bytes from 192.168.20.1: Dest Unreachable, Bad Code: 9 Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 871d 0 0000 3f 01 889f 192.168.20.103 149.20.1.201=20 92 bytes from 192.168.20.1: Dest Unreachable, Bad Code: 9 Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 871e 0 0000 3f 01 889e 192.168.20.103 149.20.1.201=20 Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 13:50:03 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1980DD004D for ; Fri, 11 Aug 2017 13:50:03 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7149A72AB5 for ; Fri, 11 Aug 2017 13:50:03 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2E14720969 for ; Fri, 11 Aug 2017 09:50:02 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 09:50:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=rlzuTdQVaQ8xzw71ZsTfvaYFmmL8D7pWhGkfyVMhYT4=; b=WkSP5HWo Z1Vn2x2xU4bVBOQadTnSCKapof5YCZKsRoWkzQM5TVTcsKfcYEZEqD0vurNUZmTR 2H5K/j7AzeCpSk52ILTuIKeQ+Ky3OwNReBQ5JHFM8DwIZmq8D+Mll9wuU9ee4T1t h1lgl8eJQONMSmDezG1/26j47cVQJZIpkoRdFHuQPcmFgW5vtXOJ+kAowFjrlaaa YGVYV6YnnXqSUQVjSNM/Y3AMquyM7zJlx6bLmxioG5BIGnxMvaScZDrXpTua8gYD tOIl71aeqUbcMBa4ZAa2a7zbhVjESwfvEAIK5vRU74s2HZ116g8wJmkePzkfEhQa dj8lrKO++LZehA== X-ME-Sender: X-Sasl-enc: KGS3+yglzSiVhv62qD5RxF6ytYbmXRYbH8VCX3mR2cFU 1502459401 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 8DF847F9A9 for ; Fri, 11 Aug 2017 09:50:01 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 7FCD9110 for ; Fri, 11 Aug 2017 13:50:00 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id E8FB3102E4A; Fri, 11 Aug 2017 15:49:58 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <878tiqfkri.fsf@vostro.rath.org> <87wp6adxve.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 15:49:58 +0200 In-Reply-To: <87wp6adxve.fsf@vostro.rath.org> (Nikolaus Rath's message of "Fri, 11 Aug 2017 15:42:29 +0200") Message-ID: <87tw1edxix.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 13:50:03 -0000 On Aug 11 2017, Nikolaus Rath wrote: > On Aug 11 2017, Ben RUBSON wrote: >> Then, you can list available fuse packages : >> # pkg search fusefs > > Similarly: > > [root@ ~]# pkg update > Updating FreeBSD repository catalogue... > pkg: Repository FreeBSD load error: access repo > file(/var/db/pkg/repo-FreeBSD.sqlite) failed: No such file or > directory > pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/meta.txz: No route to= host > repository FreeBSD has no meta file, using default settings > pkg: http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest/packagesite.txz: No r= oute to host > Unable to update repository FreeBSD > Error updating repositories! > > [root@ ~]# ping pkg.FreeBSD.org > PING pkgmir.geo.FreeBSD.org (149.20.1.201): 56 data bytes > 92 bytes from 192.168.20.1: Dest Unreachable, Bad Code: 9 > Vr HL TOS Len ID Flg off TTL Pro cks Src Dst > 4 5 00 0054 871d 0 0000 3f 01 889f 192.168.20.103 149.20.1.201 Arg. Ok, I need to learn how to interpret freebsd command output. I completely overlooked the "dest unreachable", it seemed to me as if the ping worked. Guess I need to fix my network... Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 14:14:24 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6832FDD16B0 for ; Fri, 11 Aug 2017 14:14:24 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 386CB739C9 for ; Fri, 11 Aug 2017 14:14:23 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id A3D6320C6F for ; Fri, 11 Aug 2017 10:14:22 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 10:14:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=SOifd8HeNnI6GYd6eMVCeCqF/LvLf1L2Q8cMxX636x4=; b=U3ZLu4Pc vULhPlOLYd4UsvwOocBlYL1VGko2rdA1vB/KFBOShXlLPcCoL3KSXqokX59gLy3t JquL7ztDkg7INK/5rkPCW19ExVjQwwBzq+7R7SSSZPCtHpa2hdxGyxBv1Bjq/DGU pUco45w9T07GsODyjE3ze474DUN2DVpcjkbXTb17digP4992rRg0Uu04gLRfNoZL R2bnAw1WzDV45oMM+a4Ssd5A7jBqQXS/MQJ+vSYKFK+JP04GKkxLXB8L4JjtGC/u hrFtU2p2Sl8zfWb264obCLza0WHD4HTZv0O22FbUwuOKJqnGvUeS8wjwRuYtRT5E 1qbDX76YXgNkLQ== X-ME-Sender: X-Sasl-enc: s8+gzsDZSMiCDS5i6nTgGAEw1NBCfScu5bFNdZfYTyuJ 1502460862 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 54D2E7E4EA for ; Fri, 11 Aug 2017 10:14:22 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 2966E110 for ; Fri, 11 Aug 2017 14:14:21 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id AC3AF102E4A; Fri, 11 Aug 2017 16:14:19 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 16:14:19 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 13:51:15 +0200") Message-ID: <87r2widwec.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 14:14:24 -0000 On Aug 11 2017, Ben RUBSON wrote: >> On 11 Aug 2017, at 13:24, Nikolaus Rath wrote: >>=20 >>>> Ok.. some progress. Now it fails with: >>>>=20 >>>> # example/hello /mnt >>>> mount_fusefs: >>>> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>>> on /mnt: No such file or directory >>>> fuse: failed to mount file system: No error: 0 >>>>=20 >>>> Anyone know what this might mean? >>>=20 >>> Same result with libfuse from sysutils/fusefs-libs ? >>=20 >> No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something of the >> BSD-specific mount code wasn't merged correctly? >>=20 >> Here's the pull request that I merged: https://github.com/libfuse/libfus= e/pull/189 > > Current patches can be found in this dir : > # cd /usr/ports/sysutils/fusefs-libs/files > (do not forget to run the 2 portsnap commands of my previous mail before = if you did not run them yet) > > As far as I can see, these patches and PR189 are the same. > > However there were new commits after PR189, perhaps you should test the l= ib at this point ? > https://github.com/libfuse/libfuse/tree/8f3c800e151d8d8844d851344f85f6baa= 3ac2d8f Nope, same problem here: [root@ ~/libfuse/build]# example/hello error: no mountpoint specified [root@ ~/libfuse/build]# example/hello /mnt mount_fusefs: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /mnt= : No such file or directory fuse: failed to mount file system: No error: 0 Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 14:22:51 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4AF6BDD20E1 for ; Fri, 11 Aug 2017 14:22:51 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 CE7E37428D for ; Fri, 11 Aug 2017 14:22:50 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id i66so48774690wmg.0 for ; Fri, 11 Aug 2017 07:22:50 -0700 (PDT) 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=FsXr/g6VZw13WBHD2PfbKi5/vMphBvw9I5oldLAzh8g=; b=IvEcNiYmYLO+UHrDJinIcAb6Tvw9Bd9CbLKAkD1TFAUH6AQuLSgyfdIhRGM1lW+Zj5 ui0nDdyF6jvjacp3UBkW9qLNyn+lDvAVR6/PvNYOMW7PfF86smd+RiODg/LYTW0fdO4y JBvo8bjNQ6EMJ5gcISphFwWN9cOVzdULf/ObuVrQ6vBPh9dKIaUrD8qKAnBUywf/7WQ5 4qAgFQQ/4w++ltowlSna6K6BRkVbI1gjBngTEQ7HvOOAPBsq8AN1e9t/iEK2edHT32nW 3c+8PZHyTW5TwCSqk+HCybssetegBcnNSmojoyUS6xmyEgjKM4Mgx7b54njVd/SYvX18 GH6Q== 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=FsXr/g6VZw13WBHD2PfbKi5/vMphBvw9I5oldLAzh8g=; b=mdLHplTAT13ZZUUQRvrlXDh+R6AnjCH2z1Kj1AqN475R+uyp6iKnA+ZsnvTO8KHxUF yxwrN7bSpT+lmUx/q6VkcSzXGbcNlenFHg8Pmw+I13I8bLT1tR5HvrV3h2A7reoEYUjj 5YByJ9G5hsUa0uq7GlmuYkq8i+gqJkdekzCi0olWE7VWqk6gLHzCPEeNi/L0z36JrrOD uohcLNLFz4pDWrOiz2C2sRc/4M2Rbdh3zBXbzQF30V2LpqWASqgFaS1sDPv2XQI69SZ2 71ra0QgBXTr4ZmHCYFQszOV0WZIUolYojkgBAloZ6z0eytpfkXKsnhUETPD86wwp5MGn MMhw== X-Gm-Message-State: AHYfb5jpKTfdnKcKIYWaH3hVebij0h8yLjRvHKlkIUwagESZ+k355Lw6 V4VHkVulljwtvkoR/Oo= X-Received: by 10.28.23.195 with SMTP id 186mr9973389wmx.173.1502461368687; Fri, 11 Aug 2017 07:22:48 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id c8sm1217352wmd.14.2017.08.11.07.22.47 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 07:22:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87r2widwec.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 16:22:46 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 14:22:51 -0000 > On 11 Aug 2017, at 16:14, Nikolaus Rath wrote: >=20 > On Aug 11 2017, Ben RUBSON wrote: >>> On 11 Aug 2017, at 13:24, Nikolaus Rath wrote: >>>=20 >>>>> Ok.. some progress. Now it fails with: >>>>>=20 >>>>> # example/hello /mnt >>>>> mount_fusefs: >>>>> = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>>>> on /mnt: No such file or directory >>>>> fuse: failed to mount file system: No error: 0 >>>>>=20 >>>>> Anyone know what this might mean? >>>>=20 >>>> Same result with libfuse from sysutils/fusefs-libs ? >>>=20 >>> No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something of = the >>> BSD-specific mount code wasn't merged correctly? >>>=20 >>> Here's the pull request that I merged: = https://github.com/libfuse/libfuse/pull/189 >>=20 >> Current patches can be found in this dir : >> # cd /usr/ports/sysutils/fusefs-libs/files >> (do not forget to run the 2 portsnap commands of my previous mail = before if you did not run them yet) >>=20 >> As far as I can see, these patches and PR189 are the same. >>=20 >> However there were new commits after PR189, perhaps you should test = the lib at this point ? >> = https://github.com/libfuse/libfuse/tree/8f3c800e151d8d8844d851344f85f6baa3= ac2d8f >=20 > Nope, same problem here: >=20 > [root@ ~/libfuse/build]# example/hello > error: no mountpoint specified > [root@ ~/libfuse/build]# example/hello /mnt > mount_fusefs: = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /mnt: No such = file or directory > fuse: failed to mount file system: No error: 0 I managed to build master branch : https://github.com/libfuse/libfuse Following instructions in README.md. Log is here, with the tests : https://benrubson.github.io/fusebuild.log And here is the example program you try to run : # ./example/hello /mnt # mount | grep mnt Not surprising as it fails in tests. # ./example/hello_ll /mnt # mount | grep mnt /dev/fuse on /mnt (fusefs, local, synchronous) Ben From owner-freebsd-fs@freebsd.org Fri Aug 11 14:31:59 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21A17DD29D4 for ; Fri, 11 Aug 2017 14:31:59 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (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 A627874B3C for ; Fri, 11 Aug 2017 14:31:58 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x233.google.com with SMTP id f21so13979267wrf.5 for ; Fri, 11 Aug 2017 07:31:58 -0700 (PDT) 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=ks3fBD0XRQmsPus7Xxx33QZA2i2XMVxdzyUi4EdOUtY=; b=iMu3WV0k2wgpD6L3IjGDmnYcPJ0swDpvLqRtKDTvfLZggG7aSuxggpiCrlArv66VgT y9w3YuqzCpjyJ+DZ4mdq+2rN69xev58/b/h4t181a+Ea7TScYwdp5KA8c8TPoGQ7h5fR y5cbJB7OtAExX/Hi9M88kPQr3gHdKd8+PTUa9jf8HMZgAyCQHaq7YFpnMJ5GMGiVGYib OC2Xl/r3bRfbaKaH73luuTQEadESQBnCqhhdDUZ0GRXTI+PO12LaV/vZCq19bxcavYpN EMYsYZgqOS41bwCgv5NQp2GbI7ne1XroR3MYVw059aBABB7I5JQZZPrzWI87WNnC/fyT Rafg== 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=ks3fBD0XRQmsPus7Xxx33QZA2i2XMVxdzyUi4EdOUtY=; b=ameYvh9sfWmJfm8E3Q9MyoBQq9jdS2FKZj4wBD2pnx0dF0rexWUbPlyeLoP5MK1fwE 6XdlUPqE99H5buqoycv6LbJX9CnV1PkhyaX1rIm770RVDK/cpPVx6akdTgz46AceGPYl cqClnyXOd/rULAg/wlJFNGAo4WDCxtoJKN9XzBzLI4l6CWF4lg1aoaK1mYmRHUpM/ZOS xSv3QQxYcA0tXYu+mjDvj/rpySWv+H9C81oW4FiO0aqP2I9BC804Qzq+TPmZ1Pr4ZZva 1cWH41ISt/ZRijgfn87ZwHQLzPmUuxE7dkFuqG+mtAiS8dbxoFLpJzuVEon9+zBTuKph 4DoQ== X-Gm-Message-State: AHYfb5gkiyJ1szOG7tCQT8VW9RFhYYm6l0GHMiwHgmUi6f5Qr918E+CA CuXAHL5FVxd8K0vO65Y= X-Received: by 10.223.154.183 with SMTP id a52mr11309246wrc.47.1502461916076; Fri, 11 Aug 2017 07:31:56 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id l81sm990118wmf.26.2017.08.11.07.31.55 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 07:31:55 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: Date: Fri, 11 Aug 2017 16:31:54 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <8EFD18D4-BD4E-4A30-A89E-129419EBC374@gmail.com> References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 14:31:59 -0000 > On 11 Aug 2017, at 16:22, Ben RUBSON wrote: >=20 >>=20 >> On 11 Aug 2017, at 16:14, Nikolaus Rath wrote: >>=20 >> On Aug 11 2017, Ben RUBSON wrote: >>>> On 11 Aug 2017, at 13:24, Nikolaus Rath wrote: >>>>=20 >>>>>> Ok.. some progress. Now it fails with: >>>>>>=20 >>>>>> # example/hello /mnt >>>>>> mount_fusefs: >>>>>> = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>>>>> on /mnt: No such file or directory >>>>>> fuse: failed to mount file system: No error: 0 >>>>>>=20 >>>>>> Anyone know what this might mean? >>>>>=20 >>>>> Same result with libfuse from sysutils/fusefs-libs ? >>>>=20 >>>> No, fusexmp_fh from fusefs-fusexmp_fh works fine. Maybe something = of the >>>> BSD-specific mount code wasn't merged correctly? >>>>=20 >>>> Here's the pull request that I merged: = https://github.com/libfuse/libfuse/pull/189 >>>=20 >>> Current patches can be found in this dir : >>> # cd /usr/ports/sysutils/fusefs-libs/files >>> (do not forget to run the 2 portsnap commands of my previous mail = before if you did not run them yet) >>>=20 >>> As far as I can see, these patches and PR189 are the same. >>>=20 >>> However there were new commits after PR189, perhaps you should test = the lib at this point ? >>> = https://github.com/libfuse/libfuse/tree/8f3c800e151d8d8844d851344f85f6baa3= ac2d8f >>=20 >> Nope, same problem here: >>=20 >> [root@ ~/libfuse/build]# example/hello >> error: no mountpoint specified >> [root@ ~/libfuse/build]# example/hello /mnt >> mount_fusefs: = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /mnt: No such = file or directory >> fuse: failed to mount file system: No error: 0 >=20 > I managed to build master branch : > https://github.com/libfuse/libfuse I just had to remove "assert(... -oauto_unmount ...)" from : test/test_setattr.c test/test_write_cache.c From owner-freebsd-fs@freebsd.org Fri Aug 11 15:02:39 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 32EBDDD482F for ; Fri, 11 Aug 2017 15:02:39 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout03.t-online.de (mailout03.t-online.de [194.25.134.81]) (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 D02B575C97 for ; Fri, 11 Aug 2017 15:02:38 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd25.aul.t-online.de (fwd25.aul.t-online.de [172.20.26.130]) by mailout03.t-online.de (Postfix) with SMTP id 4593142B08F9; Fri, 11 Aug 2017 17:02:30 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (VUdktmZE8hWdCAKU1-5Hmu3GoGOXbxwzFzcByxSWtz9TrBNzx60LjEKBRcYW4F-wgG@[84.154.108.129]) by fwd25.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dgBSC-2c3r4i0; Fri, 11 Aug 2017 17:02:24 +0200 Subject: Re: State of FUSE on FreeBSD To: Ben RUBSON , Freebsd fs References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> <8EFD18D4-BD4E-4A30-A89E-129419EBC374@gmail.com> From: Stefan Esser Message-ID: Date: Fri, 11 Aug 2017 17:02:23 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <8EFD18D4-BD4E-4A30-A89E-129419EBC374@gmail.com> Content-Language: de-DE X-ID: VUdktmZE8hWdCAKU1-5Hmu3GoGOXbxwzFzcByxSWtz9TrBNzx60LjEKBRcYW4F-wgG X-TOI-MSGID: b5b627bc-a70c-41b5-a0cd-a81e2dddc15d Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 15:02:39 -0000 Am 11.08.17 um 16:31 schrieb Ben RUBSON: > >> On 11 Aug 2017, at 16:22, Ben RUBSON wrote: >> >> I managed to build master branch : >> https://github.com/libfuse/libfuse > > I just had to remove "assert(... -oauto_unmount ...)" from : > test/test_setattr.c > test/test_write_cache.c I have modified the existing port to build the new libfuse, see attached file (to be unpacked in /usr/ports). I tried "example/hello -d /mnt" and "example/hello_11 -d /mnt". While "hello" fails, "hello_ll" seems to work, but I get the following output from "df": $ df /mnt Filesystem 1K-blocks Used Avail Capacity Mounted on df: File system /mnt does not have a block size, assuming 512. /dev/fuse 0 0 0 100% /mnt Unmounting /mnt works as expected. Running the tests results in: $ py.test-3.6 test ======================================= test session starts ======================================= platform freebsd12 -- Python 3.6.2, pytest-3.2.0, py-1.4.34, pluggy-0.4.0 -- /usr/local/bin/python3.6 cachedir: test/.cache rootdir: libfuse-50d9158/test, inifile: pytest.ini collected 24 items test/test_ctests.py::test_write_cache[False] PASSED test/test_ctests.py::test_write_cache[True] FAILED ===================================== short test summary info ===================================== FAIL test/test_ctests.py::test_write_cache[True] ============================================ FAILURES ============================================= _____________________________________ test_write_cache[True] ______________________________________ Traceback (most recent call last): File "libfuse-50d9158/test/test_ctests.py", line 31, in test_write_cache subprocess.check_call(cmdline) File "/usr/local/lib/python3.6/subprocess.py", line 291, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['libfuse-50d9158/test/../test/test_write_cache', '/tmp/pytest-of-root/pytest-8/test_write_cache_True_0', '-owriteback_cache']' died with . -------------------------------------- Captured stderr call --------------------------------------- Assertion failed: (conn->capable & FUSE_CAP_WRITEBACK_CACHE), function tfs_init, file test_write_cache.c, line 56. !!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! =============================== 1 failed, 1 passed in 61.28 seconds =============================== Regards, STefan From owner-freebsd-fs@freebsd.org Fri Aug 11 15:09:20 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 669B5DD4CFC for ; Fri, 11 Aug 2017 15:09:20 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 352FF75E3A; Fri, 11 Aug 2017 15:09:19 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5388D20CB4; Fri, 11 Aug 2017 11:09:18 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 11:09:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=KpJXjGufQv+t+I8QcIh+N2LxMtzEsSTAfcliJh7VuI8=; b=epCgW98/ zbdqqMRr7r1Id3J3Fsftno6kuibXdjtpAWfTzruhLlgk9djEY97voSdBL5IdtpWd 6ZKmDsBPSCTSqAzoVGYv7myDTtKJ9TKAkfQ5PfAOXPM/FFjGbC2VXnS/XDYP6oUJ oMwq923oB2JYI3wYD6LVEmB+p8IyQ2pF+76nyKt/7/LXvf0KAImiPKqTh9RoE7vd nLtESknKotIMfKoBmB1y3N8xxfvG5Bd6RNcFSJLFB73jLdpTtLlLLiH0YB1vTM3j 7JmGgegTj5L6F8Ps4QHeafYbEsXPBUtp6fXt5vgHBuW5T57JKD/+pxgyvWE4ZeoK LDILcgmDV5zF3Q== X-ME-Sender: X-Sasl-enc: nhT4hBm97CJhLS9NjKf5H+1rc3mG7uVy1vf3+bDFI8Id 1502464158 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 0DA127F9BB; Fri, 11 Aug 2017 11:09:18 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 09DEF110; Fri, 11 Aug 2017 15:09:17 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 900E1102E4A; Fri, 11 Aug 2017 17:09:15 +0200 (CEST) From: Nikolaus Rath To: Ben RUBSON , Stefan Esser , freebsd-fs@freebsd.org Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: Ben RUBSON , Stefan Esser , freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 17:09:15 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 16:22:46 +0200") Message-ID: <87lgmqdtus.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 15:09:20 -0000 On Aug 11 2017, Ben RUBSON wrote: >> Nope, same problem here: >>=20 >> [root@ ~/libfuse/build]# example/hello >> error: no mountpoint specified >> [root@ ~/libfuse/build]# example/hello /mnt >> mount_fusefs: >> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >> on /mnt: No such file or directory >> fuse: failed to mount file system: No error: 0 > > I managed to build master branch : > https://github.com/libfuse/libfuse > > Following instructions in README.md. > > Log is here, with the tests : > https://benrubson.github.io/fusebuild.log Ok, that's great. If I had that result, I could work on the remaining issues. Unfortunately, all I get is the above error. Do you have any idea what could be different for me? As far as I can remember, I downloaded the image from https://download.freebsd.org/ftp/snapshots/VM-IMAGES/12.0-CURRENT/amd64/Lat= est/FreeBSD-12.0-CURRENT-amd64.qcow2.xz, did a number of 'pkg install ' runs and loaded the fuse kernel module. That's it. > And here is the example program you try to run : > # ./example/hello /mnt > # mount | grep mnt > Not surprising as it fails in tests. > > # ./example/hello_ll /mnt > # mount | grep mnt > /dev/fuse on /mnt (fusefs, local, synchronous) root@ ~/libfuse/build]# example/hello_ll /mnt mount_fusefs: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ on /mnt= : No such file or directory fuse: failed to mount file system: No error: 0 Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 15:10:36 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06525DD4E0B for ; Fri, 11 Aug 2017 15:10:36 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C83CF75EED; Fri, 11 Aug 2017 15:10:35 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5A37620D45; Fri, 11 Aug 2017 11:10:34 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 11:10:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=5nVraUW7lgC3zsPGy31LQLJzKM9LcAeaoo9rdA92RAo=; b=TviPkZxL fTI84wlKFt4C/jmPqfIdW9/3KTqUi8bFRx4Jpgp602W22q9S844ET1VycTEjXWsn u9G7ltFGdVoOoRJI37EUJ9HYOrdOOq2S23gKCvoIqxEBYt9wVH+29J0vTJ4xtpX1 hoizkO7L1u9OENWBY8AW1aL8LKx+q5n0Mu9pMpPuu8R29RgM0D/T6mILisfmj8df DkPaRrhqaT0+m4iVoa9tIkXUNfrE4nZ+BJDT8DnkzTnxayZUGLkDgAYtkUeeAJA3 Zq3MtuC1cG8F5ZeZG2mtyWAD6c0aVzA5l3GlwK2e58Uk4yfbPxiWJZGKbqGZl+hk pnrKNqm48UM69Q== X-ME-Sender: X-Sasl-enc: KSe8sgatRBsOXoQGCcIoK18fxWZIH7o53fQtZavgwdtZ 1502464234 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 19B55240A4; Fri, 11 Aug 2017 11:10:34 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 448BE110; Fri, 11 Aug 2017 15:10:33 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id DB107102E4A; Fri, 11 Aug 2017 17:10:31 +0200 (CEST) From: Nikolaus Rath To: Stefan Esser Cc: Ben RUBSON , Freebsd fs Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> <8EFD18D4-BD4E-4A30-A89E-129419EBC374@gmail.com> Mail-Copies-To: never Mail-Followup-To: Stefan Esser , Ben RUBSON , Freebsd fs Date: Fri, 11 Aug 2017 17:10:31 +0200 In-Reply-To: (Stefan Esser's message of "Fri, 11 Aug 2017 17:02:23 +0200") Message-ID: <87h8xedtso.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 15:10:36 -0000 On Aug 11 2017, Stefan Esser wrote: > Am 11.08.17 um 16:31 schrieb Ben RUBSON: >>=20 >>> On 11 Aug 2017, at 16:22, Ben RUBSON wrote: >>> >>> I managed to build master branch : >>> https://github.com/libfuse/libfuse >>=20 >> I just had to remove "assert(... -oauto_unmount ...)" from : >> test/test_setattr.c >> test/test_write_cache.c > > I have modified the existing port to build the new libfuse, see attached > file (to be unpacked in /usr/ports). I think you forgot to attach the file. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 15:17:58 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFB5BDD56BF for ; Fri, 11 Aug 2017 15:17:58 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (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 93426764F7 for ; Fri, 11 Aug 2017 15:17:58 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22d.google.com with SMTP id m85so44166834wma.0 for ; Fri, 11 Aug 2017 08:17:58 -0700 (PDT) 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=rKQCCI4D1X6kWHcTvG7x1uSiQwtT3eSTxL4r44bR6Tg=; b=b9TPupf6vcM5U5AdKpxNaoSjY2rbyzoDKhcGc1nL74sPENS6djyj65jdu6ltg6eUN9 eu6E+JstEUEZWdUAbBXjUogAbeE198g+oj1QT8bj4lhKDmI79XIQmOBZyjMSU2ACkpPo IpNNxELIHLrGQ/Y7YSL7NCJ6Pz5bIEVNYiJuokjgCnBnAYkfQEEd5FD/6tIv0auK0xdY oNHGtPwa9chDxCF6oriuwRst2jB5NGAXoLMyu7mnGRVs7yBZrggIzW+KzizfQgtaoMvh 6ptg68Fh7kWewMUFMNX1bIFKvrBQK5P6jz4zJLvyeloMVKHQKB4lvE6kaKGlnBORQuqq Ixhw== 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=rKQCCI4D1X6kWHcTvG7x1uSiQwtT3eSTxL4r44bR6Tg=; b=OGQHIu4faYJ9eaC9bBn7rY1tOGz9/SIIv+iX5GeMaktnn0OH8IHjQ0aplwKEX5h7C5 d64zh8RCWAWfMYBPqYIzTuL6FsOnWJ0DRHT6WcVycFgA9lKTTNI3NYX8ct2lgXF2O49G /DsE6Tj9CMkYymkNEAcYUhT/TXW8FpfUG6pQH4gQXQLibhcv+r6YpS4ahjTriMjwZtRO 2kebZ/7fX4XLn6hTOU6bTwSkJnZRyZPCYg+hTLk+N56dP6xcpJ5Fqze0W2YMzTpPp+Af +kR1h0XnLmhUUdXNYdgc/IOw+5K1PjpoZcsPmUb0VdBzBRDKhIaYOac/au9tZEGgN3z5 n9Hg== X-Gm-Message-State: AHYfb5hH9djDZfcev4sjugqGtbOn71oWeMpGPbkbRlll8KWepa6lz+3x bNFgwgwCjLijsGNiroI= X-Received: by 10.28.14.149 with SMTP id 143mr9423036wmo.102.1502464676698; Fri, 11 Aug 2017 08:17:56 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id e1sm1382218wrc.91.2017.08.11.08.17.55 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 11 Aug 2017 08:17:56 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: State of FUSE on FreeBSD From: Ben RUBSON In-Reply-To: <87lgmqdtus.fsf@vostro.rath.org> Date: Fri, 11 Aug 2017 17:17:55 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> <87lgmqdtus.fsf@vostro.rath.org> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 15:17:59 -0000 > On 11 Aug 2017, at 17:09, Nikolaus Rath wrote: >=20 > On Aug 11 2017, Ben RUBSON wrote: >>> Nope, same problem here: >>>=20 >>> [root@ ~/libfuse/build]# example/hello >>> error: no mountpoint specified >>> [root@ ~/libfuse/build]# example/hello /mnt >>> mount_fusefs: >>> = ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>> on /mnt: No such file or directory >>> fuse: failed to mount file system: No error: 0 >>=20 >> I managed to build master branch : >> https://github.com/libfuse/libfuse >>=20 >> Following instructions in README.md. >>=20 >> Log is here, with the tests : >> https://benrubson.github.io/fusebuild.log >=20 > Ok, that's great. If I had that result, I could work on the remaining > issues. >=20 > Unfortunately, all I get is the above error. Do you have any idea what > could be different for me? >=20 > As far as I can remember, I downloaded the image from > = https://download.freebsd.org/ftp/snapshots/VM-IMAGES/12.0-CURRENT/amd64/La= test/FreeBSD-12.0-CURRENT-amd64.qcow2.xz, > did a number of 'pkg install ' runs and loaded the fuse kernel > module. That's it. I would rather use a STABLE image, last version is 11.1 : = https://download.freebsd.org/ftp/snapshots/VM-IMAGES/11.1-STABLE/amd64/Lat= est/ Ben From owner-freebsd-fs@freebsd.org Fri Aug 11 15:22:26 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C77FFDD5BCC for ; Fri, 11 Aug 2017 15:22:26 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout11.t-online.de (mailout11.t-online.de [194.25.134.85]) (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 7637C76888 for ; Fri, 11 Aug 2017 15:22:25 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd29.aul.t-online.de (fwd29.aul.t-online.de [172.20.26.134]) by mailout11.t-online.de (Postfix) with SMTP id 38B6A4249D75 for ; Fri, 11 Aug 2017 17:22:18 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (Xjg21cZCYh-4EBh7r1iu+IQ1wz3-b3ngalA7NZ8OgbnTHstQkNtC-QysC2I7zzSZC9@[84.154.108.129]) by fwd29.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dgBlQ-0Qczdg0; Fri, 11 Aug 2017 17:22:16 +0200 Subject: Re: State of FUSE on FreeBSD To: Freebsd fs References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> <8EFD18D4-BD4E-4A30-A89E-129419EBC374@gmail.com> <87h8xedtso.fsf@vostro.rath.org> From: Stefan Esser Message-ID: <000f1e33-55a4-451d-3863-2a964534c362@freebsd.org> Date: Fri, 11 Aug 2017 17:22:15 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <87h8xedtso.fsf@vostro.rath.org> Content-Language: de-DE X-ID: Xjg21cZCYh-4EBh7r1iu+IQ1wz3-b3ngalA7NZ8OgbnTHstQkNtC-QysC2I7zzSZC9 X-TOI-MSGID: 0d69672a-b4fc-4d9c-be61-0c02649f57f0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 15:22:26 -0000 Am 11.08.17 um 17:10 schrieb Nikolaus Rath: > On Aug 11 2017, Stefan Esser wrote: >> Am 11.08.17 um 16:31 schrieb Ben RUBSON: >>> >>>> On 11 Aug 2017, at 16:22, Ben RUBSON wrote: >>>> >>>> I managed to build master branch : >>>> https://github.com/libfuse/libfuse >>> >>> I just had to remove "assert(... -oauto_unmount ...)" from : >>> test/test_setattr.c >>> test/test_write_cache.c >> >> I have modified the existing port to build the new libfuse, see attached >> file (to be unpacked in /usr/ports). > > I think you forgot to attach the file. No, it is stripped by the mail list software and I seem to have forgotten to send you a CC ... But you should receive the one attached to this mail ... ;-) Regards, STefan From owner-freebsd-fs@freebsd.org Fri Aug 11 15:56:32 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D401BDD7A92 for ; Fri, 11 Aug 2017 15:56:32 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A2A1D779D1 for ; Fri, 11 Aug 2017 15:56:31 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 1226120B1D; Fri, 11 Aug 2017 11:56:31 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 11:56:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=1NEcEYp4V8qG+pJF1rCKgP89ehTKX/ewla8tuV2XHA8=; b=ftGkI2/B HJ++KChHpEMbdGT3pLHMLmMMxjNhL80Ky+6AgdWu7/Q3oYWUleHwG5YDuVqCyenD fpYI9aHa90UlEw/gOLWCk1cL5v7zEIZrFIbBDTQ64oSaMOpg1ZDY4USJovOsIfdl rph0por91L3VNCJHH6OfDwz1m5JjnUEQb7EKgHPLd7fZ454EgwZU38uEfE5Yao2f lb19oA4nHWWRJ06Fz/nC2Bjn0B52UFe8e9CPuwKaPIpJ5eN8G7lJwUbUACbdOazr dzQDhWdI+UTPQdSz667zMQnrVdar9EovyZS7KbLSTtVR4jZseo+RnIL9VKsJFjkY vT2/D6ruPV3GLQ== X-ME-Sender: X-Sasl-enc: YFJnOM6nB+68p7zzzPnotNrM8732d5hB/jWVL1s+Wkqu 1502466990 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id C01F77E4EA; Fri, 11 Aug 2017 11:56:30 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id E8FB8110; Fri, 11 Aug 2017 15:56:29 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 72D99102E4A; Fri, 11 Aug 2017 17:56:28 +0200 (CEST) From: Nikolaus Rath To: Ben RUBSON Cc: Freebsd fs Subject: Re: State of FUSE on FreeBSD References: <87y3r0ankb.fsf@vostro.rath.org> <87efsifpiu.fsf@vostro.rath.org> <47A5197B-6A83-4819-A6EE-E56ABD31C4B3@gmail.com> <87bmnmfouj.fsf@vostro.rath.org> <8760dufiu2.fsf@vostro.rath.org> <87r2widwec.fsf@vostro.rath.org> <87lgmqdtus.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: Ben RUBSON , Freebsd fs Date: Fri, 11 Aug 2017 17:56:28 +0200 In-Reply-To: (Ben RUBSON's message of "Fri, 11 Aug 2017 17:17:55 +0200") Message-ID: <87bmnmdro3.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 15:56:32 -0000 On Aug 11 2017, Ben RUBSON wrote: >> On 11 Aug 2017, at 17:09, Nikolaus Rath wrote: >>=20 >> On Aug 11 2017, Ben RUBSON wrote: >>>> Nope, same problem here: >>>>=20 >>>> [root@ ~/libfuse/build]# example/hello >>>> error: no mountpoint specified >>>> [root@ ~/libfuse/build]# example/hello /mnt >>>> mount_fusefs: >>>> ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ= ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ >>>> on /mnt: No such file or directory >>>> fuse: failed to mount file system: No error: 0 > > I would rather use a STABLE image, last version is 11.1 : > https://download.freebsd.org/ftp/snapshots/VM-IMAGES/11.1-STABLE/amd64/La= test/ Success! Now I'm getting something more helpful: [root@ ~/libfuse/build]# example/hello -f /mnt fuse: error: filesystem requested capabilites that are not supported by ker= nel, aborting. >From here on I can take it again. I hope someone else (tm) will look into the issues with the development release. Best, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 18:46:12 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C5B5D9307E for ; Fri, 11 Aug 2017 18:46:12 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 002E182C4C for ; Fri, 11 Aug 2017 18:46:11 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 9E09720D8C for ; Fri, 11 Aug 2017 14:46:10 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 14:46:10 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=RyYooAbUtZhPQYwJR3 DMVwByWDJaZwsaRs17859sDy0=; b=FIfkij9jTTjvkMflgOetAhPz7QFwa93gfm GY3Idbig0lzADg3uGaAvOlCfKVu+9VBtytC9QRbvscp6vWTRvYoewxh7WfFgU2El M9/eGFupDcNNCdaDAnV2H1vQ7V1M2ukmYD7M76N0R6myaflwtsHpyNh6iP3s8XnT Die3wsmMOLXPS/50MbdaObK4hR/pq6XZptkdP9zIcSPkdKL2M4E5uAsGsJOzuFsc fKahPWPCdINa3tMDukUqtKUss3egPbIM9nW4jhggg8RSc0XEf/pj5Kpo64bEelJ+ 0nNP+9ALrMozGmjq0L4a3/73rohGC5QC/saZFrP/cOaXnCuKL+lw== X-ME-Sender: X-Sasl-enc: MP1kA1F59ow42ggrsg5olbPQmZch3AwZ98MEF/fo2QqJ 1502477170 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 6AF15244B4 for ; Fri, 11 Aug 2017 14:46:10 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id 74602D9 for ; Fri, 11 Aug 2017 18:46:09 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id E312F102E4A; Fri, 11 Aug 2017 20:46:07 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Status of FUSE in FreeBSD kernel Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 20:46:07 +0200 Message-ID: <878tiqdjtc.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 18:46:12 -0000 Hello, Is there some resource that gives an overview of the features supported by the FUSE kernel module in FreeBSD? For example, I am wondering if the EINVAL error that I'm getting when sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error on my side, or because the FreeBSD kernel just doesn't support it. I expect to encounter the same question for a number of other functions, e.g. the other FUSE_NOTIFY_* requests. Thanks, -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 18:58:11 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 33792D93EE9 for ; Fri, 11 Aug 2017 18:58:11 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 063BB8346E for ; Fri, 11 Aug 2017 18:58:10 +0000 (UTC) (envelope-from Nikolaus@rath.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D700F20D7A for ; Fri, 11 Aug 2017 14:58:09 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 11 Aug 2017 14:58:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=slQmnrGrQsRn6OJUuhoTVNzkYr9QE3n6a8aQVn1h3eI=; b=eJdHTK1G p0Agp/L8/VOTMf7fSqJrXTTQF2y2CC6sM8PRF3Ws8Oa2MFXXld6+joKAwu5o6cn/ R1GEqI5TwVRKf2XiYylTQQ+Scg64h2VGBAGP39QBl1mEf57LqKhvsuHLPzprIpfM Q/Beiscx/FoZaRW6Xxynaev4K5etsMtRgqqNIr+MPtNWt4mGGkbwdY2acDRuHBkF FzHr25imIcSqjiWyhFfWALEcX2VIAv4zD1xH6YLDeQIOtjaJDijGtBxPaKzfaqpc cFPp6TDtI9pc07mNny+i+OrRJgtfwuZ16sft3WnecLEWzSBQMKIyDT/BwAEvjgHm pHAhuzQA3CfBeQ== X-ME-Sender: X-Sasl-enc: MF6wgt6aW1wPT+76o5dnLeTa9L2aXO8AX6R5oDRsS/wT 1502477889 Received: from ebox.rath.org (ebox.rath.org [45.79.69.51]) by mail.messagingengine.com (Postfix) with ESMTPA id 965B524442 for ; Fri, 11 Aug 2017 14:58:09 -0400 (EDT) Received: from vostro.rath.org (vostro [192.168.12.4]) by ebox.rath.org (Postfix) with ESMTPS id BCC90D9 for ; Fri, 11 Aug 2017 18:58:08 +0000 (UTC) Received: by vostro.rath.org (Postfix, from userid 1000) id 44CBA102E4A; Fri, 11 Aug 2017 20:58:07 +0200 (CEST) From: Nikolaus Rath To: freebsd-fs@freebsd.org Subject: Re: Status of FUSE in FreeBSD kernel References: <878tiqdjtc.fsf@vostro.rath.org> Mail-Copies-To: never Mail-Followup-To: freebsd-fs@freebsd.org Date: Fri, 11 Aug 2017 20:58:07 +0200 In-Reply-To: <878tiqdjtc.fsf@vostro.rath.org> (Nikolaus Rath's message of "Fri, 11 Aug 2017 20:46:07 +0200") Message-ID: <8760dudj9c.fsf@vostro.rath.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 18:58:11 -0000 On Aug 11 2017, Nikolaus Rath wrote: > Hello, > > Is there some resource that gives an overview of the features supported > by the FUSE kernel module in FreeBSD? > > For example, I am wondering if the EINVAL error that I'm getting when > sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error > on my side, or because the FreeBSD kernel just doesn't support it. > > I expect to encounter the same question for a number of other functions, > e.g. the other FUSE_NOTIFY_* requests. Another example: calling 'mknod' or 'mkfifo' on a FUSE mountpoint doesn't seem to make it through to the filesystem, the kernel returns -EINVAL instead. Is that a problem with the filesystem, or not supported by the kernel? Thanks! -Nikolaus --=20 GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =C2=BBTime flies like an arrow, fruit flies like a Banana.=C2= =AB From owner-freebsd-fs@freebsd.org Fri Aug 11 21:26:22 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2AA9ADC7579 for ; Fri, 11 Aug 2017 21:26: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 mx1.freebsd.org (Postfix) with ESMTPS id 1927263FCB for ; Fri, 11 Aug 2017 21:26:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7BLQLs1021063 for ; Fri, 11 Aug 2017 21:26:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218101] [fuse] [request] support entry_timeout / attr_timeout Date: Fri, 11 Aug 2017 21:26:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ben.rubson@gmail.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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 21:26:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218101 --- Comment #1 from Ben RUBSON --- Here is a test case for this request report : # Create a Fuse EncFS in reverse mode (will give an encrypted view of the p= lain folder) : plain=3D/tmp/encfs_test/plain ciphr=3D/tmp/encfs_test/ciphr mkdir -p $plain $ciphr encfs --extpass=3D"echo test" --standard $plain $ciphr --reverse # Update a file in the plain folder while [ 1 ]; do echo >>$plain/file ; sleep 0.5; done # Monitor the files in the encrypted view : while [ 1 ]; do clear; stat $ciphr/*; sleep 0.5; done As you can see, the timestamps correctly get updated, but not the sizes. It's then dangerous because if you open the encrypted file (using dd for example, dd if=3D$ciphr/... of=3D/dev/null), it will then be truncated (!) to the size being displayed by stat, whereas it was in reality much bigger, as its plain version was growing. I found fuse sysctls, some are cache related, but no benefit. Adding "-o attr_timeout=3D0 -o entry_timeout=3D0" to the encfs command in Linux makes this to work. Thank you ! Ben --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 11 21:43:27 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96A79DC8ADC for ; Fri, 11 Aug 2017 21:43:27 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670042.outbound.protection.outlook.com [40.107.67.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E0AE6579E for ; Fri, 11 Aug 2017 21:43:26 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0192.CANPRD01.PROD.OUTLOOK.COM (10.165.218.136) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1320.16; Fri, 11 Aug 2017 21:43:24 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.1320.021; Fri, 11 Aug 2017 21:43:24 +0000 From: Rick Macklem To: Nikolaus Rath , "freebsd-fs@freebsd.org" Subject: Re: Status of FUSE in FreeBSD kernel Thread-Topic: Status of FUSE in FreeBSD kernel Thread-Index: AQHTEtIeNFWYkFpI30ijVE+adsaJHKJ/r9rr Date: Fri, 11 Aug 2017 21:43:24 +0000 Message-ID: References: <878tiqdjtc.fsf@vostro.rath.org> In-Reply-To: <878tiqdjtc.fsf@vostro.rath.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTXPR01MB0192; 6:eLaqQV3omCNW++o2W9DCyJh77BzWD4Zc6uMRg4ENtmKkEpFoSwIeH5e5KIgvUH12Pez++k1aUHdC6Ir8MEZ49Gfh5Ux1qYZ5TttbeQnERu2wjDHcxVyg4Ssk5V1pQtZSl2JRxPxjkhuficAF4TSnlIaaAsfOYlxnpF2cSCrZ5f1xhpFtCu4E7t6wyHhDM3JEKSAJmWg+b+QAAcM92DqeKj1CqI2L0fu5e8iItDF5P7QMvRxCMMahSQXaug9CEQkaoZqoU2KFXe7is1BbObTnNcsYLyPUibQq4Hs1s0cCicFJjkHdXFbHhw59PPj0w8UXkmILbcQjO1GGt1K26rNK3A==; 5:scPOBtJAhosvLZdnhHjvLZ33iNmnzk+3ICBYWKonxoP+UlLmw1UEvBAPsTfgt0EbklUsfeHKyGd2SWYpbAyBCpDBrYUM1td4+LsEAT3p/eaJDQTusQxuS5EF/kARZoxmn7Va8bQH3pKA4bqalPgCbw==; 24:n7+VKsOdSITh2FpDUEySFWwKm3xnMlr2JnKeYs4hlDQWK9qo0ArYgQ4q+K9IAU5WwUbps9vJNoXjEqt331okjo3GNoQSiGdziMEDCXAqUdQ=; 7:yJzuBLojkWIyoFsbANttezkI01YQQWu0KMY1NePRllIYD51HPfYg1BGYnXREbcaytBoXblmhy/gy8Os+DQeXvPiD/VhrcnJ1ISR/xOwKsMHm52bSZ0wtNjvAk+DXK5NZpqIPmVWkz1YD4feFqz8n2JBRlBN9O/uZDz5Pt4An+9nllJUzxKArZMl2YikjQPdyOqS4EiNNn7ySD23wUegakucx1Vn8DLVNDJQVw79aTtM= x-ms-exchange-antispam-srfa-diagnostics: SSOS; x-ms-office365-filtering-correlation-id: ec66c85d-a8f6-4c38-43a4-08d4e101fe7d x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:YTXPR01MB0192; x-ms-traffictypediagnostic: YTXPR01MB0192: x-exchange-antispam-report-test: UriScan:(75325880899374); x-microsoft-antispam-prvs: x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(93006095)(93001095)(100000703101)(100105400095)(3002001)(10201501046)(6041248)(20161123558100)(20161123560025)(20161123555025)(20161123564025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:YTXPR01MB0192; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:YTXPR01MB0192; x-forefront-prvs: 03965EFC76 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(377454003)(189002)(86362001)(2950100002)(68736007)(3660700001)(2906002)(105586002)(229853002)(6506006)(77096006)(102836003)(5660300001)(2501003)(7696004)(74316002)(2900100001)(3280700002)(53936002)(6246003)(33656002)(14454004)(189998001)(55016002)(6306002)(305945005)(25786009)(53546010)(478600001)(966005)(74482002)(8936002)(8676002)(76176999)(54356999)(9686003)(101416001)(81166006)(106356001)(97736004)(6436002)(81156014)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0192; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Aug 2017 21:43:24.5984 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0192 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 21:43:27 -0000 This is open source, which means the answer is in the sources... fuse_kernel.h claims the interface is version 7.8, if that helps. rick ________________________________________ From: owner-freebsd-fs@freebsd.org on behalf= of Nikolaus Rath Sent: Friday, August 11, 2017 2:46:07 PM To: freebsd-fs@freebsd.org Subject: Status of FUSE in FreeBSD kernel Hello, Is there some resource that gives an overview of the features supported by the FUSE kernel module in FreeBSD? For example, I am wondering if the EINVAL error that I'm getting when sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error on my side, or because the FreeBSD kernel just doesn't support it. I expect to encounter the same question for a number of other functions, e.g. the other FUSE_NOTIFY_* requests. Thanks, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F =BBTime flies like an arrow, fruit flies like a Banana.=AB _______________________________________________ freebsd-fs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Fri Aug 11 22:17:25 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F93EDCAF45 for ; Fri, 11 Aug 2017 22:17:25 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-pf0-f180.google.com (mail-pf0-f180.google.com [209.85.192.180]) (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 4ABE96703A for ; Fri, 11 Aug 2017 22:17:25 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-pf0-f180.google.com with SMTP id t86so20714757pfe.2 for ; Fri, 11 Aug 2017 15:17:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=xcbqJ/szMcGiPbrAKymAPrTVRtdeikCyMWPWYwZHmsw=; b=cnJAtT5D6uGbmX1zmhKKmeGzciRKqCw5xvoRkean0KEMVMtnrB96Zf5OgsfZeoHAA+ chr1GpJSylUiBaIIYLX7iJXTO3QN9JkcVj5YXBmT/JsqoDzZYEPoQ2Er1w9Guw9sZYdh 342IWGFyQAiiIbZ2mB9Ai0/n3acmXwLdLVPUQVD0Z2wpoDpVeeFk7qRFfnVif9GTm3LJ 8vAhYC3d0rk2Ma25vcu9h5ANBcoe1TfqAbUIWvykFpullccjEICAiTMLAO0xaWLl56sT rJf9moM2eUG4cppunDsNPbnzQvFoggdatqkbrFLShin5GYwqu63SkZWvTjSijW4bn2RT 8BfA== X-Gm-Message-State: AHYfb5iq7qqxUsD6VmS3vcPm6jJLLdiCIKyd5UKpGXMWfb+BcoT2qFHG bXMnkgKjIDaNW3A/Zss= X-Received: by 10.99.109.66 with SMTP id i63mr4199292pgc.187.1502483553203; Fri, 11 Aug 2017 13:32:33 -0700 (PDT) Received: from mail-pg0-f54.google.com (mail-pg0-f54.google.com. [74.125.83.54]) by smtp.gmail.com with ESMTPSA id w8sm5572594pgc.1.2017.08.11.13.32.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Aug 2017 13:32:32 -0700 (PDT) Received: by mail-pg0-f54.google.com with SMTP id y129so19538203pgy.4 for ; Fri, 11 Aug 2017 13:32:32 -0700 (PDT) X-Received: by 10.101.90.7 with SMTP id y7mr16181502pgs.29.1502483552034; Fri, 11 Aug 2017 13:32:32 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.100.150.15 with HTTP; Fri, 11 Aug 2017 13:32:31 -0700 (PDT) In-Reply-To: <8760dudj9c.fsf@vostro.rath.org> References: <878tiqdjtc.fsf@vostro.rath.org> <8760dudj9c.fsf@vostro.rath.org> From: Conrad Meyer Date: Fri, 11 Aug 2017 13:32:31 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Status of FUSE in FreeBSD kernel To: freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 22:17:25 -0000 Hi Nikolaus, These questions are probably best answered by reading the source. I grepped the FreeBSD tree for FUSE_NOTIFY_INVAL_INODE and did not see it. Looking around, I don't think we have any of the libfuse notify support. As far as mknod/mkfifo, that should work. EINVAL can come from bogus dev value for a CHR/BLK mknod or an unrecognized mode type. Best, Conrad On Fri, Aug 11, 2017 at 11:58 AM, Nikolaus Rath wrote: > On Aug 11 2017, Nikolaus Rath wrote: >> Is there some resource that gives an overview of the features supported >> by the FUSE kernel module in FreeBSD? >> >> For example, I am wondering if the EINVAL error that I'm getting when >> sending FUSE_NOTIFY_INVAL_INODE requests to FUSE is because of an error >> on my side, or because the FreeBSD kernel just doesn't support it. >> >> I expect to encounter the same question for a number of other functions, >> e.g. the other FUSE_NOTIFY_* requests. > > Another example: calling 'mknod' or 'mkfifo' on a FUSE mountpoint > doesn't seem to make it through to the filesystem, the kernel returns > -EINVAL instead. > > Is that a problem with the filesystem, or not supported by the kernel? > > Thanks! > -Nikolaus From owner-freebsd-fs@freebsd.org Sat Aug 12 03:32:48 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D40CDDD7A9 for ; Sat, 12 Aug 2017 03:32:48 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254:10::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F039A70A8D for ; Sat, 12 Aug 2017 03:32:47 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]) (authenticated bits=0) by hydra.pix.net (8.16.0.19/8.15.2) with ESMTPSA id v7C3WaG0067989 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 11 Aug 2017 23:32:44 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Received: from magrathea.distal.com (magrathea.distal.com [IPv6:2001:470:e24c:200:ea06:88ff:feca:960e]) (authenticated bits=0) by mail.distal.com (8.15.2/8.15.2) with ESMTPSA id v7C3WY7S085338 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 11 Aug 2017 23:32:35 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Content-Type: multipart/signed; boundary="Apple-Mail=_21154BD9-E6CD-41C7-A7A7-9C57D2804300"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS: Device names in a raidz1 pool after changing controllers From: Chris Ross In-Reply-To: <20170811062459.GA30374@hell.ukr.net> Date: Fri, 11 Aug 2017 23:32:24 -0400 Cc: freebsd-fs@freebsd.org Message-Id: References: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com> <20170811062459.GA30374@hell.ukr.net> To: Vitalij Satanivskij X-Mailer: Apple Mail (2.3124) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]); Fri, 11 Aug 2017 23:32:35 -0400 (EDT) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 03:32:48 -0000 --Apple-Mail=_21154BD9-E6CD-41C7-A7A7-9C57D2804300 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Aug 11, 2017, at 02:24 , Vitalij Satanivskij wrote: >=20 >=20 > Hello >=20 > for disabling diskid > kern.geom.label.disk_ident.enable=3D"0" >=20 > same for gptid > kern.geom.label.gptid.enable=3D"0" >=20 > same for gpt label > kern.geom.label.gpt.enable=3D"0" >=20 > In /boot/loader.conf >=20 > Just choose how you prefer >=20 > And if tank isn't boot pool you can export and import with -d option = to choose which naming of devices to use (eg /dev/gpt /dev/diskid etc) Okay. I thought I would try this last bit. However, only the first = two disks (still ada0 and ada1) list partitions in /dev/gpt, because I = just used the entirety of the other two disks I guess. And, only the = other two disks have shown up in /dev/diskid. (nb, later research shows = the other disks when I run =E2=80=9Cgpart list=E2=80=9D, but they have = =E2=80=9C(null)" labels, as do their one partitions) So, "import -d /dev/gpt=E2=80=9D doesn=E2=80=99t find anything = (because none of tank=E2=80=99s disks are there), and =E2=80=9Cimport -d = /dev/diskid=E2=80=9D finds the same as it configured automatically, with = ada1p4 and the two diskid=E2=80=99s. Only /dev/gptid does what you = describe above, where it lists all three by gptid, but I would prefer = not to do that atm. I was hoping to get =E2=80=9Cada1p4=E2=80=9D =E2=80=9Cd0p1=E2=80=9D = and =E2=80=9Cd1p1=E2=80=9D. If I ls /dev, I see: # ls -l /dev/ada* /dev/da* crw-r----- 1 root operator 0x5f Aug 11 01:20 /dev/ada0 crw-r----- 1 root operator 0x60 Aug 11 01:20 /dev/ada0p1 crw-r----- 1 root operator 0x61 Aug 11 01:20 /dev/ada0p2 crw-r----- 1 root operator 0x62 Aug 11 01:20 /dev/ada0p3 crw-r----- 1 root operator 0x64 Aug 11 01:20 /dev/ada1 crw-r----- 1 root operator 0x6b Aug 11 01:20 /dev/ada1p1 crw-r----- 1 root operator 0x6c Aug 11 01:20 /dev/ada1p2 crw-r----- 1 root operator 0x6d Aug 11 01:20 /dev/ada1p3 crw-r----- 1 root operator 0x6e Aug 11 01:20 /dev/ada1p4 crw-r----- 1 root operator 0x65 Aug 11 01:20 /dev/da0 crw-r----- 1 root operator 0x70 Aug 11 23:20 /dev/da0p1 crw-r----- 1 root operator 0x66 Aug 11 01:20 /dev/da1 crw-r----- 1 root operator 0x76 Aug 11 23:20 /dev/da1p1 So I=E2=80=99d think it would work, but, both =E2=80=9Czpool import=E2=80= =9D and =E2=80=9Czpool import -d /dev=E2=80=9D both show tank as: tank ONLINE raidz1-0 ONLINE ada1p4 ONLINE diskid/DISK-WOL240261932p1 ONLINE diskid/DISK-WOL240261922p1 ONLINE Let me know if there=E2=80=99s something else I can try. Otherwise, I = may just try putting gpt labels on the other partitions. But, I have = more controller swapping soon, so it=E2=80=99s mostly just informational = at the moment. Thanks=E2=80=A6 - Chris --Apple-Mail=_21154BD9-E6CD-41C7-A7A7-9C57D2804300 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJZjnbRAAoJEPFBDnXvoNg0eewP/35KuXJS5PekF8A+3OEWjTS5 8aZi2cnYf+RNCzMHtYrxwThq+zGsH23f42Q/JaME5Nx/l+f/n17ut6dzeZ5WuvZU 70Uhx3CyCGJ9EEVrKQbEKIdZ87fmnycd2ZDkkAi2J1Aff5IVydBFiTWQbcSQWCBg zDic4V5GaI4C9zJ6AjVcAf8SdtBBpDWIHZloSJaIEZzWh3VhdDL98MoJVTel53// AO+05eI6UFkpusU81tBNnSJBi1CJAibTzLt3RpjogBRLVeYRdZQYmC9D+weKQkIk fVEuFqVPP6nxDA6kegObMkIK+RKFdIBq3nH231mpf/+yYRNHTWtvEKQpCyMAwEmA AeCg9b9g9t/iycHA+JPuWq8rc8xNIqrfbctU+YJms4tKbVoYB9ZPQ2xpS9NGVrHB uWEN6fS4INvaCva3KWdAOcBNv5k0UECIj+lavdHKsxF3V0Ahej62M/tAmCLjBgtx f4iS2MZRZLSPPA8cUg1pyDVRLpZpMDMooSdowivJGEnAqX7kKpzybZLh35v9O8cO 2DqBytVwU961ayJGURqpWUuU8t5oyQz70HPlQO8YHjWPpum16LSpGu6snva4JJfx ztCtGbl2lUSOXoG4bp0HzzqQlxAO37qrvSGxq5rjv8Gu9wiSaCJs94AdJ0+GGbkP 00OZDxdAbQwNbgKrKSEz =njqq -----END PGP SIGNATURE----- --Apple-Mail=_21154BD9-E6CD-41C7-A7A7-9C57D2804300-- From owner-freebsd-fs@freebsd.org Sat Aug 12 07:25:19 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ED8FDC31A5 for ; Sat, 12 Aug 2017 07:25:19 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 B4AA477603 for ; Sat, 12 Aug 2017 07:25:18 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x241.google.com with SMTP id f38so3798508wrf.4 for ; Sat, 12 Aug 2017 00:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=z6FH3vgqqBdUsivWo6ppfqZVy2RqPvv2dnTSMLCZubk=; b=TDyLC4nP4Phasu3DSqsgzmrypTnPf2/IWOPq8NoFhnxmp9giEmTna8QjAlruqmMdEg /AqSLtLTqb/N9trBvh+mmIzXE/h92yLkTZkhM1hfoeDq0e3OB3cINI2Yb1Zj3MQbNmGq svife+i2pzByQUdwYIvjjWLKMSG5XoNRzgu07F1Tpt9K7cHwz1b7GT5jKDt9gvareJL4 Ta5zC2GG+89nL1TVYgl0FbbMivIfvn6ufBITe4EMOlwtYDLtbwdEx3u4Pt6nrw8Gue4p N/vq3IK2bIH+xLcL3hmUa3fPMOOEfQyTltmKa9eeuG/gbnNdI40RY3jXgNV8owkTPEJI 14KQ== 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:cc :content-transfer-encoding:message-id:references:to; bh=z6FH3vgqqBdUsivWo6ppfqZVy2RqPvv2dnTSMLCZubk=; b=oR5EPZD2vYjwW2cDW34NevNZaljOPJ9gF9gZb7bpUDSrPJtkWoy0K4dj3+/0qOALqt re0Ex7LGYz3EL6m8lEyxz446OXqTxQZ4noCoIdMwbTLKBeHXxl/VfdVNCiUVIS86GJFx DvpG8FtwNjRoZ2D8OyXKtwWxlvy04FJjzgTUaQ7fxtmjKW/uiOvC0F908YWYhqYzM9z/ O/7hNYGqYB5XlhEacS3wx1hMW9nisNwhgp1HRnyZz3spL8jxdZWdEJ9uw7dlwat0Lnqm TUBVA19DxHhUl24p017QM0vwT/tgnSGKXviJqSQeXKxV5VcvJeaWXiqPBo0YNkL0QCoA e5nQ== X-Gm-Message-State: AHYfb5j5cOMRTD2S+UpWpkziCH1Kg0K4rzbZghsKKe4HGc3FWxUm5ABW L+uo21ai74yziQ== X-Received: by 10.223.170.140 with SMTP id h12mr11961576wrc.79.1502522715646; Sat, 12 Aug 2017 00:25:15 -0700 (PDT) Received: from ben.home (LFbn-1-6951-179.w90-116.abo.wanadoo.fr. [90.116.132.179]) by smtp.gmail.com with ESMTPSA id c13sm3221508wrc.7.2017.08.12.00.25.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 12 Aug 2017 00:25:14 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS: Device names in a raidz1 pool after changing controllers From: Ben RUBSON In-Reply-To: Date: Sat, 12 Aug 2017 09:25:15 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <5562B8AA-5A76-4ECB-8224-CFE1A8CA954B@gmail.com> References: <6976A8FF-994C-48D3-99B1-2181CD15C94C@distal.com> <20170811062459.GA30374@hell.ukr.net> To: Chris Ross , Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 07:25:19 -0000 > On 12 Aug 2017, at 05:32, Chris Ross wrote: >=20 >=20 >> On Aug 11, 2017, at 02:24 , Vitalij Satanivskij = wrote: >>=20 >>=20 >> Hello >>=20 >> for disabling diskid >> kern.geom.label.disk_ident.enable=3D"0" >>=20 >> same for gptid >> kern.geom.label.gptid.enable=3D"0" >>=20 >> same for gpt label >> kern.geom.label.gpt.enable=3D"0" >>=20 >> In /boot/loader.conf >>=20 >> Just choose how you prefer >>=20 >> And if tank isn't boot pool you can export and import with -d option = to choose which naming of devices to use (eg /dev/gpt /dev/diskid etc) >=20 > Okay. I thought I would try this last bit. However, only the first = two disks (still ada0 and ada1) list partitions in /dev/gpt, because I = just used the entirety of the other two disks I guess. And, only the = other two disks have shown up in /dev/diskid. (nb, later research shows = the other disks when I run =E2=80=9Cgpart list=E2=80=9D, but they have = =E2=80=9C(null)" labels, as do their one partitions) >=20 > So, "import -d /dev/gpt=E2=80=9D doesn=E2=80=99t find anything = (because none of tank=E2=80=99s disks are there), and =E2=80=9Cimport -d = /dev/diskid=E2=80=9D finds the same as it configured automatically, with = ada1p4 and the two diskid=E2=80=99s. Only /dev/gptid does what you = describe above, where it lists all three by gptid, but I would prefer = not to do that atm. >=20 > I was hoping to get =E2=80=9Cada1p4=E2=80=9D =E2=80=9Cd0p1=E2=80=9D = and =E2=80=9Cd1p1=E2=80=9D. If I ls /dev, I see: >=20 > # ls -l /dev/ada* /dev/da* > crw-r----- 1 root operator 0x5f Aug 11 01:20 /dev/ada0 > crw-r----- 1 root operator 0x60 Aug 11 01:20 /dev/ada0p1 > crw-r----- 1 root operator 0x61 Aug 11 01:20 /dev/ada0p2 > crw-r----- 1 root operator 0x62 Aug 11 01:20 /dev/ada0p3 > crw-r----- 1 root operator 0x64 Aug 11 01:20 /dev/ada1 > crw-r----- 1 root operator 0x6b Aug 11 01:20 /dev/ada1p1 > crw-r----- 1 root operator 0x6c Aug 11 01:20 /dev/ada1p2 > crw-r----- 1 root operator 0x6d Aug 11 01:20 /dev/ada1p3 > crw-r----- 1 root operator 0x6e Aug 11 01:20 /dev/ada1p4 > crw-r----- 1 root operator 0x65 Aug 11 01:20 /dev/da0 > crw-r----- 1 root operator 0x70 Aug 11 23:20 /dev/da0p1 > crw-r----- 1 root operator 0x66 Aug 11 01:20 /dev/da1 > crw-r----- 1 root operator 0x76 Aug 11 23:20 /dev/da1p1 >=20 >=20 > So I=E2=80=99d think it would work, but, both =E2=80=9Czpool = import=E2=80=9D and =E2=80=9Czpool import -d /dev=E2=80=9D both show = tank as: >=20 > tank ONLINE > raidz1-0 ONLINE > ada1p4 ONLINE > diskid/DISK-WOL240261932p1 ONLINE > diskid/DISK-WOL240261922p1 ONLINE >=20 >=20 > Let me know if there=E2=80=99s something else I can try. Otherwise, = I may just try putting gpt labels on the other partitions. But, I have = more controller swapping soon, so it=E2=80=99s mostly just informational = at the moment. Hello, Try adding -o cachefile=3Dnone to the import command. As you mention, you should however add labels to your disks and make ZFS = import them by label. ada/da may not be consistent over reboot, so label are a much better way = to quickly identify (failed) disks. Ben From owner-freebsd-fs@freebsd.org Sat Aug 12 15:50:36 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AE77CDDEA2F for ; Sat, 12 Aug 2017 15:50:36 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 6FB7E65B89 for ; Sat, 12 Aug 2017 15:50:36 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by mail-qk0-x241.google.com with SMTP id m84so6019443qki.5 for ; Sat, 12 Aug 2017 08:50:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kraus-haus-org.20150623.gappssmtp.com; s=20150623; h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MjHsvgiLSvpfuasu3J/hQLYf8RWllt/+/3QQNmkY7qM=; b=saBFQ9HrIFzogDEf3rH7kTR4rNWBvVkUgEYn032Uyu72w0egPUh0YN/CexTnhg9iHp 38Uj80hTjZFbryc5H9sdty4Ebnu/VAvXkGtAwmbMFkDnM8a+MrZ7Vz+utFyE2WwpkiYr vp8dwFBi8KGH8zuGNznD5RzCBXizVTdVtMw62+Z4xykj3UPNpZtVMm71h7Eg9L8sCUdG ehGkftp5zauJDEq6Gb9tudzzd04JiyYslDaEQI/qbNCGe/kCFZUko/7Mxl4S+mFU/ixQ JfvhCHPsrP08rVvMrC66uzcEPDFtNAnNL+oKAz6Xm3L1FsftIX5VB9UOmto+2wZiqQ+O qbEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MjHsvgiLSvpfuasu3J/hQLYf8RWllt/+/3QQNmkY7qM=; b=KD10/yqnqjnpw6gqkwKFuidrtAAhxvqoi3tNWVSo2XBgadK81WsxUbBDnQLLZWTsVM moyL+XLAdbCThTT8eEr3O2fsNq9Bl+CAo8b3q61Aps6tEI+VV6u7mFjvBDEtr8KmZs1j yIDbVZwFKSH8x4T0mvF3kYFeZhhICbqe4pz9IO8xaG4oszgEGtPDxXM4NDdn8zzirc8J yNZOoFy8zO39yP0WtSuKZbdZR1/P0KwP79ldaVJsXCy2qxvxCOQsFr1e0u2j7/5vIyBQ RNeKr6E+YT/01eBCQAnlHJHGnj5pj6M35LH0RejLfQ4QK4EpKWqKQrQ8uehIP3Ld+j4i dx8w== X-Gm-Message-State: AHYfb5hcJAW+Sy517iE/g3srSDNcuAqgPTtmkeQa7tfbDvhOWXg75n+b LZmqKh8UvGeqRSQG X-Received: by 10.55.20.25 with SMTP id e25mr24944550qkh.75.1502553035460; Sat, 12 Aug 2017 08:50:35 -0700 (PDT) Received: from [192.168.2.65] (pool-74-109-188-83.albyny.fios.verizon.net. [74.109.188.83]) by smtp.gmail.com with ESMTPSA id r23sm2399878qtc.50.2017.08.12.08.50.33 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 12 Aug 2017 08:50:33 -0700 (PDT) Subject: Re: zfs listing and CPU Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=us-ascii From: Paul Kraus In-Reply-To: Date: Sat, 12 Aug 2017 11:50:34 -0400 Cc: freebsd-fs@freebsd.org, freebsd-stable Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "Eugene M. Zheganin" X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 15:50:36 -0000 > On Aug 11, 2017, at 2:28 AM, Eugene M. Zheganin = wrote: >=20 > Why does the zfs listing eat so much of the CPU ? > 47114 root 1 20 0 40432K 3840K db->db 4 0:05 26.84% = zfs > 47099 root 1 20 0 40432K 3840K zio->i 17 0:05 26.83% = zfs > 47106 root 1 20 0 40432K 3840K db->db 21 0:05 26.81% = zfs > 47150 root 1 20 0 40432K 3428K db->db 13 0:03 26.31% = zfs > 47141 root 1 20 0 40432K 3428K zio->i 28 0:03 26.31% = zfs > 47135 root 1 20 0 40432K 3312K g_wait 9 0:03 25.51% = zfs > This is from winter 2017 11-STABLE (r310734), one of the 'zfs'es is = cloning, and all the others are 'zfs list -t all'. I have like 25 gigs = of free RAM, do I have any chance of speeding this up using may be some = caching or some sysctl tuning ? We are using a simple ZFS web API that = may issue concurrent or sequential listing requests, so as you can see = they sometimes do stack. How many snapshots do you have ? I have only seen this behavior with = LOTS (not hundreds, but thousands) of snapshots. What does your `iostat -x 1` look like ? I expect that you are probably = saturating your drives with random I/O. From owner-freebsd-fs@freebsd.org Sat Aug 12 16:32:17 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE912DE114A for ; Sat, 12 Aug 2017 16:32: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 mx1.freebsd.org (Postfix) with ESMTPS id 9D86D676A6 for ; Sat, 12 Aug 2017 16:32:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7CGWHJF073922 for ; Sat, 12 Aug 2017 16:32:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221075] regression: 11.1 is unable to mount ZFS / on boot Date: Sat, 12 Aug 2017 16:32: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.1-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: seschwar@gmail.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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 16:32:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221075 --- Comment #13 from seschwar@gmail.com --- So I had another go at this... (In reply to Marius Strobl from comment #12) > (is the card reader you mention a USB one?). nope: $ pciconf -lv (...) none2@pci0:11:0:0: class=3D0x0c0010 card=3D0x04a31028 chip=3D0x11f71217 re= v=3D0x05 hdr=3D0x00 vendor =3D 'O2 Micro, Inc.' device =3D 'OZ600 1394a-2000 Controller' class =3D serial bus subclass =3D FireWire none3@pci0:11:0:1: class=3D0x080501 card=3D0x04a31028 chip=3D0x83201217 re= v=3D0x05 hdr=3D0x00 vendor =3D 'O2 Micro, Inc.' device =3D 'OZ600RJ1/OZ900RJ1 SD/MMC Card Reader Controller' class =3D base peripheral subclass =3D SD host controller none4@pci0:11:0:2: class=3D0x018000 card=3D0x04a31028 chip=3D0x83301217 re= v=3D0x05 hdr=3D0x00 vendor =3D 'O2 Micro, Inc.' device =3D 'OZ600 MS/xD Controller' class =3D mass storage > The one thing that comes to my mind is that since r318197, mmcsd(4) depen= ds > on geom_flasmap(4) and that the latter might cause some interaction with = ZFS. > (...) One - not necessarily conclusive - way to > test the theory of interaction between geom_flasmap(4) and ZFS would be t= o use > a kernel built from a configuration with mmcsd(4) removed, so this depend= ency > isn't dragged in. Ok, I've build a 11.1 kernel using the following configuration: $ cat /usr/src/sys/amd64/conf/CUSTOM include GENERIC ident CUSTOM nodevice mmc nodevice mmcsd nodevice sdhci This kernel is indeed capable of mounting the root filesystem on my ZFS poo= l!=20 So your guess that base r318197 is not actually the cause of this, but mere= ly exposes the issue is probably spot on. 12.0-CURRENT not exhibiting the issue raises the question if the underlying problem is fixed there, or just happens to not be triggered. Is there a way for me to provide more information on this? Maybe boot with kern.geom.debugflags set to some appropriate value? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Aug 12 17:14:52 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 01C15D94971 for ; Sat, 12 Aug 2017 17:14:52 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C52CB694AA for ; Sat, 12 Aug 2017 17:14:51 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (lava.sentex.ca [IPv6:2607:f3e0:0:5::11]) by smarthost2.sentex.ca (8.15.2/8.15.2) with ESMTPS id v7CHEcZ3024466 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sat, 12 Aug 2017 13:14:39 -0400 (EDT) (envelope-from mike@sentex.net) Received: from [192.168.43.26] (saphire3.sentex.ca [192.168.43.26]) by lava.sentex.ca (8.15.2/8.15.2) with ESMTP id v7CHEaEd079458 for ; Sat, 12 Aug 2017 13:14:37 -0400 (EDT) (envelope-from mike@sentex.net) To: "freebsd-fs@freebsd.org" From: Mike Tancsa Subject: protecting zfs snapshot info Organization: Sentex Communications Message-ID: Date: Sat, 12 Aug 2017 13:14:37 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.78 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 17:14:52 -0000 Is there a way in zfs to protect non root users from seeing snapshots ? lets say a user makes a permissions mistake on a sensitive homedirectory on a Monday AM that is not discovered until the next day. If there are a whole mess of snapshots created between those two points in time, there is no way to protect that directory without deleting the snapshots. ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-fs@freebsd.org Sat Aug 12 23:36:59 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25B5CDD1C1D for ; Sat, 12 Aug 2017 23:36:59 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254:10::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BDB7376754 for ; Sat, 12 Aug 2017 23:36:58 +0000 (UTC) (envelope-from cross+freebsd@distal.com) Received: from mail.distal.com (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]) (authenticated bits=0) by hydra.pix.net (8.16.0.19/8.15.2) with ESMTPSA id v7CNanaS097695 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Sat, 12 Aug 2017 19:36:56 -0400 (EDT) (envelope-from cross+freebsd@distal.com) Received: from magrathea.distal.com (magrathea.distal.com [IPv6:2001:470:e24c:200:ea06:88ff:feca:960e]) (authenticated bits=0) by mail.distal.com (8.15.2/8.15.2) with ESMTPSA id v7CNalwM091586 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 12 Aug 2017 19:36:48 -0400 (EDT) (envelope-from cross+freebsd@distal.com) From: Chris Ross Content-Type: multipart/signed; boundary="Apple-Mail=_E3908DB3-977A-4930-9B6F-C35E4B2D5B44"; protocol="application/pgp-signature"; micalg=pgp-sha512 Subject: Oh no, what have I done... Message-Id: <3408A832-BF2E-4525-9EAC-40979BA3555B@distal.com> Date: Sat, 12 Aug 2017 19:36:31 -0400 To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mail.distal.com [IPv6:2001:470:e24c:200:0:0:0:ae25]); Sat, 12 Aug 2017 19:36:48 -0400 (EDT) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Aug 2017 23:36:59 -0000 --Apple-Mail=_E3908DB3-977A-4930-9B6F-C35E4B2D5B44 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 So, I had a zpool with a single raidz1 in it. That was fine. I = wanted to make that pool bigger, and learned by researching how to do = that that I _can=E2=80=99t_ add a device to the raidz1, as I=E2=80=99d = presumed I would do, to just make it larger. While researching other = options, I added a lone device to the pool, somewhat by accident, but = then realized =E2=80=9Coh wait, that won=E2=80=99t give me redundancy or = safety, not what I want=E2=80=A6=E2=80=9D so tried to take it back out = before data got written to it. However, that appears to not be an = option. After finding that =E2=80=9Cremove=E2=80=9D and =E2=80=9Coffline=E2= =80=9D don=E2=80=99t work for that disk vdev, I just pulled the disk. = All the while assuming that since the raidz1 was still kosher, I would = find a way to get it running as long as noone wrote a bunch of data to = the erroneously attached disk. But, I fear I may=E2=80=99ve shot myself. Is there any way to recover = my raid1z vdev from this situation, and get a working zfs pool back? Before a reboot, which seems to have made things worse, the pool in = question looked: cross@hyrule[~](576): sudo zpool status tank pool: tank state: UNAVAIL status: One or more devices are faulted in response to IO failures. action: Make sure the affected devices are connected, then run 'zpool = clear'. see: http://illumos.org/msg/ZFS-8000-HC scan: scrub repaired 0 in 10h39m with 0 errors on Thu May 12 09:55:26 = 2016 config: NAME STATE READ WRITE CKSUM tank UNAVAIL 0 0 0 raidz1-0 ONLINE 0 0 0 ada1p4 ONLINE 0 0 0 gpt/3g01 ONLINE 0 0 0 gpt/3g02 ONLINE 0 0 0 10950428150510887813 REMOVED 0 0 0 was = /dev/da2p1 errors: No known data errors Is there anything that can be done here? A =E2=80=9Czfs import=E2=80=9D= from single user doesn=E2=80=99t seem at all willing to consider it, = just fails immediately with I/O error. Help? (And no, of course I don=E2=80=99t have backups! Technically, = it was all data that wasn=E2=80=99t critical and/or could be recovered, = but it will take days to reconfigure things, and data will be lost.) - Chris --Apple-Mail=_E3908DB3-977A-4930-9B6F-C35E4B2D5B44 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJZj5EPAAoJEPFBDnXvoNg0ggkP/RPXCbwJnMtnk4LrmN5w/5+i RstmAf77xSSxM7xgnh18uOYzIF3fxl9irRxkz9bd3EadgEnROQh8H5GCm3WAnmJr fBoG7txo1mc9qfIbQyhkYUdv3AAY72ncSgMf0Egn0gi7TdXGXt35Mc/81aF7/+it C21Pcee1PLZXGWt4EBSt8/pWWJiyQ8M5d/MBI3i5jYMB6Zm624QLPgEwWQR7Fq53 yZ1jcbv9i7Q/7Il74KUVqjoNJSzIzG5l+itXePK+U3l5UnQUKohH8M5Tm/ZnboWy jiy8E2P3W59oiDO+iVNYy6D/WXe1+skM1zP2O/DN3PGMtJ0QCCNsT8qMXmmi+Omm qVeI0bm2QdtwwGAbU+0RkZtYgNT1sQNmdCjYuTyPGBrhFDJMKDca6uED908j6/BC Me+MMZVvvzn/BKUDs3dFXod1PyxAHPpGMCeaOv+Qmbl7HfHPUOZuNUjXUk0vL2Ll YTnTOSsROOdzNHGBr1eII33hZA/+PBV5lsciNu8M/B6Fumh0+EbWjAchNvgJhmKL da1Rhkyv3/E7z81lgOx8+bnXI7spQ2/7JNpxWg5fwrY35Z91UYRBEwocPeUoZsRu EZkY7CmjbQdm6C0nZM1eSQYcA08J0bE0+Fb4RZV/OA6syGIWomPEF7whoVgQT4q/ X7JYk9DWRc1IAIO0FelB =muXc -----END PGP SIGNATURE----- --Apple-Mail=_E3908DB3-977A-4930-9B6F-C35E4B2D5B44--