From: David Ford <david+cert@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: NFS woes continued, 2.5.59 v.s. 2.5.61
Date: Fri, 21 Feb 2003 22:30:32 -0500 [thread overview]
Message-ID: <3E56EED8.8070301@blue-labs.org> (raw)
Shell -> 2.5.59, serves /home/xxxxx to web/mail server
W/Mail -> 2.5.61, client for /home/xxxx, serves other directories to two
other clients
Clients, 2.5.61 and 2.5.56, these load the W/Mail exported directories fine.
The /home/xxxx mounts exported by Shell for W/Mail are the problem.
2.5.59 -> 2.5.61. Worked fine up until today.
Shell syslog:
Feb 21 22:16:30 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:749 for /home/james (/home/james)
Feb 21 22:16:41 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:753 for /home/hnc (/home/hnc)
Feb 21 22:16:51 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:757 for /home/hnc (/home/hnc)
Feb 21 22:17:02 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:761 for /home/securitynerds (/home/securitynerds)
Feb 21 22:17:13 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:765 for /home/securitynerds (/home/securitynerds)
Feb 21 22:17:23 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:769 for /home/m2k (/home/m2k)
Feb 21 22:17:34 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:773 for /home/m2k (/home/m2k)
Feb 21 22:17:44 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:777 for /home/nexpedition (/home/nexpedition)
Feb 21 22:17:55 james rpc.mountd: authenticated mount request from
mail.blue-labs.org:781 for /home/nexpedition (/home/nexpedition)
[.....]
W/Mail:
# mount -t nfs -a
mount: wrong fs type, bad option, bad superblock on james:/home/james,
or too many mounted file systems
mount: wrong fs type, bad option, bad superblock on james:/home/hnc,
or too many mounted file systems
mount: wrong fs type, bad option, bad superblock on
james:/home/securitynerds,
or too many mounted file systems
mount: wrong fs type, bad option, bad superblock on james:/home/m2k,
or too many mounted file systems
mount: wrong fs type, bad option, bad superblock on james:/home/nexpedition,
or too many mounted file systems
syslog:
nfs_get_root: getattr error = 5
nfs_read_super: get root inode failed
nfs: server james not responding, timed out
nfs_get_root: getattr error = 5
nfs_read_super: get root inode failed
nfs warning: mount version older than kernel
nfs: server james not responding, timed out
nfs_get_root: getattr error = 5
nfs_read_super: get root inode failed
nfs: server james not responding, timed out
nfs_get_root: getattr error = 5
nfs_read_super: get root inode failed
nfs warning: mount version older than kernel
nfs: server james not responding, timed out
nfs_get_root: getattr error = 5
nfs_read_super: get root inode failed
nfs: server james not responding, timed out
nfs_get_root: getattr error = 5
nfs_read_super: get root inode failed
nfs warning: mount version older than kernel
nfs: server james not responding, timed out
[....]
2.5.62 is a no-go, OOPS on boot. I've had too much NFS frustration to
deal with yet another problem so I haven't posted that OOPS yet.
This NFS issue is pretty important to me since it's a 100% fault
condition, not a once in a while.
Make that 2.5.61 is also broken (OOPS) on boot. FSCK.
Ok, trying .60.
David
reply other threads:[~2003-02-22 3:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E56EED8.8070301@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox