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. > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
