From: Adam Schrotenboer <adam@m2000.com>
To: David Chinner <dgc@sgi.com>
Cc: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>,
NeilBrown <neilb@suse.de>,
"J. Bruce Fields" <bfields@fieldses.org>,
xfs@oss.sgi.com, Jesper Juhl <jesper.juhl@gmail.com>,
Trond Myklebust <trond.myklebust@netapp.com>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Thomas Daniel <tdaniel@m2000.com>,
Frederic Revenu <frevenu@m2000.com>, Jeff Doan <jdoan@m2000.com>
Subject: Re: [opensuse] nfs_update_inode: inode X mode changed, Y to Z
Date: Thu, 17 Apr 2008 12:37:12 -0700 [thread overview]
Message-ID: <4807A6E8.6010102@m2000.com> (raw)
In-Reply-To: <20080326050208.GH108924158@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
David Chinner wrote:
> On Wed, Mar 26, 2008 at 02:37:38PM +1100, David Chinner wrote:
>
>> Given this state of affairs (i.e. HSM using ikeep), I guess we can do
>> anything we want for the noikeep case. I'll cook up a patch that does
>> something similar to ext3 generation numbers for the initial seeding....
>>
>
> Patch below for comments. It passes xfsqa, but there's no userspace
> support for it yet. 2.6.26 is the likely target for this change.
>
2.6.26 merge window begins now. Has this been pushed yet? Is it in
linux-next tree ?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2008-04-17 20:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9a8748490803121513w285cd45rb6b26a3d842cac1b@mail.gmail.com>
[not found] ` <20080312221511.GC31632@fieldses.org>
[not found] ` <9a8748490803121516u36395872i70cc88b0439adc74@mail.gmail.com>
[not found] ` <18394.1501.991087.80264@notabene.brown>
[not found] ` <47DAEFD0.9020407@m2000.com>
[not found] ` <47E92F8E.7030504@m2000.com>
[not found] ` <20080325190943.GF2237@fieldses.org>
[not found] ` <32953.192.168.1.70.1206477121.squirrel@neil.brown.name>
[not found] ` <20080325212425.GA20257@josefsipek.net>
[not found] ` <34178.192.168.1.70.1206481102.squirrel@neil.brown.name>
2008-03-25 22:13 ` [opensuse] nfs_update_inode: inode X mode changed, Y to Z Josef 'Jeff' Sipek
2008-03-25 23:09 ` NeilBrown
2008-03-26 3:37 ` David Chinner
2008-03-26 5:02 ` David Chinner
2008-04-17 19:37 ` Adam Schrotenboer [this message]
[not found] <47C5EC81.6080004@m2000.com>
[not found] ` <47C71EC6.3050702@m2000.com>
[not found] ` <3AD71C5E-B45A-4BDB-8C94-73D62256BEBF@astro.wisc.edu>
2008-03-12 18:06 ` Adam Schrotenboer
[not found] <47CF0829.4020502@m2000.com>
[not found] ` <1204752463.5035.34.camel@heimdal.trondhjem.org>
[not found] ` <47CF157B.1010908@m2000.com>
[not found] ` <18383.24847.381754.517731@notabene.brown>
[not found] ` <47CF62C5.7000908@m2000.com>
[not found] ` <18384.50909.866848.966192@notabene.brown>
2008-03-07 5:55 ` Adam Schrotenboer
2008-03-12 17:55 ` Adam Schrotenboer
2008-03-12 18:08 ` Trond Myklebust
2008-03-12 18:16 ` Adam Schrotenboer
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=4807A6E8.6010102@m2000.com \
--to=adam@m2000.com \
--cc=bfields@fieldses.org \
--cc=dgc@sgi.com \
--cc=frevenu@m2000.com \
--cc=jdoan@m2000.com \
--cc=jeffpc@josefsipek.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tdaniel@m2000.com \
--cc=trond.myklebust@netapp.com \
--cc=xfs@oss.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 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).