From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Subject: Re: Does NFS4 need st_gen?
Date: Thu, 20 Oct 2011 15:57:31 -0400 [thread overview]
Message-ID: <20111020195731.GC9987@fieldses.org> (raw)
In-Reply-To: <877h3za89w.fsf@inspiron.ap.columbia.edu>
On Thu, Oct 20, 2011 at 01:21:31PM -0400, Nikolaus Rath wrote:
> I'm working on a FUSE file system that stores file system metadata in an
> SQL database (http://code.google.com/p/s3ql/). Not having to keep track
> of inode generation numbers would keep the code much simpler, because I
> want to delete inode-rows from the SQL table when the last reference to
> the inode is deleted (so I can't keep track of the generation no).
You can use current time, or a counter, or something, as the generation
number.
> Now I'll either have to make inodes unique (and run into trouble after
> 2^32 inodes have been used), or keep with the current scheme of
> randomizing new inodes (which keeps the probability of problems low
> enough but is ugly).
With 2^32 inode numbers plus 2^32 generation numbers it should be
possible to work something out that doesn't require remembering every
old inode.
--b.
next prev parent reply other threads:[~2011-10-20 19:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-19 14:17 Does NFS4 need st_gen? Nikolaus Rath
2011-10-19 17:15 ` J. Bruce Fields
2011-10-19 19:11 ` Nikolaus Rath
2011-10-20 12:02 ` J. Bruce Fields
2011-10-20 17:21 ` Nikolaus Rath
2011-10-20 19:57 ` J. Bruce Fields [this message]
2011-10-20 20:37 ` Nikolaus Rath
2011-10-21 0:07 ` Trond Myklebust
2011-10-21 13:54 ` Nikolaus Rath
2011-10-21 16:00 ` Trond Myklebust
2011-10-21 16:09 ` Nikolaus Rath
2011-10-21 17:10 ` Trond Myklebust
2011-10-21 17:44 ` Nikolaus Rath
2011-10-22 18:47 ` Boaz Harrosh
2011-10-22 18:59 ` Boaz Harrosh
2011-10-22 20:10 ` Nikolaus Rath
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=20111020195731.GC9987@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.