From owner-freebsd-fs@FreeBSD.ORG Tue Jul 2 22:20:01 2013 Return-Path: Delivered-To: fs@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 38A23286; Tue, 2 Jul 2013 22:20:01 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id 06AC6199B; Tue, 2 Jul 2013 22:20:00 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id aq17so13696165iec.36 for ; Tue, 02 Jul 2013 15:20:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hBGo1+pUXsexSuQaA0Vk2o5xHWkcdJDOw3R6r+pQERQ=; b=wSrBj5CZbBlnqLSbh1CGGWs/i6F4EdUN1PfvBy9dxEuHn85f26udIH4uUUAJD5XHrI xX6oL/6jLdE2Rc/5antCQVmUCy54NQRIFT7sjPkAxC/Xa6Y12y0AiiYsjESpW9Aveowz bbq03J25ngbV5hyik7i9P7E8Wt5RQMkSB4tKcDn9SeN4xj/lk/U8qolOPSx6cC7vmBCC y6+YlEBNcwBtkssbo4WB4QH8STYc/7fg5alMcQCOFQHqBorJ+7hrN8/JidBUEE9ORYgr r7i5c7aKIgSnIw8P/ueCAgI1N2ihqX4WKS6JunTSfI26cx0w59nPFc7fCxIGjkr2PApw FFAQ== MIME-Version: 1.0 X-Received: by 10.42.43.4 with SMTP id v4mr516861ice.109.1372803600779; Tue, 02 Jul 2013 15:20:00 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.42.253.129 with HTTP; Tue, 2 Jul 2013 15:20:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Jul 2013 00:20:00 +0200 X-Google-Sender-Auth: 8UrOPadts59ZtxuRGA_gi3Ooeok Message-ID: Subject: Re: New fusefs implementation not usable with multiple fusefs mounts From: Attilio Rao To: Kevin Oberman , George Neville-Neil Content-Type: text/plain; charset=UTF-8 Cc: fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 22:20:01 -0000 On Wed, Jul 3, 2013 at 12:07 AM, Kevin Oberman wrote: > I have been using the new fusefs for a while and have had to back it out and > go back to the old kernel module. I keep getting corrupted file NTFS systems > and I think I understand why, > > I mount two NTFS systems: > /dev/fuse 184319948 110625056 73694892 60% /media/Media > /dev/fuse 110636028 104943584 5692444 95% /media/Windows7_OS > > Note that both systems are mounted on /dev/fuse and I am assured that this > is by design. Both work fine for reads and seem to work for writes. Then I > unmount either of them. Both are unmounted, at least as far as the OS is > concerned. There is no way to unmount one and leave the other mounted. It > appears that any attempt to unmount either system does a proper unmount of > /media/Media, but, while marking /media/Windows7_OS as unmounted, actually > does not do so. The device ends up corrupt and the only way I have been able > to clean it is to boot Windows and have a disk check run. Media never seems > to get corrupted. > > Any further information I might gather before filing a PR? I am running on > 9.1 stable, but havehad the problem since the patch set first became > available on 9.0-stable. I do not understand, new fusefs implementation was never committed to stable branch to my knowledge. Did you backport manually? BTW I cc'ed George which should maintain the module. Attilio -- Peace can only be achieved by understanding - A. Einstein