On Feb 22, 2013, Josef Bacik wrote:
> So I understand what you are getting at, but I think you are doing it wrong.
> If
> we're calling with CHUNK_ALLOC_FORCE, but somebody has already started to
> allocate with CHUNK_ALLOC_NO_FORCE, we'll reset the space_info->force_alloc to
> our original cal
On Feb 23, 2013, Alexandre Oliva wrote:
> On Feb 22, 2013, Josef Bacik wrote:
>> So I understand what you are getting at, but I think you are doing it wrong.
>> If
>> we're calling with CHUNK_ALLOC_FORCE, but somebody has already started to
>> allocate with CHUNK_ALLOC_NO_FORCE, we'll reset th
On Feb 21, 2013, Alexandre Oliva wrote:
> What I saw in that function also happens to explain why in some cases I
> see filesystems allocate a huge number of chunks that remain unused
> (leading to the scenario above, of not having more chunks to allocate).
> It happens for data and metadata, but
On Thu, Feb 21, 2013 at 06:15:49PM -0700, Alexandre Oliva wrote:
> On Feb 21, 2013, Alexandre Oliva wrote:
>
> > What I saw in that function also happens to explain why in some cases I
> > see filesystems allocate a huge number of chunks that remain unused
> > (leading to the scenario above, of n
