From: Kevin Brandstatter <icarusthecow@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Removing file = quota exceded
Date: Tue, 24 Jun 2014 07:15:38 -0500 [thread overview]
Message-ID: <53A96BEA.40800@gmail.com> (raw)
In-Reply-To: <pan$ce26c$9607f21a$b0e5b759$ed8f68f3@cox.net>
I do recall that the issue was more specifically happening with larger
files.
In another scenario i had two files, one small or even empty, and one
large that filled the
subvolume quota. If i recall correctly, I was able to remove the smaller
file without exceeding
the quota limit, and then remove the larger file. However, removing the
larger file resulted
in the quota exceeded error. The behavior you describe with small files
makes this case make
more sense.
Likewise, I found that handling an unlink with a full subvolume qgruop
(EDQUOT) the same way as a full file system (ENOSPC) resolved the issue.
-Kevin
On 06/24/2014 12:31 AM, Duncan wrote:
> Duncan posted on Mon, 23 Jun 2014 01:53:45 +0000 as excerpted:
>
>> However, because btrfs stores very small files (generally something
>> under 16 MiB, the precise size depends on filesystem parameters)
>> entirely within metadata
> Hmm. Should be under 16 KiB I believe, not 16 MiB.
>
next prev parent reply other threads:[~2014-06-24 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 1:16 Removing file = quota exceded Kevin Brandstatter
2014-06-22 16:38 ` Josef Bacik
2014-06-22 17:56 ` Kevin Brandstatter
2014-06-23 1:53 ` Duncan
2014-06-23 23:36 ` [PATCH] handle start_unlink_transaction the same for an exceded quota , limit as an out of space error Kevin Brandstatter
2014-06-24 5:31 ` Removing file = quota exceded Duncan
2014-06-24 12:15 ` Kevin Brandstatter [this message]
2014-06-23 23:43 ` Kevin Brandstatter
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=53A96BEA.40800@gmail.com \
--to=icarusthecow@gmail.com \
--cc=1i5t5.duncan@cox.net \
--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).