On 06/22/2014 11:38 AM, Josef Bacik wrote:
On 06/21/2014 06:16 PM, Kevin Brandstatter wrote:
so ive come accross the issue of being unable to remove a file when a
subvolume quota is reached. This can be resolved by truncating the file
first, or removing the quota temporarily.
However, it
Duncan posted on Mon, 23 Jun 2014 01:53:45 + 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.
--
Duncan - List
On 06/21/2014 06:16 PM, Kevin Brandstatter wrote:
so ive come accross the issue of being unable to remove a file when a
subvolume quota is reached. This can be resolved by truncating the file
first, or removing the quota temporarily.
However, it should be reasonable that you should alwasy be
One thing i note is that I can unlink from a full filesystem.
I tested it by writing a file until the device ran out of space, and
then rm it,
the same method that i used to cause the disk quota error, and it was
able to remove without
issue.
-Kevin
On 06/22/2014 11:38 AM, Josef Bacik wrote:
On
Kevin Brandstatter posted on Sun, 22 Jun 2014 12:56:30 -0500 as excerpted:
One thing i note is that I can unlink from a full filesystem.
I tested it by writing a file until the device ran out of space, and
then rm it, the same method that i used to cause the disk quota error,
and it was able
so ive come accross the issue of being unable to remove a file when a
subvolume quota is reached. This can be resolved by truncating the file
first, or removing the quota temporarily.
However, it should be reasonable that you should alwasy be able to
remove a file, regardless of quota limitations
