From owner-freebsd-current@FreeBSD.ORG Sat Jul 20 04:42:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 68B8391; Sat, 20 Jul 2013 04:42:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by mx1.freebsd.org (Postfix) with ESMTP id 296491FD; Sat, 20 Jul 2013 04:42:42 +0000 (UTC) Received: by mail-ob0-f169.google.com with SMTP id up14so6299928obb.14 for ; Fri, 19 Jul 2013 21:42:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kg5b3Fnd2DzjtMDaYZcGfIlsu94bOLBssI1XF55r+b0=; b=nBuJEyTGx2LuIHmOSEc8ckcBLCkMyeKcGqsd/o2d8Hyi0FWkMYF67csqKaa4UwNhx3 eo8oKqHOy6To2r+PA30GRD7tTLfzElshRYWH7iqUtiBuBoGvSTrsOtc9TfKxETkoDHiT tNS7D4t57W05J78eaYufM7imCaAIK5gOPGa/ldvaozVNU9si6GNaOLiKaOqYLiAWsh2l GFt7flPKIb1jw185k4cpF/2sZCuUZK2EcLpT6oBrBTCVem4D+wo77iaBSQBzKzQiGeLh kjskA+kp1qUvno8i4w9QnQ/V6frhVO4OkggPByy+LaEaaMrj73gSfYz1PgjD6mmaLZDE +xPA== MIME-Version: 1.0 X-Received: by 10.182.153.72 with SMTP id ve8mr14729378obb.39.1374295361763; Fri, 19 Jul 2013 21:42:41 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.76.112.212 with HTTP; Fri, 19 Jul 2013 21:42:41 -0700 (PDT) In-Reply-To: <51E9E669.3090500@FreeBSD.org> References: <51E94F09.4020109@FreeBSD.org> <51E95B4D.4030104@gmail.com> <51E96C84.3000209@FreeBSD.org> <51E97265.8040507@gmail.com> <51E9E669.3090500@FreeBSD.org> Date: Fri, 19 Jul 2013 21:42:41 -0700 X-Google-Sender-Auth: PHfrWbDYpx5YLQ1poL2U7YHFhro Message-ID: Subject: Re: FUSE not work. From: Kevin Oberman To: Pedro Giffuni Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Alexander Panyushkin , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 04:42:42 -0000 On Fri, Jul 19, 2013 at 6:22 PM, Pedro Giffuni wrote: > On 19.07.2013 12:07, Alexander Panyushkin wrote: > >> 19.07.2013 19:42, Pedro Giffuni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> >>> (re-posting since the original response didn't make it through) >>> >>> On 19.07.2013 10:29, Alexander Panyushkin wrote: >>> >>>> 19.07.2013 17:36, Pedro Giffuni =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> >>>>> Hello; >>>>> >>>>> The internal data structures in the FUSE kernel module have been >>>>> updated to be more compatible with MacFUSE and the linux FUSE. >>>>> >>>>> This basically means you have to rebuild your fuse modules >>>>> (including NTFS). >>>>> >>>>> We should not really update the FUSE_KERNEL_MINOR_VERSION yet. >>>>> I will add a note to UPDATING. >>>>> >>>>> Pedro. >>>>> >>>> >>>> >>>> >>>> Unfortunately the port is not build in FreeBSD 10 >>>> >>>> >>>> =3D=3D=3D>>> Starting build for sysutils/fusefs-kmod <<<=3D=3D=3D >>>> >>>> >>> fusefs-kmod is not needed on -current. I meant you have to rebuild >>> and reinstall fusefs-* ; in particular fusesfs-libs and ntfs. >>> >>> Since this is a ports issue I will not update the UPDATING file. >>> >>> Developers that need to know should use __FreeBSD_version >>> 1000038 as a reference. >>> >>> >> I rebuild sysutils/fusefs-ntfs with Clang and GCC, but this has no effec= t. >> >> sysctl kern.osreldate >> kern.osreldate: 1000037 >> >> ntfs-3g /dev/ad10s1 /mnt/ntfs_0 >> mount >> ... >> /dev/fuse on /mnt/ntfs_0 (fusefs, local, synchronous) >> >> ls -la /mnt/ntfs_0 >> unique: 18, opcode: GETATTR (3), nodeid: 1, insize: 40, pid: 47053 >> getattr / >> unique: 18, success, outsize: 112 >> fuse: writing device: Invalid argument >> ls: /mnt/ntfs_0: Input/output error >> >> fuse is at least partly broken in -current. I discovered that if you mount two devices that use fuse, when you umount any of them, ll are marked as not mounted and disappear from df(1) or mount(8) output, but only one is actually cleanly unmounted and, if it has been written to, will likely be corrupt. This applies to at least ntfs. ATM no one is supporting fuse in current, so this may become a serious issue before long. --=20 R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com