From: James Pearson <james-p@moving-picture.com>
To: Donald Burns <DMB@reliance.co.uk>
Cc: "'nfs@lists.sourceforge.net'" <nfs@lists.sourceforge.net>
Subject: Re: Problems with hard links in root NFS filesystem
Date: Thu, 01 Aug 2002 12:51:22 +0100 [thread overview]
Message-ID: <3D4920BA.6685567E@moving-picture.com> (raw)
In-Reply-To: F418066D6DFA5040A1169F0B39B7604A0DE23D@rg273.reliance.co.uk
What options are you using to export the file systems from the server?
Are you using 'no_subtree_check' ?
Using no_subtree_check fixed a similar problem I had - see:
http://marc.theaimsgroup.com/?l=linux-nfs&m=101309591431249&w=2
James Pearson
Donald Burns wrote:
>
>
> Dear list members,
>
> I have a problem using NFS.
>
> Synopsis: Files that are hard linked on the server's root
> NFS images for a Beowulf cluster become inaccesable
> either imediately or after a few hours.
>
> Boot example: From the server's logs (server is rg272) :-
>
> July 30 10:05:45 rg272 kernel: nfsd Security: sbin/init bad
> export.
> July 30 10:05:46 rg272 kernel: nfsd Security: sbin/bash bad
> export.
>
> The client boot-up hangs at this point.
>
> After time example: From the server's logs (as I remember it):-
>
> July 30 11:34:02 rg272 kernel: nfsd Security:
> lib/libc6.x.x.so bad export.
>
> Client example: From the command line:-
>
> cat /etc/inittab
> cat: standard output: Stale NFS file handle
>
> Other symptoms:
>
> When booting the cluster each machine must be booted
> on its own. Booting the machines in parallel fills the
> servers logs with "bad export" messages.
>
> Problem exists irrespective of NFS protocol
> used (V2 or V3)
>
> Cycling the power on the server clears the problem
> temporarily but restarting the NFS service does not.
>
> System Details:
>
> Software:- Linux RedHat 7.3 on server and clients
> (kernel 2.4.18)
> Server:- Dell GX530 dual processor precision work
> station.
> Clients:- Dell GX260 single processor work station.
>
> Progress in solving the problem to date:
>
> By trawling the web I found one Gunnar Raetch who
> experianced almost identical problems using kernel
> 2.4.14. He fixed the problem by applying the
> following kernel patches:-
>
> http://www.cse.unsw.edu.au/~neilb/patches/linux/2.4.14-pre4/
>
> patch-D-NfsdOpsPrepare
> patch-E-NfsdOps
> patch-F-ReiserfsNfsdOps
>
> I am unable patch my 2.4.18 kernel with these patches.
> I also tried down grading to kernel 2.4.14, successfully
> applied the patches & compiled, but the USB support
> in 2.4.14 would not allow me use of my mouse and keyboard
> (Oh Sh*t!).
>
> I hope this provides sufficient info to resolve the problem.
>
> Many thanks in advance for your anticipated kind help.
>
> Best Regards,
>
> Donald.
>
> Reliance Gear Company Ltd.
> Rowley Mills
> Penistone Road
> Lepton
> Huddersfield
> England
> HD8 0LE
>
> Tel: +44 1484 601000
> fax: +44 1484 601001
>
> http://www.reliance.co.uk
>
> THE INFORMATION IN THIS COMMUNICATION IS CONFIDENTIAL AND INTENDED ONLY FOR
> THE USE OF THE ADDRESSEE. DISCLOSURE, USE OR COPYING OF THIS MESSAGE OR
> ITS CONTENTS OTHER THAN BY THE ADDRESSEE IS PROHIBITED. IF YOU RECEIVE THIS
> COMMUNICATION IN ERROR WE WOULD BE GRATEFUL IF YOU WOULD NOTIFY US
> IMMEDIATELY AND DELETE ANY MATERIAL RECEIVED
>
> -------------------------------------------------------
> 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:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-08-01 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 11:20 Problems with hard links in root NFS filesystem Donald Burns
2002-08-01 11:51 ` James Pearson [this message]
2002-08-01 12:01 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 9:05 Donald Burns
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=3D4920BA.6685567E@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=DMB@reliance.co.uk \
--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.