From owner-freebsd-current@FreeBSD.ORG Fri Feb 27 07:41:36 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1BC7097F for ; Fri, 27 Feb 2015 07:41:36 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E1D0A128 for ; Fri, 27 Feb 2015 07:41:35 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id t1R7CYTV078027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 26 Feb 2015 23:12:35 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54F018DD.30800@freebsd.org> Date: Thu, 26 Feb 2015 23:12:29 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: FreeBSD FUSE calls truncate() on read-only files References: <6676D082-5C06-4E59-B22C-5C00D1FD229F@netapp.com> In-Reply-To: <6676D082-5C06-4E59-B22C-5C00D1FD229F@netapp.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Fri, 27 Feb 2015 07:41:36 -0000 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