Date: Fri, 30 Dec 2011 11:02:56 +0200 From: Gleb Kurtsou <gleb.kurtsou@gmail.com> To: David P Discher <dpd@bitgravity.com> Cc: freebsd-fs@freebsd.org, Johannes Totz <jtotz@imperial.ac.uk> Subject: Re: fusefs broken on 8-stable? Message-ID: <20111230090256.GA6796@reks> In-Reply-To: <C2F65D41-3D0D-4453-9046-BB85AF66860B@bitgravity.com> References: <iqj9pf$mrn$1@dough.gmane.org> <isc2ui$kq$1@dough.gmane.org> <87E5C7D5-2D73-4A42-B871-8B27448B0DD9@bitgravity.com> <20111229215125.GA8539@reks> <C2F65D41-3D0D-4453-9046-BB85AF66860B@bitgravity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On (29/12/2011 14:06), David P Discher wrote: > Is this a straight dump for p4 ? > > Earlier this week, I checked out //depot/projects/soc2011/ilya_fuse/... out of p4. But only used the kmod, not the libs. Unfortunately, it was 10x slower than the 0.3.9 version currently in the ports tree. I never got it to the same point ... after a few days, had only written about 6-10GB of data. It's the same as p4 (+ few minor tweaks). fuse-0.4 is more strict on resizing files which is very likely to be slow for encrypted file system (encfs). Try setting sysctl vfs.fuse.sync_resize=0. I don't know all the details but there was memory leak and arbitrary memory corruption in old fuse. It's believed to be fixed in fuse-0.4. My guess you are hitting the same bug. > My panic happens after about 500-600GB of data has been written via the fuse. > > However, my testing is easy (except for the waiting) ... I'll gladly give it a try. > > --- > David P. Discher > dpd@bitgravity.com * AIM: bgDavidDPD > BITGRAVITY * http://www.bitgravity.com > > On Dec 29, 2011, at 1:51 PM, Gleb Kurtsou wrote: > > > > > There is alternative fuse port at https://github.com/glk/fuse-freebsd-ports > > > > Could you try it and let us know if it works. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111230090256.GA6796>