On 2016-05-18 07:24, Austin S. Hemmelgarn wrote:
On 2016-05-17 13:30, Josef Bacik wrote:
Our enospc flushing sucks. It is born from a time where we were early
enospc'ing constantly because multiple threads would race in for the same
reservation and randomly starve other ones out. So I came up
On Tue, May 17, 2016 at 01:30:55PM -0400, Josef Bacik wrote:
> V1->V2:
> -fixed a check in space_info_add_old_bytes where we didn't take into account
> bytes_may_used for the space used.
> -don't count ticket->bytes when checking overcommit.
I still see the warning in generic/333, same as with v1
On 2016-05-17 13:30, Josef Bacik wrote:
Our enospc flushing sucks. It is born from a time where we were early
enospc'ing constantly because multiple threads would race in for the same
reservation and randomly starve other ones out. So I came up with this solution
to block any other reservations
