Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Sorry, Just noticed a second thing to reply too.. Dave Dykstra wrote: > On Tue, Jun 06, 2006 at 08:37:07PM -0700, mike wrote: > >>On 6/6/06, Montse Seisdedos <mseisdedos at mediafusion.es> wrote: >> >>>Hello everybody: >>> >>>I'm trying to built a HA nfs server in a FC4. >>> >>>I've been reading about link or not to link /var/lib/nfs to the share fs. >>>I did it, but when i try to start nfs i get the following errors >>> >>>Jun 6 11:01:17 mfs-01 exportfs[5969]: can't open /var/lib/nfs/rmtab for >>>reading >>>Jun 6 11:01:17 mfs-01 exportfs[5969]: could not open /var/lib/nfs/xtab for >>>locking >>>Jun 6 11:01:17 mfs-01 exportfs[5969]: could not open /var/lib/nfs/etab for >>>locking >>>Jun 6 11:01:17 mfs-01 exportfs[5969]: can't lock /var/lib/nfs/etab for >>>writing >>>Jun 6 11:01:17 mfs-01 exportfs[5969]: could not open /var/lib/nfs/xtab for >>>locking >>>Jun 6 11:01:17 mfs-01 exportfs[5969]: can't lock /var/lib/nfs/xtab for >>>writing >>> >>># ls -l /var/lib/nfs >>>lrwxrwxrwx 1 root root 12 jun 6 10:02 /var/lib/nfs -> /u/varlibnfs >>># ls -la /var/lib/nfs/ >>>total 120 >>>drwxr-xr-x 4 root root 4096 jun 6 10:08 . >>>drwxr-xr-x 17 root root 77824 jun 6 10:07 .. >>>-rw-r--r-- 1 root root 0 sep 27 2005 etab >>>-rw-r--r-- 1 root root 0 sep 27 2005 rmtab >>>drwxr-xr-x 2 root root 4096 sep 27 2005 rpc_pipefs >>>drwx------ 2 rpcuser rpcuser 4096 sep 27 2005 statd: >>>-rw------- 1 root root 0 s:ep 27 2005 state >>>-rw-r--r-- 1 root root 0 sep 27 2005 xtab > > > I think those errors show that you must not be properly stopping and > starting all the nfs services. I'm not very familiar with what the > packages are called in FC4, but please post your haresources file and > hopefully someone can point out what's wrong with it. You should only > be attempting to access the shared /var/lib/nfs files on the machine > that's the active server and so that directory should be available. > > > <SNIP> I have a heartbeat 1.2.x and drbd 0.6.x on an FC 1 system... the general order in haresources for my systems is setup the IP go primary on the drbd resource and mount it start nfslock start nfs i.e. foobar IPaddr::192.168.192.87 \ datadisk::nfsstate \ datadisk::cm \ nfslock \ nfs \ IIRC, with a 0.7.x drbd you need to do the "go primary" and "mount it" in two steps, using the new drbd script and the heartbeat filesystem script. Like Dave said, "You should only be attempting to access the shared /var/lib/nfs files on the machine that's the active server", so I would suggest checking the state of your nfs and nfslock services, i.e., chkconfig for nfs and nfslock should look like: # chkconfig --list nfs nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off # chkconfig --list nfslock nfslock 0:off 1:off 2:off 3:off 4:off 5:off 6:off -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter