linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Raymond Jennings <shentino@gmail.com>, Albino B Neto <bino@riseup.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] Ext3 removal, quota & udf fixes
Date: Wed, 2 Sep 2015 09:28:37 -0400	[thread overview]
Message-ID: <55E6F985.3080105@gmail.com> (raw)
In-Reply-To: <55E68D49.5000404@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]

On 2015-09-02 01:46, Raymond Jennings wrote:
> On 09/01/15 20:30, Albino B Neto wrote:
>> 2015-08-31 23:53 GMT-03:00 Theodore Ts'o <tytso@mit.edu>:
>>> Yes, you can go back to ext3-only.  In fact, we do *not* automatically
>>> upgrade the file system to use ext4-specific features.
>>>> So it's not just a "you can use ext4 instead" issue. Can you do that
>>>> *without* then forcing an upgrade forever on that partition? I'm not
>>>> sure the ext4 people are really even willing to guarantee that kind of
>>>> backwards compatibility.
>>> Actually, we do guarantee this.  It's considered poor form to
>>> automatically change the superblock to add new file system features in
>>> a way that would break the ability for the user to roll back to an
>>> older kernel.  This isn't just for ext3->ext4, but for new ext4
>>> features such as metadata checksumming.  The user has to explicitly
>>> enable the feature using "tune2fs -O new_feature /dev/sdXX".
>> Yeah!
>>
>> 2015-09-01 16:39 GMT-03:00 Austin S Hemmelgarn <ahferroin7@gmail.com>:
>>> NO, it is not logical.  A vast majority of Android smartphones in the
>>> wild
>>> use ext2, as do a very significant portion of embedded systems that
>>> don't
>>> have room for the few hundred kilobytes of extra code that the ext4
>>> driver
>>> has in comparison to ext2.
>> Ext2 portion embedded and Ext3 many machines.
>
> So basically the game plan is gutting ext3 because code-dupe with ext4,
> but keep ext2 because ext4 is too big for embedded to outright replace
> ext2?
>
> Hmm...are there any embedded systems out there that use ext3 and can fit
> its code ext3 but not ext4?
Probably, but I don't know of any myself.  TBH, the systems that use 
ext2 because of space savings are usually ones with less than 64M of 
RAM, which is becoming a smaller and smaller market share.



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-09-02 13:28 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  6:19 [GIT PULL] Ext3 removal, quota & udf fixes Jan Kara
2015-08-31 21:37 ` Linus Torvalds
2015-08-31 22:31   ` Raymond Jennings
2015-08-31 22:39     ` Linus Torvalds
2015-08-31 23:03       ` Raymond Jennings
2015-09-01  2:53       ` Theodore Ts'o
2015-09-01 12:52       ` Eric Sandeen
2015-09-01 15:17         ` Jeff Mahoney
2015-09-01  0:24     ` Raymond Jennings
2015-09-01  6:44     ` Christoph Hellwig
2015-09-01 10:29     ` Albino B Neto
2015-09-01 19:39       ` Austin S Hemmelgarn
2015-09-01 23:58         ` Theodore Ts'o
2015-09-02 16:58           ` Austin S Hemmelgarn
2015-09-02  3:30         ` Albino B Neto
2015-09-02  5:46           ` Raymond Jennings
2015-09-02 13:28             ` Austin S Hemmelgarn [this message]
2015-09-02 11:58         ` Chuck Ebbert
2015-09-02 13:33           ` Austin S Hemmelgarn
2015-09-01  0:23   ` Andreas Dilger
2015-09-02 16:52   ` Mel Gorman
2015-09-02 18:45     ` Darrick J. Wong
2015-09-02 23:47       ` Linus Torvalds
2015-09-03 11:28         ` Albino B Neto
2015-09-03 21:49           ` Darrick J. Wong
2015-09-15  5:31         ` Jan Kara
2015-09-03 18:22 ` Richard Yao
2015-09-03 18:36   ` Eric Sandeen
2015-09-03 19:13     ` Richard Yao
2015-09-03 18:36   ` Darrick J. Wong
2015-09-03 19:16     ` Richard Yao
2015-09-03 19:36       ` Darrick J. Wong
2015-09-03 22:26         ` Richard Yao

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=55E6F985.3080105@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=bino@riseup.net \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shentino@gmail.com \
    --cc=torvalds@linux-foundation.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).