From owner-freebsd-fs@FreeBSD.ORG Wed Oct 10 14:16:40 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA3D1DD2; Wed, 10 Oct 2012 14:16:40 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id EF7A28FC14; Wed, 10 Oct 2012 14:16:39 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id b5so579556lbd.13 for ; Wed, 10 Oct 2012 07:16:38 -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 :content-transfer-encoding; bh=Emw3WDSv3cx24RzP2Vb83jpaECCKgIrAtXUpxGs5fZY=; b=wun0N2XAePYS3hsFXW64YFISVZvxd7G+PS69SHQrKHRxXnmGn0eNmIwrK7S/rQ/wSI YyXb6gkxlTAJCXF8f8b1q2g/+3NL1oHWTBgJEDeLjaohQy1ONibO8Fby9dmv77XRBcso 1BMXjUcNT+jmtDNmXxzGJJZ3G2/9i/CRInksU1tVl3TsHCBk/APsjQsoLBb1tvwZETpY EQuLOpR8v8EHWdAAtWpLcEGLRAbKKi4uRwHFFnbGFJ0fuvOV8Q5/a5ANgUi/JniwwTWY g9tZZ+ZLlCl1N2P/WVx0sP0VoyFWG6Z1In7sgafL3ixybTRzWXIbcV9pwpP09mLfFqyL 0QaA== MIME-Version: 1.0 Received: by 10.112.28.98 with SMTP id a2mr1356473lbh.110.1349878598383; Wed, 10 Oct 2012 07:16:38 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.112.101.234 with HTTP; Wed, 10 Oct 2012 07:16:38 -0700 (PDT) In-Reply-To: References: <20120829060158.GA38721@x2.osted.lan> <20120831052003.GA91340@x2.osted.lan> <20120905201531.GA54452@x2.osted.lan> <20120917140055.GA9037@x2.osted.lan> <5061F6E9.6030104@omnilan.de> <5062E0DE.70805@omnilan.de> <5065B873.4070509@omnilan.de> Date: Wed, 10 Oct 2012 15:16:38 +0100 X-Google-Sender-Auth: OUg9aRI-HLCYpFCJ3ie2WQewPOU Message-ID: Subject: Re: MPSAFE VFS -- List of upcoming actions From: Attilio Rao To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD FS , Harald Schmalzbauer , freebsd-current@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: Wed, 10 Oct 2012 14:16:40 -0000 On Wed, Oct 10, 2012 at 6:15 AM, Kevin Oberman wrote: > On Mon, Oct 8, 2012 at 7:57 AM, Attilio Rao wrote: >> On Fri, Sep 28, 2012 at 4:47 PM, Harald Schmalzbauer >> wrote: >>> schrieb Attilio Rao am 28.09.2012 16:18 (localtime): >>>> On Wed, Sep 26, 2012 at 12:02 PM, Harald Schmalzbauer >>>> wrote: >>>>> ... >>>> After many people willing to test fuse on STABLE_9, I made this patch >>>> that at least compiles there: >>>> http://www.freebsd.org/~attilio/fuse_import/fuse_stable9_241030.patch >>> >>> Thanks a lot! In the meantime I made the original patch compiling. I >>> simply looked at the changes which were made around july in the fuse >>> project to follow changes in head (checkpath(), vrecycle() and >>> vtruncbuf()) and "reverted" them. >>> Since I have no idea about the code I modified, I'm happy that you did = a >>> more qualified patch set :-) >>> >>>> Of course, I didn't have a chance to test it because I'm also out for >>>> vacation right now but please do and report. >>> >>> Happy holiday!!! If you're by chance arround the Oktoberfest, drop me a >>> note, I'll pay you a Ma=C3=9F (or any other drink if you don't like >>> =E2=80=9EWiesnbier=E2=80=9C) :-) >> >> I really hoped to make this year, but no luck :/ >> >>>>> ... >>>>> Some questions: Is this planned to be mfc'd and if so, how can one kn= ow? >>>> In which sense "how can one know?". We usually specify MFC timeouts in >>>> the commit message (not sure if this answers your concerns). >>> >>> Yep, that's what I wanted to know. So if there's no MFC timeout in the >>> log, it's not intended to be MFCd ever I guess. >>> >>> Thanks a lot! >>> World/Kernel compiled fine in the meantime, I'll do some sshfs tests. >> >> Did you do any test in the end? >> >> Thanks, >> Attilio > > i have done same testing and it clearly is more stable than the old > kmod. At least operations that crashed my system now work. > > I did see one weird anomaly, though. I had several NTFS file system > mounted, one a Windows OS. I also had a GELI encrypted UFS file system > mounted. They were both mounted and working. I finished with the data > disk and tried to unmount it. I got no error, but it remained mounted. > I did not actually try to access it. Figured it would umount when I > shut down or end up dirty and I'd have to fsck it. The unmount attempt > was using nautilus/gnome-mount. This is not the odd part, though. Kevin, can you please report steps required to reproduce it in high detail (rather than a description), please? This will help in reproducing it and eventually fixing it. Attilio --=20 Peace can only be achieved by understanding - A. Einstein