From: "Jim Schutt" <jaschut@sandia.gov>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: btrfs warnings from 2.6.39-rc5
Date: Mon, 16 May 2011 08:28:57 -0600 [thread overview]
Message-ID: <4DD134A9.8010008@sandia.gov> (raw)
In-Reply-To: <4DC016C1.2070505@redhat.com>
Josef Bacik wrote:
> On 04/27/2011 02:43 PM, Jim Schutt wrote:
>> Hi,
>>
>> I'm not sure if they matter, but I got these warnings on
>> one of the machines I'm using as a Ceph OSD server:
>>
>> [ 1806.549469] ------------[ cut here ]------------
>> [ 1806.554593] WARNING: at fs/btrfs/extent-tree.c:5790
>> use_block_rsv+0xa7/0x101 [btrfs]()
>> Please let me know if I can do anything to help sort these out.
>>
>
> I just posted a patch for this problem, it's titled
>
> Btrfs: fix how we do space reservation for truncate
>
> Please apply it and test it and see if it makes this problem go away.
This patch has been working very well for me, thanks.
I've had no sign of truncate trouble since I started using it.
-- Jim
> Thanks,
>
> Josef
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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-05-16 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 18:43 btrfs warnings from 2.6.39-rc5 Jim Schutt
2011-05-03 14:52 ` Josef Bacik
2011-05-04 16:37 ` Jim Schutt
2011-05-16 14:28 ` Jim Schutt [this message]
2011-05-16 14:56 ` 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=4DD134A9.8010008@sandia.gov \
--to=jaschut@sandia.gov \
--cc=ceph-devel@vger.kernel.org \
--cc=josef@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.