From: Josef Bacik <josef@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: don't use delalloc block rsv for free space inodes
Date: Mon, 29 Aug 2011 12:17:10 -0400 [thread overview]
Message-ID: <4E5BBB86.7050501@redhat.com> (raw)
In-Reply-To: <1314631147-13434-1-git-send-email-josef@redhat.com>
On 08/29/2011 11:19 AM, Josef Bacik wrote:
> In tracking down this "not enough space" warning with checksums, it seems that
> we were running out of space partly because we do not reserve space for our free
> space inodes. Since this is technically metadata anyway go ahead and use the
> global_block_rsv for our free space inodes. We shouldn't be modifying too much
> other metadata since this will be a preallocated extent and that was already
> accounted for earlier. Thanks,
>
Ignore these, they cause other problems, I'll fix it a different way.
Thanks,
Josef
prev parent reply other threads:[~2011-08-29 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 15:19 [PATCH] Btrfs: don't use delalloc block rsv for free space inodes Josef Bacik
2011-08-29 15:37 ` [PATCH] Btrfs: don't use delalloc block rsv for free space inodes V2 Josef Bacik
2011-08-29 16:17 ` Josef Bacik [this message]
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=4E5BBB86.7050501@redhat.com \
--to=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 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).