Posting on behalf of Eric in an attempt to preserve the threading.
On Jun 28, 2005, at 9:10 AM, Eric J Haywiser wrote:
> Thanks so much for your follow-up. Unforunately, because
> it was separated from the original thread, I almost missed it. Perhaps
> you can post my response as a follow-up to the second thread you
> started. I would do this myself except that I am not a subscriber and
> don't have your original message so I don't think I can reply to the
> thread. I would hate to start a 3rd thread for this important problem.
> I was experiencing the:
> "svn failed: Can't get shared lock on file"
> problem. Your solution was the right one for me. I didn't notice any
> other NFS issues and haven't a clue how statd died or how long it has
> dead. Under RedHat one may restart statd via:
> /etc/init.d/nfslock start
> Perhaps you can post this as an additional followup to the list
> it seems like a common problem. Could spontaneous death point
> to a bug in statd?
> rpc.statd version 1.0.1
On Feb 7, 2005, at 5:37 PM, Adam Shand wrote:
> As a follow up for Google (and anyone else that's interested) ...
> I had this symptom as well and the problem was simply that statd had
> Simply restarting statd (or in my case "/etc/init.d/nfs-common
> restart") solved the problem.
>> Hi Greg,
>> Since this will quickly degenerate into an NFS mail perhaps it should
>> be off list? Then again, other might encounter the same
>> problem so I just put an [OT] warning in.
>> The NFS server is running Slackware 10 (their latest June release)
>> with a 2.6.7 kernel. It is compiled with all the NFS options
>> turned on:
>> # Network File Systems
>> And it is exported using the command:
>> /mnt/hd/ 192.168.0.0/255.255.0.0(sync,rw,no_root_squash)
>> The native file system is XFS.
>> My client is another Slackware 10 + kernel 2.6.7 system compiled with
>> # Network File Systems
>> # CONFIG_NFS_V4 is not set
>> # CONFIG_NFS_DIRECTIO is not set
>> # CONFIG_NFSD_V4 is not set
>> # CONFIG_NFSD_TCP is not set
>> # CONFIG_ROOT_NFS is not set
>> # CONFIG_RPCSEC_GSS_KRB5 is not set
>> And as I said, mounted with
>> 192.168.101.12:/mnt/hd/home/svn /data/svn-nfs-repos nfs
>> o,posix 0 0
>> Do you have any suggestions? I assume I am doing something obviously
>> wrong but I am new to this whole NFS thing.
>> It is whispered that Greg Hudson was heard, on or about 08/18/04
>> 00:30 to say:
>> >>svnadmin load /data/svn-nfs-repos/go-dev < go-dev.dmp
>> >>svn: Error opening db lockfile
>> >>svn: Can't get shared lock on file
>> '/data/svn-nfs-repos/go-dev/locks/db.lock': No locks available
>> > Although FSFS is designed to be less picky than BDB about the
>> > underlying file store, it does require the ability to perform file
>> > locking. That might change in the future, but for now it's a
>> > requirement.
>> > You didn't give much information about your NFS server platform (or
>> > the client platform); if your server is the old user-space Linux NFS
>> > server, I believe upgrading to the newer kernel nfsd might help.
>> Chris Beck / Y.A.B.A. / Fungal Genomics / Concordia University / tel.
>> ext. 5791
>> "We do not inherit the Earth from our Ancestors,
>> we borrow it from our Children."
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jun 28 01:03:25 2005