From: Josef Bacik <jbacik@fusionio.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
Josef Bacik <JBacik@fusionio.com>
Subject: Re: use_block_rsv problems with 3.6.1
Date: Thu, 11 Oct 2012 14:51:54 -0400 [thread overview]
Message-ID: <20121011185154.GA5755@localhost.localdomain> (raw)
In-Reply-To: <50771184.2060807@profihost.ag>
On Thu, Oct 11, 2012 at 12:35:48PM -0600, Stefan Priebe wrote:
> Hello,
>
> on i've seen the following backtrace a lot on 3.6.1:
> [ 2231.644332] use_block_rsv: 1451 callbacks suppressed
> [ 2231.645249] btrfs: block rsv returned -28
Yeah this is the last deep dark corner of ENOSPC, we don't quite hold enough
reserved to handle deleting lots of csums. Technically this is supposed to be
taken care of by ye olde global block rsv, but in some cases it's not enough.
On the bright side if you are just seeing the warnings then we're able to find
space somewhere and you are a-ok, but it is kind of annoying. Once I finish my
fsync stuff I'll go back to this problem and try and figure out a real solution.
Thanks,
Josef
next prev parent reply other threads:[~2012-10-11 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 18:35 use_block_rsv problems with 3.6.1 Stefan Priebe
2012-10-11 18:51 ` Josef Bacik [this message]
2012-10-11 18:56 ` Stefan Priebe
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=20121011185154.GA5755@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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).