public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Peter J. Braam" <braam@clusterfs.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: tmpfs, NFS, file handles
Date: 20 Feb 2002 20:42:50 +0100	[thread overview]
Message-ID: <shsk7t82b45.fsf@charged.uio.no> (raw)
In-Reply-To: <20020220094649.X25738@lustre.cfs> <3C73D548.648C5D64@mandrakesoft.com> <20020220122116.C28913@lustre.cfs>
In-Reply-To: <20020220122116.C28913@lustre.cfs>

>>>>> " " == Peter J Braam <braam@clusterfs.com> writes:

     > Would the following also work?

     > - have a 32 bit counter: set inode->i_ino to count++

That is exactly what iunique() does except that it also checks for
uniqueness and allows you to specify a minimum value. Sooner or later
your 32-bit counter will wrap round...

     > - up the generation number each time the counter warps.

     > Between boot cycles NFS could still get confused, that might be
     > helped by setting the initial generation to the system time.

Yep. That is what the 'fat' filesystem does.

Cheers,
  Trond

  reply	other threads:[~2002-02-20 19:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20 16:46 tmpfs, NFS, file handles Peter J. Braam
2002-02-20 16:56 ` Jeff Garzik
2002-02-20 19:21   ` Peter J. Braam
2002-02-20 19:42     ` Trond Myklebust [this message]
2002-02-20 22:53     ` Neil Brown
2002-02-21  4:43       ` David Chow
2002-02-21  5:04         ` Neil Brown
     [not found]           ` <3C790FB2.50503@rcn.com.hk>
2002-02-24 21:49             ` Neil Brown
2002-02-21  7:40     ` Christoph Rohland
  -- strict thread matches above, loose matches on Subject: below --
2002-02-21 16:16 Lever, Charles
2002-02-21 22:58 ` Neil Brown

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=shsk7t82b45.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=braam@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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