Re: FreeBSD FUSE calls truncate() on read-only files
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. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD FUSE calls truncate() on read-only files
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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: FreeBSD FUSE calls truncate() on read-only files
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 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
FreeBSD FUSE calls truncate() on read-only files
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? Thanks, Lars signature.asc Description: Message signed with OpenPGP using GPGMail