From owner-freebsd-current@FreeBSD.ORG Wed Jul 24 18:16:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EE789D27; Wed, 24 Jul 2013 18:16:52 +0000 (UTC) (envelope-from vsityz@gmail.com) Received: from mail-ea0-x22d.google.com (mail-ea0-x22d.google.com [IPv6:2a00:1450:4013:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2F8602368; Wed, 24 Jul 2013 18:16:52 +0000 (UTC) Received: by mail-ea0-f173.google.com with SMTP id g10so419647eak.4 for ; Wed, 24 Jul 2013 11:16:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=9/aMqd1FXoBSOMUKjsXsibxVsPWlZOQEBClZh0xtQx8=; b=idnI268ekdQYUpZIIiixABoWnOg7esMgZJX8KVR2QMZnaUPu1/iLyHr15bPpE4j5wL yqq4t5UZN6ChQ5vy4vnkgDOhvgRnQfs8GciA8MYlsj7E+ZFgLnDVDyRpYX+DIJBbW2Ii h/9qK0Pg2ErNFXiV/eHUKcxSQJUgiZ8yuUzEfThHIzqXpPsob44FW1kCF3iMMcOcg8rp 2raSGHumIWJDeuhzmYP6tTYZZ7JYgwWJBccS4uHUFaRoJE1C1FfXpNQVo7fB5VlXciPr Hh4uV9wJEYk18CT8osRdPynGqSnjMuz/9gHLmMqAc+0g+cPwwYq8cfBeAT9QYJSP7FCh hHOA== X-Received: by 10.15.54.198 with SMTP id t46mr39121772eew.74.1374689810460; Wed, 24 Jul 2013 11:16:50 -0700 (PDT) Received: from scorpion.kiev.ua ([46.247.165.131]) by mx.google.com with ESMTPSA id r54sm67864089eev.8.2013.07.24.11.16.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 11:16:49 -0700 (PDT) Message-ID: <51F01A0C.2070808@gmail.com> Date: Wed, 24 Jul 2013 21:16:44 +0300 From: Alexander Panyushkin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130721 Thunderbird/17.0.7 MIME-Version: 1.0 To: Baptiste Daroussin , FreeBSD Current Subject: Re: FUSE not work. References: <51E94F09.4020109@FreeBSD.org> <51E95B4D.4030104@gmail.com> <51E96C84.3000209@FreeBSD.org> <51E97265.8040507@gmail.com> <51E9E669.3090500@FreeBSD.org> <20130724152216.GE63694@ithaqua.etoilebsd.net> In-Reply-To: <20130724152216.GE63694@ithaqua.etoilebsd.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Kevin Oberman , Pedro Giffuni 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: Wed, 24 Jul 2013 18:16:53 -0000 24.07.2013 18:22, Baptiste Daroussin пишет: > On Fri, Jul 19, 2013 at 09:42:41PM -0700, Kevin Oberman wrote: >> 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 пишет: >>>> >>>>> (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 пишет: >>>>>> >>>>>>> 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 >>>>>> >>>>>> >>>>>> ===>>> Starting build for sysutils/fusefs-kmod <<<=== >>>>>> >>>>>> >>>>> 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 effect. >>>> >>>> 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. > This is fixed now. > > btw this problem is/was not related to fuse on current but rather to > fusefs-libs. > > Bapt I am rebuilding now world uname -a FreeBSD scorpion.kiev.ua 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Wed Jul 24 20:34:19 EEST 2013 root@scorpion.kiev.ua:/usr/obj/usr/src/sys/Kernel amd64 and ports fusefs-libs-2.9.3 and fusefs-ntfs-2012.1.15 Problem not fixed.