linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael J. Dikkema" <mjd@moot.ca>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 question (fh_lock_parent)
Date: Wed, 20 Dec 2000 09:44:27 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0012200939180.7919-100000@sliver.moot.ca> (raw)
In-Reply-To: <14911.53776.854761.710519@notabene.cse.unsw.edu.au>

On Wed, 20 Dec 2000, Neil Brown wrote:

> 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.

That's what you'd think. All these machines have a drive mounted on
/var.

[root@www /root]# df
Filesystem           1k-blocks      Used Available Use% Mounted on
10.0.0.10:/nfsroot    34020868  24061800   8230876  75% /
/dev/sda1              8744304   1473776   6826336  18% /var

I've checked to see if mtab was lying to me, and it's not.. I can unmount
and remount the drive on /var.. 

The system runs with one nfs server, and 4 children, all using nfs
root. They all mount /dev/sda1 on /var. Yet for some reason I get these
messages. I went from 2.2.16 -> 2.2.18 without changing anything but the
kernel. Has something changed? This doesn't look right to me at all.



,.;::
: 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/

  reply	other threads:[~2000-12-20 16:15 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
2000-12-20 15:44   ` Michael J. Dikkema [this message]
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=Pine.LNX.4.21.0012200939180.7919-100000@sliver.moot.ca \
    --to=mjd@moot.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    /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).