On Tue, Jun 03, 2003 at 02:33:45PM +0100, Edward Hibbert wrote:
>
> Our application consists of a number of machines collaborating on a shared
> database over NFS. We therefore require the ability to force data to be
> sync'd from the client to the backend - and at the moment we do this by
> disabling caching completely, via the noac option and acquiring and
> releasing non-exclusive locks round io calls.
>
> Any improvements in the granularity of control over NFS client-side caching
> would be very valuable to us.
To disable ac for a single directory for a certain amount of time, see
http://web.inter.nl.net/users/fvm/nfs-noac/2.4.20-noac-timeout.patch
http://web.inter.nl.net/users/fvm/nfs-noac/readme:
This patch implements /proc/sys/net/nfs/noac-timeout
When a nonzero value is written, suspend atribute caching for the current
working directory and one level of files inside for the specified number
of seconds. Attribute caching will automatically be enabled when the time
elapses. Writing a zero re-enables attribute caching as well. Reading
yields the number of remaining seconds attribute caching will be disabled.
Maybe an NFS specific ioctl would be cleaner. But the above patch can be
used even from simple scripts.
-- Frank - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 07 2003 - 22:00:20 EST