From: Neil Brown <neilb@cse.unsw.edu.au>
To: "Michael J. Dikkema" <mjd@moot.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 question (fh_lock_parent)
Date: Wed, 20 Dec 2000 08:24:32 +1100 (EST) [thread overview]
Message-ID: <14911.53776.854761.710519@notabene.cse.unsw.edu.au> (raw)
In-Reply-To: message from Michael J. Dikkema on Tuesday December 19
In-Reply-To: <Pine.LNX.4.21.0012190929280.637-100000@sliver.moot.ca>
On Tuesday December 19, mjd@moot.ca wrote:
>
> I've been getting tonnes of these since I installed 2.2.18. Is this a
> problem? Should I even worry about this? If I don't need to worry about
> it, is there a way to stop displaying this message?
>
> fh_lock_parent: mqueue/xfBAA14279 parent changed or child unhashed
> fh_lock_parent: mqueue/xfBAA16413 parent changed or child unhashed
You are running sendmail on an NFS client with /var/spool mounted off
the NFS server which is giving these message - right?
These messages tend to indicate a race between two different NFS
requests that try to do something to the one file - probably unlink
it, though possibly rename it.
If everything is configured properly (e.g. you don't have two
different sendmails on two different clients trying to use the one
shared spool area), then this would seem to imply that the server is
responding more slowly that the client would like, and the client is
resending the unlink (or whatever) request and so there are two
identical requests being served by the NFS server and they race.
So it is hard to be sure if you should worry about this.
Maybe if you tell us what you are trying to do (i.e. confirm the
configuration of sendmail, NFS mounts and the number of clients.
Also, how frequent is this? Would you be able to get a tcpdump of a
few hundred packets either side of the message? If you do try this,
make sure that you use a large snap-length for tcpdump (-s 1024) to
get the whole nfs packet.
NeilBrown
>
> ,.;::
> : Michael J. Dikkema
> | Systems / Network Admin - Internet Solutions, Inc.
> | http://www.moot.ca Work: (204) 982-1060
> ; mjd@moot.ca
> ',.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-19 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 15:30 2.2.18 question (fh_lock_parent) Michael J. Dikkema
2000-12-19 21:24 ` Neil Brown [this message]
2000-12-20 15:44 ` Michael J. Dikkema
2000-12-20 17:52 ` Michael J. Dikkema
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=14911.53776.854761.710519@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mjd@moot.ca \
/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;
as well as URLs for NNTP newsgroup(s).