Re: How do I get NFS locking to work?
On Thu, Dec 14, 2006 at 12:18:27PM -0500, hendrik@topoi.pooq.com wrote:
> How do I get NFS locking to work? (And why doesn't it "just work"
> anyway?)
>
> I am unable to use monotone properly over an NFS mount because it very
> sensibly tries to lock its repository before modifying it.
>
> My only clue to the problem is messages that keep being reported by
> logcheck:
>
> > Security Events
> > =-=-=-=-=-=-=-=
> > Dec 11 12:15:34 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> > Dec 11 12:15:34 lovesong kernel: lockd: failed to monitor 172.25.1.11
> > Dec 11 12:15:34 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
> > Dec 11 12:15:34 lovesong kernel: lockd: failed to monitor 172.25.1.11
These are messages from before I installed the new kernel yesterday.
But I'm still getting them today:
Dec 14 12:21:56 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
Dec 14 12:21:56 lovesong kernel: lockd: failed to monitor 172.25.1.11
Dec 14 12:31:35 lovesong kernel: nsm_mon_unmon: rpc failed, status=-13
Dec 14 12:31:35 lovesong kernel: lockd: failed to monitor 172.25.1.11
The status-reports below were generated today. after yestarday's kernel
upgrade.
-- hendrik
>
> etc. etc.
>
> I have not installed a firewall between the two machines.
>
> The server is 172.25.1.11, aka "april", an AMD-64 runnin etch (updated
> yesterday)
> I have installed the nfs-kernel-server package, version 1:1.0.10-4
>
> The client is 32-bet AMD machine running sarge.
>
> Here's the output of some status-reporting commands, in case they might
> be useful. Should I provide anything else?
>
> april:/farhome/hendrik# lsmod
> Module Size Used by
> iptable_filter 7808 0
> ip_tables 25192 1 iptable_filter
> x_tables 22024 1 ip_tables
> nfs 236216 0
> ipv6 285664 14
> nfsd 256200 17
> exportfs 10368 1 nfsd
> lockd 67600 3 nfs,nfsd
> nfs_acl 8320 2 nfs,nfsd
> sunrpc 166984 13 nfs,nfsd,lockd,nfs_acl
> ppdev 14088 0
> lp 17736 0
> ide_generic 5760 0 [permanent]
> i2c_nforce2 12544 0
> i2c_core 27776 1 i2c_nforce2
> floppy 67112 0
> snd_hda_intel 23708 0
> snd_hda_codec 184192 1 snd_hda_intel
> psmouse 44432 0
> tsdev 13056 0
> snd_pcm 88968 2 snd_hda_intel,snd_hda_codec
> snd_timer 29192 1 snd_pcm
> snd 65256 4
> snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
> soundcore 15392 1 snd
> snd_page_alloc 14864 2 snd_hda_intel,snd_pcm
> parport_pc 41640 1
> parport 44684 3 ppdev,lp,parport_pc
> serio_raw 12036 0
> pcspkr 7808 0
> evdev 15360 1
> reiserfs 231168 3
> dm_mirror 25216 0
> dm_snapshot 20536 0
> dm_mod 62800 7 dm_mirror,dm_snapshot
> raid1 26880 1
> md_mod 82844 2 raid1
> ide_cd 45088 0
> cdrom 40488 1 ide_cd
> ide_disk 20608 7
> usbhid 45088 0
> sata_nv 17412 0
> libata 106784 1 sata_nv
> scsi_mod 152880 1 libata
> amd74xx 19504 0 [permanent]
> forcedeth 46212 0
> generic 10756 0 [permanent]
> ide_core 147584 5
> ide_generic,ide_cd,ide_disk,amd74xx,generic
> ehci_hcd 36104 0
> ohci_hcd 24836 0
> thermal 20240 0
> processor 38248 1 thermal
> fan 9864 0
> april:/farhome/hendrik#
>
>
> and output from rpcinfo:
> april:/farhome/hendrik# rpcinfo -p
> program vers proto port
> 100000 2 tcp 111 portmapper
> 100000 2 udp 111 portmapper
> 100003 2 udp 2049 nfs
> 100003 3 udp 2049 nfs
> 100003 4 udp 2049 nfs
> 100003 2 tcp 2049 nfs
> 100003 3 tcp 2049 nfs
> 100003 4 tcp 2049 nfs
> 100021 1 udp 32768 nlockmgr
> 100021 3 udp 32768 nlockmgr
> 100021 4 udp 32768 nlockmgr
> 100021 1 tcp 54008 nlockmgr
> 100021 3 tcp 54008 nlockmgr
> 100021 4 tcp 54008 nlockmgr
> 100005 1 udp 905 mountd
> 100005 1 tcp 908 mountd
> 100005 2 udp 905 mountd
> 100005 2 tcp 908 mountd
> 100005 3 udp 905 mountd
> 100005 3 tcp 908 mountd
> 391002 2 tcp 642 sgi_fam
> 100024 1 udp 32770 status
> 100024 1 tcp 45918 status
> april:/farhome/hendrik#
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: