[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <loom.20140209T153529-464@post.gmane.org>
Date: Sun, 9 Feb 2014 14:39:42 +0000 (UTC)
From: Ian Nartowicz <claws@...towicz.co.uk>
To: linux-ext4@...r.kernel.org
Subject: Re: inline_data feature
Zheng Liu <gnehzuil.liu <at> gmail.com> writes:
>
> On Sat, Jan 25, 2014 at 10:29:09PM -0500, Theodore Ts'o wrote:
> > On Sat, Jan 25, 2014 at 08:22:56PM +0000, Ian Nartowicz wrote:
> > > Ian Nartowicz <claws <at> nartowicz.co.uk> writes:
> > >
> > > >
> > > > I have been trying to test the inline_data feature of EXT4.
> >
> > Could you try running e2fsck under valgrind? And could you also
> > confirm the git commit ID of the e2fsprogs pu branch that you used to
> > compile it?
> >
>
> Ian,
> Thanks for reporting the problem. That would be great if you can run
> e2fsck under valgrind as Ted suggested because it would help us to find
> the root cause.
>
> Further, Here is the latest patch set for making e2fsprogs support
> inline_data feature [1], which isn't applied into e2fsprogs/pu branch.
> This patch set is against e2fsprogs/next branch.
> Regards,
> - Zheng
> --
I was using the pu commit ID 11266daa7cc2af6601929f041684f1e2a2c4f773 from
October 14th. I'll try the latest patches against next. Are those patches
available as a tarball?
I ran valgrind and got a lot of output. Mostly uninitialised stuff, moves
and one or two others. Do you want that or just wait and see how the new
build goes?
--ian
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists