From owner-freebsd-ports@FreeBSD.ORG Tue Oct 30 04:01:59 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3583F6E7 for ; Tue, 30 Oct 2012 04:01:59 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ea0-f182.google.com (mail-ea0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id AF7E88FC0C for ; Tue, 30 Oct 2012 04:01:57 +0000 (UTC) Received: by mail-ea0-f182.google.com with SMTP id c10so2470123eaa.13 for ; Mon, 29 Oct 2012 21:01:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IGXigpXQIIvp1pD0XF2elwMG1ZybEUmGriMtyz/1+tA=; b=sbVnWSU9oMHly5h6obX0ANNs0XLGwPPQZT1ymDTXWbgN3kFSGgpJc8sANi6Yt3Gsrn eqDxKL6/B3YJCMe2irNdEHyk5KWYmP3juTGtD7IWZg8Kee+8/DVqQXVtCnKg/53W/z9C T+PVLfae3hMkGce3il+OExAUpI7ooU3A3eRjVH6+JF6D0R4L9t7zBdTy/BgX9Fu73f8Q aqhZfeCVDAHMdqdxIyky3y+kxJCHYHkZGYWkXmKbVX/mnC6KZ0g6UofY1Khns6gz7fWx DIJyav2NE7wbr/DCcY+sB/eYBFXaLgpFjBhD5GDFalMevfouyGnRt2qk3Pq/ff0VLKpC HPFQ== MIME-Version: 1.0 Received: by 10.14.220.71 with SMTP id n47mr68790219eep.26.1351569716695; Mon, 29 Oct 2012 21:01:56 -0700 (PDT) Received: by 10.223.66.194 with HTTP; Mon, 29 Oct 2012 21:01:56 -0700 (PDT) In-Reply-To: <508E76B3.2030306@smeets.im> References: <508E76B3.2030306@smeets.im> Date: Mon, 29 Oct 2012 21:01:56 -0700 Message-ID: Subject: Re: fuse problems From: Kevin Oberman To: Florian Smeets Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2012 04:01:59 -0000 On Mon, Oct 29, 2012 at 5:29 AM, Florian Smeets wrote: > On 10/29/2012 07:46, Kevin Oberman wrote: >> Florian, >> >> After updating fusefs-libs to 2.9.9 I fould serious problems with an >> NTFS file system. I am using the new fuse kernel code on 9-Stable on >> an amd64 system. >> > > I don't think it is related to the fusefs-libs update to 2.9.2. > > Can you please replace sysutils/fusefs-kmod with this version and revert > the fuse changes from your source tree? > http://people.freebsd.org/~flo/fusefs-kmod.tar.bz2 > > Reinstall fusefs-libs (2.9.1 or 2.9.2 shouldn't matter) and ntfs-3g, and > please try to copy something again. (after repairing the filesystem > obviously :)) > > Please also make sure that the old fuse.ko is gone from > /usr/local/modules, and make absolutely sure that you load the new > module. You should see > > fuse-freebsd: version 0.4.4, FUSE ABI 7.8 > > in /var/log/messages. > > I only have a "real" NTFS partition on a 10-current host, but with > fusefs-libs-2.9.2 and the in tree fuse code i was able to copy the > complete source tree to the NTFS partition without problems. So with my > new fusefs-kmod port it should work the same on 9.x. It does if I create > an md backed NTFS partition on a 9.x host and copy stuff over. You may be right, but I have done quite a bit of testing of the new kernel code with fusefs-ntfs and it had not given me any problem until this one that bit the day I upgraded fusefs-libs.. It was pretty nasty, but runnig a disk check on Windows fixed the problems though I lost all files copied to that system since the problem cropped up. Irt was part-way through a transfer of about 20 files totaling 150 or 200 MB. I should mention that the files were all copied over a network that was performing poorly due to a memory leak in the router. I can't see how that could have been tied to the problem, though. I'll upgrade fusefs-lib again tomorrow, but I'm moving this weekend and getting things ready to go, so I probably will not be able to do much testing. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com