From: Josef Bacik <jbacik@fb.com>
To: Mark Fasheh <mfasheh@suse.de>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
<linux-btrfs@vger.kernel.org>, <fdmanana@suse.com>
Subject: Re: [PATCH v4] btrfs: qgroup: Fix qgroup accounting when creating snapshot
Date: Fri, 22 Apr 2016 14:23:59 -0400 [thread overview]
Message-ID: <571A6C3F.1010704@fb.com> (raw)
In-Reply-To: <20160422182148.GZ2187@wotan.suse.de>
On 04/22/2016 02:21 PM, Mark Fasheh wrote:
> On Fri, Apr 22, 2016 at 02:12:11PM -0400, Josef Bacik wrote:
>> On 04/15/2016 05:08 AM, Qu Wenruo wrote:
>>> + /*
>>> + * Force parent root to be updated, as we recorded it before so its
>>> + * last_trans == cur_transid.
>>> + * Or it won't be committed again onto disk after later
>>> + * insert_dir_item()
>>> + */
>>> + if (!ret)
>>> + record_root_in_trans(trans, parent, 1);
>>> + return ret;
>>> +}
>>
>> NACK, holy shit we aren't adding a special transaction commit only
>> for qgroup snapshots. Figure out a different way. Thanks,
>
> Yeah I saw that. To be fair, we run a whole lot of the transaction stuff
> multiple times (at least from my reading) so I'm really unclear on what the
> performance impact is.
>
> Do you have any suggestion though? We've been banging our heads against this
> for a while now and as slow as this patch might be, it actually works where
> nothing else has so far.
I'm less concerned about committing another transaction and more
concerned about the fact that it is an special variant of the
transaction commit. If this goes wrong, or at some point in the future
we fail to update it along with btrfs_transaction_commit we suddenly are
corrupting metadata. If we have to commit a transaction then call
btrfs_commit_transaction(), don't open code a stripped down version,
here be dragons. Thanks,
Josef
next prev parent reply other threads:[~2016-04-22 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 9:08 [PATCH v4] btrfs: qgroup: Fix qgroup accounting when creating snapshot Qu Wenruo
2016-04-19 22:19 ` Mark Fasheh
2016-04-20 14:25 ` Holger Hoffstätte
2016-04-22 18:12 ` Josef Bacik
2016-04-22 18:21 ` Mark Fasheh
2016-04-22 18:23 ` Josef Bacik [this message]
2016-04-22 18:29 ` Mark Fasheh
2016-04-25 0:56 ` Qu Wenruo
2016-04-25 14:24 ` Josef Bacik
2016-04-26 0:35 ` Qu Wenruo
2016-04-26 14:26 ` Josef Bacik
2016-04-27 1:12 ` Qu Wenruo
2016-05-11 16:57 ` Mark Fasheh
2016-05-11 16:59 ` Josef Bacik
2016-05-11 19:53 ` Mark Fasheh
2016-05-11 20:30 ` Josef Bacik
2016-05-11 23:33 ` Qu Wenruo
2016-05-12 9:10 ` David Sterba
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=571A6C3F.1010704@fb.com \
--to=jbacik@fb.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mfasheh@suse.de \
--cc=quwenruo@cn.fujitsu.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).