All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: Something wrong with extent-based journal creation
Date: Wed, 17 Jun 2009 09:45:09 -0500	[thread overview]
Message-ID: <4A390175.9010003@redhat.com> (raw)
In-Reply-To: <20090617080432.GC13073@webber.adilger.int>

Andreas Dilger wrote:
> On Jun 16, 2009  17:38 -0500, Eric Sandeen wrote:
>> I've narrowed it down to the commit (961306d3) which creates the journal
>> with extent format; if that's commented out, it works fine.
> 
> Hmm, this seems like it might be a troublesome feature...  Are we sure
> that there is proper kernel/tool compatibility for an extent-mapped
> journal?  At least none of the Lustre code has any support for this,
> though they can handle the INCOMPAT_EXTENTS feature, and I don't think
> this was present in older kernels either.
> 
> I haven't looked at the code for this yet, so it may be that it will
> "just work", but if this is a new feature I would urge caution w.r.t.
> compatibility before this is merged upstream (in either e2fsprogs or
> the kernel).

It's already upstream.... :)

But I found the problem I was looking for, at least, see the [PATCH] in
reply to my original email.  (which is actually a pretty bad bug, likely
causing problems during e2fsck etc as well)

-Eric

  reply	other threads:[~2009-06-17 14:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 22:38 Something wrong with extent-based journal creation Eric Sandeen
2009-06-17  0:57 ` [PATCH] libext2fs: write only core inode in update_path() Eric Sandeen
2009-06-17 15:35   ` Theodore Tso
2009-06-17 15:50     ` Eric Sandeen
2009-06-17 22:50       ` Theodore Tso
2009-06-17 23:00         ` Eric Sandeen
2009-06-17  8:04 ` Something wrong with extent-based journal creation Andreas Dilger
2009-06-17 14:45   ` Eric Sandeen [this message]
2009-06-17 15:31   ` Theodore Tso

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=4A390175.9010003@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.