On Tue 20-10-09 18:01:31, Aneesh Kumar K.V wrote:
> On Tue, Oct 20, 2009 at 09:24:38AM +0200, Jan Kara wrote:
> > We cannot rely on buffer dirty bits during fsync because pdflush can come
> > before fsync is called and clear dirty bits without forcing a transaction
> > commit. What we do is that we track which transaction has last changed
> > the inode and which transaction last changed allocation and force it to
> > disk on fsync.
<snip>
> > diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> > index 10539e3..3e167f6 100644
> > --- a/fs/ext4/extents.c
> > +++ b/fs/ext4/extents.c
> > @@ -3315,6 +3315,11 @@ int ext4_ext_get_blocks(handle_t *handle, struct inode *inode,
> > newblock = ext_pblock(&newex);
> > allocated = ext4_ext_get_actual_len(&newex);
> > set_buffer_new(bh_result);
> > +
> > + atomic_set(&EXT4_I(inode)->i_sync_tid, handle->h_transaction->t_tid);
> > + atomic_set(&EXT4_I(inode)->i_datasync_tid,
> > + handle->h_transaction->t_tid);
> > + printk("Datasync tid %u\n", handle->h_transaction->t_tid);
>
> The printk need to be removed ?
Ah, missed that debugging aid. Will fix.
> Also i am wondering wether we need to update i_datasync_tid only if we
> allocate new blocks ? How about writing to an fallocate area. I guess
Yes, we need to update it only if we allocate new blocks but that should
be what I've done (but maybe I screwed up...).
> we need to track the transaction in which we are marking an extent
> initialized.
You are right that i_datasync_tid needs to be updated also when we
convert uninitialized extents to initialized ones. I'll fix this case.
Thanks for review.
Honza
--
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
