From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Dan Arena <ddan39@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Why is 64bit option always on by default now?
Date: Wed, 4 Jan 2017 17:18:39 +0100 [thread overview]
Message-ID: <20170104161839.GB3607@quack2.suse.cz> (raw)
In-Reply-To: <20161223024537.4sg2ck2bmkgsn2ry@thunk.org>
On Thu 22-12-16 21:45:37, Ted Tso wrote:
> 64-bit support has been around for 7 years (since e2fsprogs 1.41).
> And yes, e2fsprogs 1.43 now has the ability to convert a file system
> from 32-bit to 64-bit, but this is an inherently dangerous thing to
> do, since it requires rewriting the inode table. If you ever crash or
> power fail during the conversion, *boom*, you can lose all or most of
> your data. So the conversion can be used as a short cut where you
> back up the whole file system, and then try to convert to 64-bit, and
> if it succeeds, then you don't have to do the restore step. If it
> crashes and you lose everything, then you can reformat the file system
> and restore from backups. :-)
>
> In general, I assume that embedded developers are more sophisticated
> than users (who will use the mke2fs in the installer to install thier
> root file system, which will be a matched set with the bootloader). I
> also can't be responsible for crappy, obsolete bootloader on embedded
> devices, some of which have device drivers only available in ancient
> BSP kernels using 3.10, etc.
Just to add some more data, we have actually got similar reports few months
ago for openSUSE once we shipped updated e2fsprogs. And the bootloader they
used (u-boot) does not support 64-bit feature at all. My answer has been
similar to yours - either update the bootloader or change mke2fs.conf in
your setup. There's one guy working on implementing 64-bit support in
u-boot BTW.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-01-04 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 18:59 Why is 64bit option always on by default now? Dan Arena
2016-12-23 2:45 ` Theodore Ts'o
2017-01-04 16:18 ` Jan Kara [this message]
[not found] ` <CAKnMEmGecqczn0ORNEpT=TYc5QXMu+t9-5LFnZNngg+gbZx4Zw@mail.gmail.com>
2017-01-05 7:13 ` Jan Kara
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=20170104161839.GB3607@quack2.suse.cz \
--to=jack@suse.cz \
--cc=ddan39@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).