[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-nfs
Subject:    [NFS] Re: Linux 2.2 client trouble after 2.4.18 server reboot
From:       Jonathan Woithe <jwoithe () physics ! adelaide ! edu ! au>
Date:       2002-07-30 7:56:24
[Download RAW message or body]

Hi Trond and others

[ NFS client troubles after server rebooted ]

> >>>>> " " == Jonathan Woithe <jwoithe@physics.adelaide.edu.au> writes:
>      > The exported directory on the server is a ReiserFS filesystem,
>      > exported with only "rw" options.  The client mounts with
>      > "hard,intr,bg" options.  NFSv3 support is not compiled in on
>      > the 2.2.19 clients.  The server is a default slackware
>      > configuration (from the point of view of NFS):
> 
> Was that ReiserFS system created on a 2.2.x system? If so, it is a
> known bug in ReiserFS itself.  There is a mount option (can't remember
> the name in the spur of the moment, but you'll find it described on
> the 'mount' manpage in www.namesys.com and you'll find it described
> several times in the NFS lists archives) that updates the filesystem
> to the latest ReiserFS format.

A few more details from tests I've done today.  Under Slackware 8.1 (what
we're using), the nfs system is shutdown with a `exportfs -au' before a
reboot.  If I carry out a stop/start cycle on the NFS system, the clients
have no problem.  It seems it only occurs across reboots - not NFS server
restarts.

Furthermore, I've found that if I do a `exportfs -a' immediately after the
server reboot then the clients are able access the NFS volume again.  And
yes, exportfs is called before rpc.mountd under Slackware 8.1.  Before the
second exportfs invocation, the /var/lib/nfs/xtab file is empty whereas it
contains details of the exported filesystems after.  I don't know if this is
relevant - but it is the only file which changes as a result of the second
call.

Does this mean that an extra `exportfs -r' (or `exportfs -a') is required
during boot to resync this, or does it indicate another problem?

In regards to the ReiserFS version, `debugreiserfs <dev>' reports a
superblock of version 3.6.

Regards
  jonathan
-- 
* Jonathan Woithe    jwoithe@physics.adelaide.edu.au                        *
*                    http://www.physics.adelaide.edu.au/~jwoithe            *
***-----------------------------------------------------------------------***
** "Time is an illusion; lunchtime doubly so"                              **
*  "...you wouldn't recognize a subtle plan if it painted itself purple and *
*   danced naked on a harpsichord singing 'subtle plans are here again'"    *


-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
[prev in list] [next in list] [prev in thread] [next in thread]