From: James Pearson <james-p@moving-picture.com>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: nfs@lists.sourceforge.net
Subject: Re: Linux 2.2 client trouble after 2.4.18 server reboot
Date: Mon, 29 Jul 2002 11:55:31 +0100 [thread overview]
Message-ID: <3D451F23.92E4DA72@moving-picture.com> (raw)
In-Reply-To: 200207290021.g6T0LLL22541@sprite.physics.adelaide.edu.au
Have a look through the archives of this list at:
http://marc.theaimsgroup.com/?l=linux-nfs&r=1&w=2
It could be similar to the problem reported in thread:
http://marc.theaimsgroup.com/?l=linux-nfs&m=101796943306978&w=2
James Pearson
Jonathan Woithe wrote:
>
> Hi all
>
> [Please CC me replies since I'm not subscribed to this list]
>
> Recently I upgraded our NFS server to Linux 2.4.18. This server provides
> exported home directories for our user Linux boxes which are currently
> running 2.2.19.
>
> Most of the time everything seems to be going well. However, if the server
> is rebooted the clients seem unable to restore the NFS connection to a
> usable state. The logs note the server becoming unavailable and then
> following the reboot they note that the server is now "ok". However, any
> attempt to then access the mounted volumes is greeted with a "permission
> denied" error. Even root can't access the drives.
>
> If the NFS volumes are unmounted and remounted the problem (predictably)
> goes away. Of course such an unmount can't occur until people have logged
> off, which makes it a little cumbersome.
>
> 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):
> CONFIG_NFS_FS=y
> CONFIG_NFS_V3=y
> # CONFIG_ROOT_NFS is not set
> CONFIG_NFSD=m
> CONFIG_NFSD_V3=y
> CONFIG_SUNRPC=y
> CONFIG_LOCKD=y
> CONFIG_LOCKD_V4=y
> The server also has the lockd oops fix from Trond.
>
> I would appreciate any pointers to ways to stop this from happening.
> Requiring that all users log out before a server reboot is rather
> inconvenient.
>
> Best 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:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
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
next prev parent reply other threads:[~2002-07-29 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 0:21 Linux 2.2 client trouble after 2.4.18 server reboot Jonathan Woithe
2002-07-29 10:55 ` James Pearson [this message]
2002-07-29 13:01 ` Weird error with nfs server and an embedded linux system Sampo Nurmentaus
2002-07-29 13:14 ` Trond Myklebust
2002-07-29 14:11 ` Sampo Nurmentaus
2002-08-12 23:44 ` Linux 2.2 client trouble after 2.4.18 server reboot Jonathan Woithe
2002-07-29 11:05 ` Trond Myklebust
2002-07-29 23:30 ` Jonathan Woithe
2002-07-30 7:44 ` Jonathan Woithe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D451F23.92E4DA72@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.