From owner-freebsd-current@FreeBSD.ORG Wed Jul 18 21:30:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D98B310656A7; Wed, 18 Jul 2012 21:30:24 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6B83F8FC17; Wed, 18 Jul 2012 21:30:23 +0000 (UTC) Received: by weyx56 with SMTP id x56so1556586wey.13 for ; Wed, 18 Jul 2012 14:30:22 -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:content-transfer-encoding; bh=PCdscUIOIQ4JOeXRvI+Dcj4Fnho/E4C2wnNrArd9siw=; b=UlFnSHfNi2u+LbAqiSSUxxPEtAkdIG5hSw4tCYiZ0nrBrkG8ODpxJVBzNug9zjbiaf dVO5bUol87Cja3QvAmvZeZyvyA0t3ABazRsH/FRiTXuGhK4/R1y7OwgTzo3/1R/16Fvh kiOVtftxKe6UNbxeoRY1GlamNruVE0mTTRQOgvuJ+QK0cvL1pKNSIHgoSUE5JDtjDgY5 jbPCB8PwGFCJTZYDSsl6BuSw4D5pL5KJTThXJ7fABB+++mPOukUlEbaPQ8ceXgwgvDtB VKL++/ihzlkmB53CT/Njhzx39k/hoqIWSRazvUDwWrWWMdqQo2CY6+7nBehVpN3sm+H4 XESw== MIME-Version: 1.0 Received: by 10.180.100.136 with SMTP id ey8mr9941213wib.15.1342647022248; Wed, 18 Jul 2012 14:30:22 -0700 (PDT) Received: by 10.223.60.147 with HTTP; Wed, 18 Jul 2012 14:30:22 -0700 (PDT) In-Reply-To: <50064FB2.3020409@entel.upc.edu> References: <50064FB2.3020409@entel.upc.edu> Date: Wed, 18 Jul 2012 14:30:22 -0700 Message-ID: From: Kevin Oberman To: =?UTF-8?Q?Gustau_P=C3=A9rez_i_Querol?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: attilio@freebsd.org, FreeBSD FS , freebsd-current@freebsd.org, George Neville-Neil Subject: Re: MPSAFE VFS -- List of upcoming actions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 18 Jul 2012 21:30:25 -0000 On Tue, Jul 17, 2012 at 10:54 PM, Gustau P=C3=A9rez i Querol wrote: > > Sorry fo the delay. > > About the ntfs support, I'd go with fuse and leave the most relevant > filesystems in kernel space. In fact filesystems not particulary specific > and not tied our kernel would go to userspace; thinks like smbfs, nwfs, > ntfs, ext2 o ext4 for example should be in userspace (the list is incompl= ete > and I don't really know if all of them are yet implemenent in userspace) = in > my opinion. That would make them easier to maintain (changes in the kerne= l > would only affect fuse, once fixed all the userspace filesystem would wor= k > again). > > As a bonus, we would get many working fs based on fuse. In the server > side gluster is a desirable thing; in the desktop things like gvfs (in th= e > linux world gvfs is used not only by gnome but also by kde or xfce) or > truecrypt > > >> >> I'm fixing low hanging fruit for the moment (see r238411 for example) >> and I still have to make a throughful review. >> However my idea is to commit the support once: >> - ntfs-3g is well stress-tested and proves to be bug-free >> - there is no major/big technical issue pending after the reviews >> >> I'm now looking for people sticking with the branch and trying to >> stress-test ntfs-3g as much as they can. For example I know that >> Gustau (cc'ed) already had issues. It would be good if he tries to >> reproduce them and make a full report. > > > I've seen ntfs-3g+fuse crashing a few times and IIRC most of the time = the > problem happened while unmounting the filesystem. I can reliably crash a system by doing an rsync to an ntfs-3g mounted FS. I have simply stopped doing it an have spent no time trying to track down the problem, but maybe anyone (gnn?) working on fusefs might want to try it. FWIW, I can to "rsync -avn local-path/ remote-system:ntfs-3g/path" always works. Remove the 'n' and actually move the data and it dies. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com