linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josef Bacik <jbacik@fusionio.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: drop dir i_size when adding new names on replay
Date: Wed, 11 Sep 2013 14:56:36 -0400	[thread overview]
Message-ID: <20130911185636.GE2446@localhost.localdomain> (raw)
In-Reply-To: <1378923537-14722-1-git-send-email-jbacik@fusionio.com>

On Wed, Sep 11, 2013 at 02:18:57PM -0400, Josef Bacik wrote:
> So if we have dir_index items in the log that means we also have the inode item
> as well, which means that the inode's i_size is correct.  However when we
> process dir_index'es we call btrfs_add_link() which will increase the
> directory's i_size for the new entry.  So to fix this just drop the name len
> size before we call btrfs_add_link() so the i_size ends out properly.  Thanks,
> 

Ignore this, it isn't quite right.  Thanks,

Josef

      reply	other threads:[~2013-09-11 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 18:18 [PATCH] Btrfs: drop dir i_size when adding new names on replay Josef Bacik
2013-09-11 18:56 ` Josef Bacik [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=20130911185636.GE2446@localhost.localdomain \
    --to=jbacik@fusionio.com \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).