From owner-freebsd-fs@FreeBSD.ORG Tue Jul 2 22:07:40 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5FB4CF37 for ; Tue, 2 Jul 2013 22:07:40 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by mx1.freebsd.org (Postfix) with ESMTP id 31CDA193A for ; Tue, 2 Jul 2013 22:07:40 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id o6so7203467oag.27 for ; Tue, 02 Jul 2013 15:07:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=YlA02al/8v8JECynBIECl3Rzuu9NXn9tXhkX+hh4DfI=; b=NqSr0RzQKNPY03SZrp0Z23nIHSMhRO2z0sTF5HaqmcC4yQ2pxC/VGQbcGQ77l0bm67 rVwGjdFWLkfE9MjGLYz79qH0jgjkJk42lAhJnI/BxGvJJRGeLaEVvPv+P7AL1yiA8AJo 3wlwUgioA9AaQbbpgaOHtpEdloe9A/E4GnDJZTGE5+aabiQbeeBw1R5Pii2Iptn12XJy A49MAHfMDQRaBMlgDaigQd0D7RB9qyHyKQADPcpLyCH5uYqoi0H5gnGzJtZzA80CQ1sa NsqqTz4VxMMPEJuV3ssH6XG4agRjo0omyUMc4MN/lw4r/QT/KIJsQhsZgTQo3qu0j0Rr tu3A== MIME-Version: 1.0 X-Received: by 10.182.171.7 with SMTP id aq7mr13017251obc.103.1372802859126; Tue, 02 Jul 2013 15:07:39 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.76.112.212 with HTTP; Tue, 2 Jul 2013 15:07:39 -0700 (PDT) Date: Tue, 2 Jul 2013 15:07:39 -0700 X-Google-Sender-Auth: V5e2uS_onrtWK_7E6maON3scDiM Message-ID: Subject: New fusefs implementation not usable with multiple fusefs mounts From: Kevin Oberman To: fs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Attilio Rao X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 22:07:40 -0000 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. -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com