From: Dong Liu <dliu@npiww.com>
To: Honza Pazdziora <adelton@informatics.muni.cz>
Cc: linux@cthulhu.engr.sgi.com
Subject: Message while mounting NFS
Date: Thu, 16 Jul 1998 13:38:11 -0400 [thread overview]
Message-ID: <199807161738.NAA17076@pluto.npiww.com> (raw)
In-Reply-To: <199807161709.TAA15707@aisa.fi.muni.cz>
Honza Pazdziora writes:
>
> Hello,
>
> These messages run accross console and go to syslog when I mount
> NFS disk from remote host:
>
> Jul 16 17:04:33 nemesis kernel: lockd_up: no pid, 2 users??
> Jul 16 17:04:38 nemesis kernel: portmap: RPC call returned error 146
> Jul 16 17:04:38 nemesis kernel: RPC: task of released request still queued!
> Jul 16 17:04:38 nemesis kernel: RPC: (task is on xprt_pending)
> Jul 16 17:04:43 nemesis kernel: portmap: RPC call returned error 146
> Jul 16 17:04:43 nemesis kernel: RPC: task of released request still queued!
> Jul 16 17:04:43 nemesis kernel: RPC: (task is on xprt_pending)
> Jul 16 17:04:43 nemesis kernel: lockd_up: makesock failed, error=-146
> Jul 16 17:04:48 nemesis kernel: portmap: RPC call returned error 146
> Jul 16 17:04:48 nemesis kernel: RPC: task of released request still queued!
> Jul 16 17:04:48 nemesis kernel: RPC: (task is on xprt_pending)
>
> The filesystem is however mounted and further works OK. The remote
> system is Solaris 2.5.1.
>
I think this is a bug of red hat system (BTW, where I can send them this bug
report?), portmapper is started after nfsfs, it should be started before
nfsfs.
Dong
next prev parent reply other threads:[~1998-07-16 17:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-14 23:38 The pre-release of Hard Hat Linux for SGI Alex deVries
1998-07-15 4:52 ` ralf
1998-07-15 6:05 ` Alex deVries
1998-07-15 9:00 ` Honza Pazdziora
1998-07-15 9:00 ` Honza Pazdziora
1998-07-15 15:26 ` ralf
1998-07-15 20:15 ` Alex deVries
1998-07-15 23:09 ` ralf
1998-07-15 20:17 ` Honza Pazdziora
1998-07-15 20:17 ` Honza Pazdziora
1998-07-15 21:07 ` Alex deVries
1998-07-15 22:13 ` Alex deVries
1998-07-16 7:23 ` Honza Pazdziora
1998-07-16 7:23 ` Honza Pazdziora
1998-07-16 9:02 ` Oliver Frommel
1998-07-16 13:54 ` Honza Pazdziora
1998-07-16 13:54 ` Honza Pazdziora
1998-07-16 14:12 ` Alex deVries
1998-07-16 14:39 ` Honza Pazdziora
1998-07-16 14:39 ` Honza Pazdziora
1998-07-16 16:17 ` Installing noarch packages Honza Pazdziora
1998-07-16 16:17 ` Honza Pazdziora
1998-07-16 16:24 ` Honza Pazdziora
1998-07-16 16:24 ` Honza Pazdziora
1998-07-16 17:09 ` Message while mounting NFS Honza Pazdziora
1998-07-16 17:13 ` Alex deVries
1998-07-16 17:38 ` Dong Liu [this message]
1998-07-17 5:28 ` Alex deVries
1998-07-17 7:50 ` Honza Pazdziora
1998-07-17 7:50 ` Honza Pazdziora
1998-07-17 17:13 ` Alex deVries
1998-07-17 16:03 ` Dong Liu
1998-07-16 17:49 ` Matthew Kirkwood
1998-07-16 18:10 ` Installing noarch packages Alex deVries
1998-07-17 7:16 ` Honza Pazdziora
1998-07-17 7:16 ` Honza Pazdziora
1998-07-17 17:12 ` Alex deVries
1998-07-16 14:28 ` The pre-release of Hard Hat Linux for SGI ralf
1998-07-16 14:35 ` Honza Pazdziora
1998-07-16 17:04 ` Some register dumps Honza Pazdziora
1998-07-15 21:42 ` The pre-release of Hard Hat Linux for SGI Thomas Bogendoerfer
[not found] <35AE3661.2E1A7F2F@detroit.sgi.com>
1998-07-17 7:54 ` Message while mounting NFS Honza Pazdziora
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=199807161738.NAA17076@pluto.npiww.com \
--to=dliu@npiww.com \
--cc=adelton@informatics.muni.cz \
--cc=linux@cthulhu.engr.sgi.com \
/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