From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Russell King <rmk@arm.linux.org.uk>
Cc: samcconn@cotw.com (Scott A McConnell), linux-kernel@vger.kernel.org
Subject: Re: nfs_refresh_inode: inode number mismatch
Date: 23 Feb 2001 10:30:34 +0100 [thread overview]
Message-ID: <shsae7dn3ut.fsf@charged.uio.no> (raw)
In-Reply-To: <200102222159.f1MLxb031306@flint.arm.linux.org.uk>
In-Reply-To: Russell King's message of "Thu, 22 Feb 2001 21:59:37 +0000 (GMT)"
>>>>> " " == Russell King <rmk@arm.linux.org.uk> writes:
> Scott A McConnell writes:
>> I am running RedHat Linux version 2.2.16-3 on my PC and Hardhat
>> Linux version 2.4.0-test5 on my MIPS board. Any thoughts or
>> suggestions?
>>
>> I saw a discussion start on the ARM list along these lines but
>> I never saw a solution.
> The problem is partly caused by the NFS server indefinitely
> caching NFS request XIDs to responses, and the NFS client not
> having a way to generate a random initial XID. (thus, for each
> reboot, it starts at the same XID number).
That shouldn't be true in the latest kernels. knfsd should normally
cache requests for no longer than 2 minutes with the changes made by
Neil following your bugreport.
Cheers,
Trond
next prev parent reply other threads:[~2001-02-23 9:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 22:30 nfs_refresh_inode: inode number mismatch Scott A McConnell
2001-02-22 21:59 ` Russell King
2001-02-23 9:30 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 23:54 Frank Cusack
2003-06-04 14:19 ` Trond Myklebust
2003-06-04 21:20 ` Frank Cusack
2003-06-04 21:28 ` Trond Myklebust
2003-06-05 9:11 ` Adrian Cox
2003-06-05 9:13 ` Russell King
2003-06-05 13:51 ` Trond Myklebust
2001-07-17 0:24 Marco d'Itri
2001-07-17 9:44 ` Trond Myklebust
2001-07-18 22:25 ` Marco d'Itri
2001-07-19 11:00 ` Trond Myklebust
2001-02-08 1:13 Jun Sun
2001-02-08 1:22 ` Neil Brown
2001-02-08 8:08 ` Russell King
2001-02-09 0:02 ` Jun Sun
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=shsae7dn3ut.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=samcconn@cotw.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;
as well as URLs for NNTP newsgroup(s).