linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Ian Nartowicz <claws@nartowicz.co.uk>
Cc: linux-ext4@vger.kernel.org
Subject: Re: inline_data feature
Date: Sat, 25 Jan 2014 22:29:09 -0500	[thread overview]
Message-ID: <20140126032909.GA24834@thunk.org> (raw)
In-Reply-To: <loom.20140125T212226-499@post.gmane.org>

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.  I am using
> > kernel 3.9.5 and have compiled e2fsprogs from the pu branch.  I am able to
> > set the feature and apparently to use the filesystem, but I get a lot of
> > warnings from the kernel and fsck reports several errors and then crashes.
> > 
> I wonder if I might have compiled against the wrong (clib?) headers?  Are
> you aware of any version dependencies in the pu branch tools?

I doubt it; this looks like a straightforward memory bug of some kind
(i.e., use after free, etc.)

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?

A compressed raw e2image file would be useful as well, but one problem
with inline data is that a raw e2image file will have some amount of
file data (for the small files that are using inline data) in the
e2image file.  We should probably look at teaching e2image to can zero
out the contents of inline data files....

Many thanks,

					- Ted

  reply	other threads:[~2014-01-26  3:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 16:17 inline_data feature Ian Nartowicz
2014-01-24 16:05 ` Ian Nartowicz
2014-01-24 16:21   ` Theodore Ts'o
2014-01-24 18:44     ` Ian Nartowicz
2014-01-25 20:22 ` Ian Nartowicz
2014-01-26  3:29   ` Theodore Ts'o [this message]
2014-01-28 12:20     ` Zheng Liu
2014-02-09 14:39       ` Ian Nartowicz
2014-02-09 15:45 ` Ian Nartowicz
2014-02-10  3:47   ` Zheng Liu
2014-02-10 12:06     ` Ian Nartowicz
2014-02-13 12:11       ` Zheng Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140126032909.GA24834@thunk.org \
    --to=tytso@mit.edu \
    --cc=claws@nartowicz.co.uk \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).