public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Making it easier for end users to use ext4
Date: Mon, 14 Jul 2008 15:55:26 -0400	[thread overview]
Message-ID: <20080714195526.GA3382@mit.edu> (raw)
In-Reply-To: <487BAA6B.7030001@redhat.com>

On Mon, Jul 14, 2008 at 02:35:07PM -0500, Eric Sandeen wrote:
> > Eric, when you have a chance, could you take a quick peek at the Fedora
> > Core section of that page and update it appropriately.  
> 
> Sure, first I'll remove "core" since that terminology doesn't exist
> anymore ;)

Is "FC" acronym as in "FC9" going away as well?  :-)

> I think very soon just saying "run the latest kernel + e2fsprogs from F9
> updates-testing" will be a good start.  It won't have delalloc yet,
> though.  Do we want to try to make that more widely available to people
> who can't/don't build their own kernels?  I'm slightly hesitant I guess
> both for the extra work of maintaining the repo & complete kernel
> builds, as well as providing too much rope to people who may not know
> just how much rope they've got ...

Well, there are two reasons why I was thinking it might be nice to
synch up the ext4 code base.  One was the "more testers good"
argument.  The other was is that while *most* of the various races and
bug fixes that have gone in since 2.6.26 were delalloc related, some
are real bugs that might bite 2.6.25 users if they start using the
ext4 code in a more demanding workload.  That would result in perhaps
preventable data loss, plus which we could end up spending time
debugging a problem which had already been solved.

If Fedora is going to be putting out another test kernel shortly, any
chance we can get the 2.6.26-ext4-1 or 2.6.26-ext4-2 (with mingming's
latest patch, to be released shortly) included in that test kernel?
Again, the goal is to make it as easy as possible for people to test
the latest version of ext4, so we can get those bugs fixed.

Regards,

						- Ted

  reply	other threads:[~2008-07-14 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 19:24 Making it easier for end users to use ext4 Theodore Ts'o
2008-07-14 19:35 ` Eric Sandeen
2008-07-14 19:55   ` Theodore Tso [this message]
2008-07-14 21:27     ` Eric Sandeen
     [not found]     ` <1216172323.8292.23.camel@mingming-laptop>
     [not found]       ` <20080716023532.GO8185@mit.edu>
     [not found]         ` <1216227720.6424.7.camel@mingming-laptop>
2008-07-16 17:52           ` [PATCH, RFC] Add more intelligent handling of the mke2fs.conf installation process Theodore Tso
2008-07-16 18:24             ` Mingming Cao
2008-07-16 21:29             ` Andreas Dilger
2008-07-16 23:08               ` Theodore Tso
2008-07-15  5:22 ` Making it easier for end users to use ext4 Goswin von Brederlow

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=20080714195526.GA3382@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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