From: Josef Bacik <jbacik@fusionio.com>
To: Aastha Mehta <aasthakm@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Questions regarding logging upon fsync in btrfs
Date: Sat, 28 Sep 2013 20:42:52 -0400 [thread overview]
Message-ID: <20130929004252.GL18681@localhost.localdomain> (raw)
In-Reply-To: <CAEx9m45FDjNCBLEYM0x7fY36R7QJesS0F-fzWzNi=d_cBSOjOQ@mail.gmail.com>
On Sun, Sep 29, 2013 at 01:35:15AM +0200, Aastha Mehta wrote:
> Hi,
>
> I have few questions regarding logging triggered by calling fsync in BTRFS:
>
> 1. If I understand correctly, fsync will call to log entire inode in
> the log tree. Does this mean that the data extents are also logged
> into the log tree? Are they copied into the log tree, or just
> referenced? Are they copied into the subvolume's extent tree again
> upon replay?
>
The data extents are copied as well, as in the metadata that points to the data,
not the actual data itself. For 3.1 it's all of the extents in the inode, in
3.8 on it's only the extents that have changed this transaction.
> 2. During replay, when the extents are added into the extent
> allocation tree, do they acquire the physical extent number during
> replay? Does they physical extent allocated to the data in the log
> tree differ from that in the subvolume?
>
No the physical location was picked when we wrote the data out during fsync. If
we crash and re-mount the replay will just insert the ref into the extent tree
for the disk offset as it replays the extents.
> 3. I see there is a mount option of notreelog available. After
> disabling tree logging, does fsync still lead to flushing of buffers
> to the disk directly?
>
notreelog just means that we write the data and wait on the ordered data extents
and then commit the transaction. So you get the data for the inode you are
fsycning and all of the metadata for the entire file system that has changed in
that transaction.
> 4. Is it possible to selectively identify certain files in the log
> tree and flush them to disk directly, without waiting for the replay
> to do it?
>
I don't understand this question, replay only happens on mount after a
crash/power loss, and everything is replayed that is in the log, there is no way
to select which inode is replayed. Thanks,
Josef
next prev parent reply other threads:[~2013-09-29 0:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-28 23:35 Questions regarding logging upon fsync in btrfs Aastha Mehta
2013-09-28 23:46 ` Aastha Mehta
2013-09-29 0:21 ` Hugo Mills
2013-09-29 0:42 ` Josef Bacik [this message]
2013-09-29 9:22 ` Aastha Mehta
2013-09-29 13:12 ` Josef Bacik
2013-09-30 19:32 ` Aastha Mehta
2013-09-30 20:11 ` Josef Bacik
2013-09-30 20:30 ` Aastha Mehta
2013-09-30 20:47 ` Josef Bacik
2013-09-30 21:07 ` Aastha Mehta
2013-09-30 21:17 ` Josef Bacik
2013-10-01 17:34 ` Josef Bacik
2013-10-01 19:40 ` Aastha Mehta
2013-10-01 19:42 ` Aastha Mehta
2013-10-01 20:13 ` Aastha Mehta
2013-10-02 11:52 ` Josef Bacik
2013-10-02 20:12 ` Aastha Mehta
2013-10-02 23:28 ` 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=20130929004252.GL18681@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=aasthakm@gmail.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).