linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Adrian Cox <adrian@humboldt.co.uk>
Cc: Frank Cusack <fcusack@fcusack.com>,
	trond.myklebust@fys.uio.no, linux-kernel@vger.kernel.org
Subject: Re: nfs_refresh_inode: inode number mismatch
Date: Thu, 5 Jun 2003 10:13:51 +0100	[thread overview]
Message-ID: <20030605101351.C960@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030605101120.2bea125a.adrian@humboldt.co.uk>; from adrian@humboldt.co.uk on Thu, Jun 05, 2003 at 10:11:20AM +0100

On Thu, Jun 05, 2003 at 10:11:20AM +0100, Adrian Cox wrote:
> There's a very common cause on embedded boards that don't have
> real-time clocks. Without a clock the client uses the same XID on every
> run, leading to lots of these messages. Is your clock broken?

BTDT.

If this is the case, you need to ensure that you don't reboot the client
before the servers XID cache times out the XID numbers.  For Linux knfsd,
that's around 2 minutes.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-06-05  9:00 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 23:54 nfs_refresh_inode: inode number mismatch 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-09 13:51       ` [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch) Frank Cusack
2003-06-09 13:55         ` Frank Cusack
2003-06-09 15:53         ` Linus Torvalds
2003-06-09 16:40           ` Trond Myklebust
2003-06-09 20:46             ` Frank Cusack
2003-06-10  0:01               ` Trond Myklebust
2003-06-11  0:54         ` viro
2003-06-11  1:28           ` Frank Cusack
2003-06-11  1:47             ` viro
2003-06-11  2:32               ` Frank Cusack
2003-06-11  2:37                 ` viro
2003-06-11  1:59           ` Trond Myklebust
2003-06-11  2:27             ` viro
2003-06-11  2:43               ` Frank Cusack
2003-06-11  2:50                 ` Frank Cusack
2003-06-11  3:00                 ` viro
2003-06-11  7:22                   ` [PATCH] NFS sillyrename fixes (was: [PATCH] nfs_unlink() race) Frank Cusack
2003-06-13  0:19                     ` [PATCH] NFS sillyrename fixes take 3 Frank Cusack
2003-06-11  3:00               ` [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch) Trond Myklebust
2003-06-11  5:30           ` Linus Torvalds
2003-06-11  6:16             ` Andreas Dilger
2003-06-11 12:33             ` Alan Cox
2003-06-11 15:08               ` Linus Torvalds
2003-06-11 15:51                 ` Alan Cox
2003-06-11 16:11                   ` Linus Torvalds
2003-06-11 16:21                     ` Alan Cox
2003-06-11 16:31                       ` Linus Torvalds
2003-06-11 16:34                         ` viro
2003-06-11 17:22                         ` Alan Cox
2003-06-11 17:37                           ` Trond Myklebust
2003-06-11 17:47                             ` Trond Myklebust
2003-06-12 21:59                               ` Jan Harkes
     [not found]                             ` <16103.29804.198545.680701@charged.uio.no>
2003-06-11 22:24                               ` Frank Cusack
2003-06-11 23:16                                 ` Trond Myklebust
2003-06-11 23:35                                   ` [PATCH] nfs_unlink() race Frank Cusack
2003-06-05  9:11     ` nfs_refresh_inode: inode number mismatch Adrian Cox
2003-06-05  9:13       ` Russell King [this message]
2003-06-05 13:51         ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
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-22 22:30 Scott A McConnell
2001-02-22 21:59 ` Russell King
2001-02-23  9:30   ` 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=20030605101351.C960@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=adrian@humboldt.co.uk \
    --cc=fcusack@fcusack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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).