#9400: flock causes problems when writing to an NFS share
---------------------------------------------+------------------------------
Reporter: mikeh | Owner: nobody
Status: new | Milestone:
Component: File uploads/storage | Version: 1.0
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by dougvanhorn):
I was just bitten by this issue (Error 37). However, it was caused by the
__NFS 3 Client__ not having a running nfslock service ($ sudo
/sbin/service nfslock start)
My system and NFS:
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
Linux 2.6.18-164.15.1.el5 #1 SMP Mon Mar 1 10:56:08 EST 2010 x86_64 x86_64
x86_64 GNU/Linux
nfs-utils.x86_64 1:1.0.9-42.el5
As an FYI, NFS 2 and NFS 3 require the third party locking service,
whereas NFS 4 has locking built into the protocol.
I'll attach a small script which tests the locking behavior directly, so
you can run the script while testing your NFS configuration. It's a cut
and paste of the locks behavior as of 1.2.1.
--
Ticket URL: <http://code.djangoproject.com/ticket/9400#comment:8>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
