linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>
Cc: dave@jikos.cz, "J. Bruce Fields" <bfields@fieldses.org>,
	Josef Bacik <josef@redhat.com>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
	linux-btrfs@vger.kernel.org, hch@infradead.org
Subject: Re: [RFC] [PATCH 2/2] Btrfs: move over to use ->update_time
Date: Fri, 11 May 2012 14:34:17 -0400	[thread overview]
Message-ID: <20120511183417.GA3503@localhost.localdomain> (raw)
In-Reply-To: <CALLzPKYBvUmCJp3WokkZjfryMfovsYVhrfggHfCmJ+3kb5pyQA@mail.gmail.com>

On Fri, May 11, 2012 at 09:06:31AM +0300, Kasatkin, Dmitry wrote:
> On Thu, Apr 12, 2012 at 2:32 PM, David Sterba <dave@jikos.cz> wrote:
> > On Thu, Apr 12, 2012 at 02:09:08PM +0300, Kasatkin, Dmitry wrote:
> >> Where is it? Can you please point out?
> >
> > http://permalink.gmane.org/gmane.comp.file-systems.btrfs/16662
> >
> > the relevant part:
> >
> > -- a/fs/btrfs/super.c
> > +++ b/fs/btrfs/super.c
> > @@ -770,7 +770,7 @@ static int btrfs_fill_super(struct super_block =
*sb,
> > =A0#ifdef CONFIG_BTRFS_FS_POSIX_ACL
> > =A0 =A0 =A0 =A0sb->s_flags |=3D MS_POSIXACL;
> > =A0#endif
> > -
> > + =A0 =A0 =A0 sb->s_flags |=3D MS_I_VERSION;
> > =A0 =A0 =A0 =A0err =3D open_ctree(sb, fs_devices, (char *)data);
> > =A0 =A0 =A0 =A0if (err) {
> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0printk("btrfs: open_ctree failed\n")=
;
>=20
> Hello,
>=20
> FYI:
>=20
> In fact just tried yesterday to use mount option "iversion" on 3.4-rc=
5
> and it seems to work without
>  + =A0 =A0 =A0 sb->s_flags |=3D MS_I_VERSION;

This hasn't gone in yet, it won't go in until 3.5.  Thanks,

Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-05-11 18:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 14:10 [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time Josef Bacik
2012-03-26 14:10 ` [RFC] [PATCH 2/2] Btrfs: move over to use ->update_time Josef Bacik
2012-04-04 17:24   ` Kasatkin, Dmitry
2012-04-04 17:43     ` Josef Bacik
2012-04-04 17:47       ` Mimi Zohar
2012-04-04 18:12         ` Kasatkin, Dmitry
2012-04-04 18:16           ` Josef Bacik
2012-04-04 18:21             ` Kasatkin, Dmitry
2012-04-09 15:16             ` J. Bruce Fields
2012-04-10  7:48               ` David Sterba
2012-04-12 11:09                 ` Kasatkin, Dmitry
2012-04-12 11:32                   ` David Sterba
2012-04-12 11:43                     ` Kasatkin, Dmitry
2012-05-11  6:06                     ` Kasatkin, Dmitry
2012-05-11 18:34                       ` Josef Bacik [this message]
2012-04-30 15:21 ` [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time Christoph Hellwig
2012-04-30 17:12   ` Josef Bacik

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=20120511183417.GA3503@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=dave@jikos.cz \
    --cc=dmitry.kasatkin@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zohar@linux.vnet.ibm.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).