All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Vlad Apostolov <vapo@sgi.com>,
	linux-xfs@oss.sgi.com
Subject: Re: TAKE 969192: Default mount option "noikeep" makes the inode generation number non-persistent
Date: Mon, 27 Aug 2007 16:22:14 +1000	[thread overview]
Message-ID: <46D26D96.7050209@sgi.com> (raw)
In-Reply-To: <20070824124933.GS61154114@sgi.com>



David Chinner wrote:
> On Fri, Aug 24, 2007 at 12:36:31PM +0100, Christoph Hellwig wrote:
>> On Fri, Aug 24, 2007 at 02:01:30PM +1000, Vlad Apostolov wrote:
>>> To avoid the problem with identical DMAPI handles, the XFSMNT_IDELETE mount
>>> option should be set as default, only if the filesystem is not mounted with
>>> XFSMNT_DMAPI.
>> Note that we have the same problem with nfs exports aswell.  Dateo maybe we
>> need a real fix insteead and keep a block of generation numbers around even
>> if and inode cluster is freed or something similar.
> 
> Yes. NFS is less critical than dmapi, though - with NFS filehandles just a
> change in generation number is usually good enough to catch most stale
> filehandle issues. With DMAPI, there's applications that record inode
> number/generation pairs and expect them never to repeat ever again.
> 
> We haven't had any reports of probelms with NFS servers due to this,
> but as soon as our HSm was exposed to this code we started getting
> strange coherency and corruption problems that have taken some time
> to track down to this issue. Hence this change seems like the
> best tradeoff while we work out a real solution.
> 
> At this point I suspect a deleted inode cluster btree in the AGI
> is the best solution because it can share most of the btree
> code with the current AGI btree and keeps the granularity of
> shared generation numbers quite fine.

Having a persistent highest/shared generation number per inode cluster
only solves part of the problem - with only 32 bits of precision, eventually
it will wrap. Generation numbers need more precision to solve this
completely. With more precision, the starting value could simply be
based on a timestamp ...

-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------

      reply	other threads:[~2007-08-27  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  4:01 TAKE 969192: Default mount option "noikeep" makes the inode generation number non-persistent Vlad Apostolov
2007-08-24 11:36 ` Christoph Hellwig
2007-08-24 12:49   ` David Chinner
2007-08-27  6:22     ` Mark Goodwin [this message]

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=46D26D96.7050209@sgi.com \
    --to=markgw@sgi.com \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=vapo@sgi.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 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.