From owner-freebsd-current@FreeBSD.ORG Mon Mar 2 08:37:09 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A7DBB87; Mon, 2 Mar 2015 08:37:09 +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 EF7C5F5F; Mon, 2 Mar 2015 08:37:08 +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 t228b7GM003043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 2 Mar 2015 00:37:07 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54F4212E.9030702@freebsd.org> Date: Mon, 02 Mar 2015 00:37:02 -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: Benjamin Kaduk Subject: Re: FreeBSD FUSE calls truncate() on read-only files References: <6676D082-5C06-4E59-B22C-5C00D1FD229F@netapp.com> <54F018DD.30800@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org 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: Mon, 02 Mar 2015 08:37:09 -0000 On 2/27/15 7:32 AM, Benjamin Kaduk wrote: > On Fri, 27 Feb 2015, Julian Elischer wrote: > >> 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. > You are of course planning to file bug reports about these issues, I > presume? > > -Ben > > First I hope to actually understand the problems.