Date: Thu, 26 Feb 2015 23:12:29 -0800 From: Julian Elischer <julian@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: FreeBSD FUSE calls truncate() on read-only files Message-ID: <54F018DD.30800@freebsd.org> In-Reply-To: <6676D082-5C06-4E59-B22C-5C00D1FD229F@netapp.com> References: <6676D082-5C06-4E59-B22C-5C00D1FD229F@netapp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/25/15 5:34 AM, Eggert, Lars wrote: > Hi, > > this came up when trying to port tup (https://github.com/gittup/tup) to FreeBSD. > > Even though we are opening the file read-only with cat, FUSE calls truncate() on it, which modifies its mtime and this screws up tup. See https://github.com/gittup/tup/issues/198 > > Anyone know why FreeBSD's FUSE is doing this? nope but it has lots of other bugs.. for example it caches information when it shouldn't, even from 'dynamic' file systems We had to change the code to disable it as our data is synthetic and might change between reads. fstat info is also cached and confused our apps mightily. > > Thanks, > Lars
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54F018DD.30800>