Dear list, I got some basic questions concerning how file access in Lustre works: from what I understand, Lustre clients lock file ranges with the server before executing I/O operations. What does a client get on its next I/O call in case the server needs to revoke the lock (the server can do that, right?): does the client try to re-acquire the lock, block and then time out (in case the server does not grant the lock again to that client)? TIA, Arne -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 6380 bytes Desc: S/MIME Cryptographic Signature Url : http://lists.lustre.org/pipermail/lustre-discuss/attachments/20100701/beefedc9/attachment.bin
Hi! On Thu, Jul 01, 2010 at 12:35:32PM +0200, Arne Wiebalck wrote:> I got some basic questions concerning how file access in Lustre > works: from what I understand, Lustre clients lock file > ranges with the server before executing I/O operations. What > does a client get on its next I/O call in case the server needs > to revoke the lock (the server can do that, right?): does > the client try to re-acquire the lock, block and then time > out (in case the server does not grant the lock again to that > client)?The locks protect the client-side caches, not the actual I/O. If a lock is dequeued, the client has to resynchronize (affected parts of) its cache with the server. Regards, Daniel.