From: Arne Jansen <sensille@gmx.net>
To: Jerome M <jmwdev38@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Quota reached: can't delete
Date: Thu, 24 Jan 2013 16:14:23 +0100 [thread overview]
Message-ID: <51014FCF.7080202@gmx.net> (raw)
In-Reply-To: <CAEgy6-3jQ3nkFqY-eJj86vDSsfZQ2naiA-VoMw-U-TPaBd3Pew@mail.gmail.com>
On 24.01.2013 16:12, Jerome M wrote:
> Hi,
>
> With the current btrfs quota implementation, when you reach a
> subvolume quota limit, you can't delete anything without first
> removing the limit or enlarge it:
>
> rm: cannot remove `testfile.bin': Disk quota exceeded
>
>
> Is there any plan to change that?
Yes, there is. The problem is that even deletion needs space.
So we need to allow remove to go over quota. The current implementation
doesn't make this distinction.
-Arne
>
> Thanks,
> Jerome
> --
> 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:[~2013-01-24 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 15:12 Quota reached: can't delete Jerome M
2013-01-24 15:14 ` Arne Jansen [this message]
2014-08-07 22:04 ` MegaBrutal
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=51014FCF.7080202@gmx.net \
--to=sensille@gmx.net \
--cc=jmwdev38@gmail.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.