Re: ext4 features

Bill Davidsen
2006-07-08T21:02:14Z

Trond Myklebust wrote:
> On Wed, 2006-07-05 at 17:22 -0400, Bill Davidsen wrote:
>> Consider the case where the build machine reads source from one network
>> filesystem and write the binary result to another on another machine. If
>> you know that I have the kernel source on a file server, do the compiles
>> on a compute server, and store the binaries on three test machines for
>> evaluation, you might guess this really can happen. Just increasing the
>> timestamp may not solve the problem, unless you have a system call to
>> set timestamp over network f/s, like a high resolution touch.
>
> If you are running 'touch' manually on all your files, you can always
> arrange to set the timestamp to something more recent. You don't
> normally need a high resolution version of utimes() (and SuSv3 won't
> provide you with one).

No, I didn't quite mean a manual touch, but a system call to "close and
set time to high resolution" for files where time uniformity is
important. Consider that in most cases the inodes times are set by the
host machine clock, which I close the change reflects the fileserving
host idea of time. If there were a call to close a file and set the
times like touch, then that could be used, for both local and network files.

Clearly if multiple clients are changing the same file that doesn't
work, and I doubt that any solution is going to avoid at least some
undesired side effects.

--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.