On Mon, 2007-05-07 at 17:15 -0700, Andrew Morton wrote:

quoted text
> On Mon, 07 May 2007 17:00:24 -0700

> Mingming Cao  wrote:

>

> > > +       while (ret >= 0 && ret < max_blocks) {

> > > +               block = block + ret;

> > > +               max_blocks = max_blocks - ret;

> > > +               ret = ext4_ext_get_blocks(handle, inode, block,

> > > +                                         max_blocks, &map_bh,

> > > +                                         EXT4_CREATE_UNINITIALIZED_EXT, 0);

> > > +               BUG_ON(!ret);

> > > +               if (ret > 0 && test_bit(BH_New, &map_bh.b_state)

> > > +                       && ((block + ret) > (i_size_read(inode) << blkbits)))

> > > +                       nblocks = nblocks + ret;

> > > +       }

> > > +

> > > +       if (ret == -ENOSPC && ext4_should_retry_alloc(inode->i_sb, &retries))

> > > +               goto retry;

> > > +

> > > Now the interesting question is: what do we do if we get halfway through

> > > this loop and then run out of space?  We could leave the disk all filled up

> > > and then return failure to the caller, but that's pretty poor behaviour,

> > > IMO.

> > >

> > The current code handles earlier ENOSPC by three times retries. After

> > that if we still run out of space, then it's propably right to notify

> > the caller there isn't much space left.

> >

> > We could extend the block reservation window size before the while loop

> > so we could get a lower chance to get more fragmented.

>

> yes, but my point is that the proposed behaviour is really quite bad.

>

I agree your point, that's why I mention it only helped the

fragmentation issue but not the ENOSPC case.

> We will attempt to allocate the disk space and then we will return failure,

quoted text
> having consumed all the disk space and having partially and uselessly

> populated an unknown amount of the file.

> 

Not totally useless I think. If only half of the space is preallocated

because run out of space, the application can decide whether it's good

enough to start to use this preallocated space or wait for the fs to

have more free space.
> Userspace could presumably repair the mess in most situations by truncating

quoted text
> the file back again.  The kernel cannot do that because there might be live

> data in amongst there.

>

> So we'd need to either keep track of which blocks were newly-allocated and

> then free them all again on the error path (doesn't work right across

> commit+crash+recovery) or we could later use the space-reservation scheme which

> delayed allocation will need to introduce.

>

> Or we could decide to live with the above IMO-crappy behaviour.

In fact Amit and I had raised this issue before, whether it's okay to do

allow partial preallocation. At that moment the feedback is it's no much

different than the current zero-out-preallocation behavior: people might

preallocating half-way then later deal with ENOSPC.
We could check the total number of fs free blocks account before

preallocation happens, if there isn't enough space left, there is no

need to bother preallocating.
If there is enough free space, we could make a reservation window that

have at least N free blocks and mark it not stealable by other files. So

later we will not run into the ENOSPC error.
The fs free blocks account is just a estimate though.
Mingming
-

unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html

Please read the FAQ at  http://www.tux.org/lkml/