From: Martynas Buozis <martynas@ti.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfsroot problems on RedHat 8 with kernel linux-2.4.18-27.8.0
Date: Fri, 23 May 2003 15:39:05 +0200 [thread overview]
Message-ID: <3ECE2479.3000706@ti.com> (raw)
In-Reply-To: shs4r3lx1ux.fsf@charged.uio.no
Hello
Thank you for response. Alias this is not a case.
Disk less client gets host name via bootp. And I specify to use autoconf
to get it via bootp in kernel parameters like it is written in
nfsroot.txt. I also see, that it is configured with right IP and right
host name. These line comes before NFS mount is tried :
IP-Config: Complete:
device=eth0, addr=<correct address>, mask=255.255.255.0,
gw=<correct address>,
host=testmws, domain=, nis-domain=(none),
bootserver=<correct address>, rootserver=<correct address>, rootpath=
All entries in this configuration information are correct. The problem
is, that nfsroot module itself sends mount request without information
that is required by Celerra.
When system is booted up (same IP and host name but using another boot
tree with identical file shared on SUN/Solaris) I can mount there file
systems shared on Celerra (simple "mount cellera:/share /mnt" command)
In this case usual mount command sends all information Celerra expects
to get. So I think that problem is really in nfsroot module itself.
Maybe it is too old, because it does not support all options available
for usual command line mount command as specified in "man nfs" ?
With best regards
Martynas Buozis
Trond Myklebust wrote:
>>>>>>" " == Martynas Buozis <martynas@ti.com> writes:
>>>>>
>
> > Hello I have problems with nfsroot module when root file system
> > is shared on EMC Cellerra. The problem is, that Celerra needs
> > the
>
> > client's name and IP address to authenticate the mount
> > request. This information is usually sent through the RPC
> > authentication data. But nfsroot module does not send this data
> > during mount, so Celerra denies request. This was a conclusion
> > by EMC support after analyzing network's traffic between disk
> > less station and Celerra.
>
>
> > I was looking what can be changed in
> > /usr/src/linux-2.4/fs/nfs/nfsroot.c code, but I am not very
> > experienced in this. Maybe somebody can help me to solve this
> > problem ? Maybe that's wrong file were too look for changes ?
> > Is it possible to make changes like this and is it possible to
> > get official fix fro this problem ?
>
> Look at Documentation/nfsroot.txt and/or the comments in
> net/ipv4/ipconfig.c. That will tell you how to specify the hostname.
>
> Cheers,
> Trond
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-05-23 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 12:07 nfsroot problems on RedHat 8 with kernel linux-2.4.18-27.8.0 Martynas Buozis
2003-05-23 12:51 ` Trond Myklebust
2003-05-23 13:39 ` Martynas Buozis [this message]
2003-05-23 14:31 ` Trond Myklebust
2003-05-24 4:33 ` Martynas Buozis
2003-05-25 21:53 ` Trond Myklebust
2003-05-26 11:47 ` Martynas Buozis
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=3ECE2479.3000706@ti.com \
--to=martynas@ti.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.