On Thu, Apr 8, 2010 at 2:18 PM, Matt W. Benjamin <[email protected]> wrote:
> Hi,
>
> Simon is correct.  A byte-range locking implementation for OpenAFS is being 
> funded by Your File System, Inc., under its DOE SBIR Phase II grant.  As 
> stated elsewhere by Jeff, there are (or will be) structures for making 
> completed available to the community during the course of the work.
>
> However, my understanding that shared r/w access to sqlite through AFS 
> probably does work, provided you ensure sqlite uses the correct locking style 
> (cf. sqlite's os_unix.c):
>
> #define SQLITE_WHOLE_FILE_LOCKING  0x0001   /* Use whole-file locking */
>
> This feature is apparently due to Adam Megacz, who posted briefly about it in 
> 2006.  See http://marc.info/?l=sqlite-users&m=116742195016159&w=2 .
>
> Regards,
>
> Matt
>


Thanks for the response. It seems like whole-file locking in sqlite
would be a good choice for me in any case, and I can't imagine needing
that kind of writing concurrency.

Doing a little more research, this message describes a few more issues
with sqlite over NFS which I suppose might apply to AFS:

http://old.nabble.com/SQLite-on-NFS-cache-coherency-td15655701.html

In a situation where the whole-file locking scheme is used, would AFS
be an acceptable choice? Would it be better than NFS?

For instance I envision a handful of clients on different machines
each writing to a single sqlite DB every few seconds; would this
defeat AFS's caching scheme?

Thanks for the thoughtful responses.





> ----- "Simon Wilkinson" <[email protected]> wrote:
>
>> On 8 Apr 2010, at 12:22, Todd Lewis wrote:
>>
>
>>
>> Someone (Matt, IIRC) was working on server support for byte range
>> locking, but I don't think we've seen any code yet.
>>
>> Cheers,
>>
>> Simon.
>
> --
>
> Matt Benjamin
>
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
>
> http://linuxbox.com
>
> tel. 734-761-4689
> fax. 734-769-8938
> cel. 734-216-5309
>
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info

Reply via email to