Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-08-02 Thread Junio C Hamano
Duy Nguyen writes: > OK how about this squashed in? The name was taken from fbsd definition > IN_LAZYMOD. I am sorry that I didn't spot this possiblity earlier, but do we need anything conditional? Either FREEBSD or LAZYMOD prerequisite tells very little what the "Work

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-08-02 Thread Duy Nguyen
On Mon, Aug 01, 2016 at 02:04:44PM -0700, Junio C Hamano wrote: > Duy Nguyen writes: > > > On Mon, Aug 1, 2016 at 3:37 AM, Torstem Bögershausen wrote: > >> the term FREEBSD may be too generic to point out a single feature > >> in an OS distributution. > >>

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-08-01 Thread Junio C Hamano
Duy Nguyen writes: > On Mon, Aug 1, 2016 at 3:37 AM, Torstem Bögershausen wrote: >> the term FREEBSD may be too generic to point out a single feature >> in an OS distributution. >> Following your investigations, it may even be possible that >> other systems

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-08-01 Thread Duy Nguyen
On Mon, Aug 1, 2016 at 3:37 AM, Torstem Bögershausen wrote: > the term FREEBSD may be too generic to point out a single feature > in an OS distributution. > Following your investigations, it may even be possible that > other systems adapt this "feature"? > > How about >

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-07-31 Thread Torstem Bögershausen
> Am 30.07.2016 um 15:20 schrieb Nguyễn Thái Ngọc Duy : > > Let's start with the commit message of [1] from freebsd.git [2] > >Sync timestamp changes for inodes of special files to disk as late >as possible (when the inode is reclaimed). Temporarily only do >

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-07-31 Thread Duy Nguyen
On Sun, Jul 31, 2016 at 3:07 AM, Eric Wong wrote: >> would be more to the point of what is going on, here. But I >> also wonder if untracked cache itself could/should be doing this >> internally. > > Still wondering :> There's nothing we can do besides maybe run a cron job

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-07-30 Thread Eric Wong
Eric Wong wrote: > Nguyễn Thái Ngọc Duy wrote: > > +test_expect_success FREEBSD 'Work around lazy mtime update' ' > > + ls -ld . >/dev/null > > +' > > stat . >/dev/null If there's some older FreeBSD w/o stat(1); "test -x ." ought to work, too, and

Re: [PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-07-30 Thread Eric Wong
Nguyễn Thái Ngọc Duy wrote: > Let's start with the commit message of [1] from freebsd.git [2] > > Sync timestamp changes for inodes of special files to disk as late > as possible (when the inode is reclaimed). Temporarily only do > this if option UFS_LAZYMOD

[PATCH] t7063: work around FreeBSD's lazy mtime update feature

2016-07-30 Thread Nguyễn Thái Ngọc Duy
Let's start with the commit message of [1] from freebsd.git [2] Sync timestamp changes for inodes of special files to disk as late as possible (when the inode is reclaimed). Temporarily only do this if option UFS_LAZYMOD configured and softupdates aren't enabled. UFS_LAZYMOD is