From: Martin Mailand <martin@tuxadero.com>
To: Josef Bacik <josef@redhat.com>
Cc: Sage Weil <sage@newdream.net>,
ceph-devel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]()
Date: Fri, 16 Sep 2011 17:15:42 +0200 [thread overview]
Message-ID: <4E73681E.4030205@tuxadero.com> (raw)
In-Reply-To: <4E735F16.7000303@redhat.com>
Hi Josef,
the commit is not in there, but the code looks like your post.
if (--trans->use_count) {
trans->block_rsv = trans->orig_rsv;
return 0;
}
trans->block_rsv = NULL;
while (count < 4) {
unsigned long cur = trans->delayed_ref_updates;
trans->delayed_ref_updates = 0;
But on the other hand I am quite new to git, how could I get your latest
commit?
Best Regards,
Martin
Am 16.09.2011 16:37, schrieb Josef Bacik:
> On 09/16/2011 10:09 AM, Martin Mailand wrote:
>> Hi Josef,
>> after a quick test it seems that I do not hit this Warning any longer.
>> But I got a new one.
>>
>
> Hmm looks like that may not be my newest stuff, is commit
>
> 57f499e1bb76ba3ebeb09cd12e9dac84baa5812b
>
> in there? Specifically look at __btrfs_end_transaction in transaction.c
> and see if the line
>
> trans->block_rsv = NULL;
>
> is before the first while() loop. 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
next prev parent reply other threads:[~2011-09-16 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 21:47 WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() Martin Mailand
2011-09-13 1:02 ` Liu Bo
2011-09-15 18:44 ` Sage Weil
2011-09-15 19:50 ` Josef Bacik
2011-09-15 20:12 ` David Sterba
2011-09-15 20:29 ` Sage Weil
2011-09-16 14:09 ` Martin Mailand
2011-09-16 14:37 ` Josef Bacik
2011-09-16 15:15 ` Martin Mailand [this message]
2011-09-15 19:55 ` David Sterba
2011-09-16 16:25 ` Jim Schutt
2011-09-19 11:06 ` David Sterba
2011-09-19 15:49 ` 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=4E73681E.4030205@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.net \
/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