Hello,
I need to switch to a newer kernel than 3.16.0-4.
But since the new ext4 is not finished yet, I'm concerned
about the safety of the data on my ext4-hd.
I don't know how the ext4-inclusion-policy-into-the-kernel is,
maybe one of you can enlighten me. I mean, the old (ie. the current)
ext4 seems to be ok, and I would not want to risk the data to a new,
but unfinished, ext4-module in a newer kernel.
Is there maybe a kernel-switch to use the old ext4 module?
Can I safely install the "stable 4.0.4" kernel from http://www.kernel.org?
--
Thx
Uenal
On Wed, Jun 03, 2015 at 09:50:39PM +0200, U.Mutlu wrote:
> I need to switch to a newer kernel than 3.16.0-4.
> But since the new ext4 is not finished yet, I'm concerned
> about the safety of the data on my ext4-hd.
> I don't know how the ext4-inclusion-policy-into-the-kernel is,
> maybe one of you can enlighten me. I mean, the old (ie. the current)
> ext4 seems to be ok, and I would not want to risk the data to a new,
> but unfinished, ext4-module in a newer kernel.
> Is there maybe a kernel-switch to use the old ext4 module?
There really is no such thing as "the new ext4", and talking about
ext4 "is not finished yet" also makes no sense. We add new features
to ext4 on a rolling basis, just as Linus is adding new features to
Linux, the gcc developers are adding new features to gcc, the emacs
developers are adding new features to emacs, etc., etc. Just as it
doesn't make sense to talk about "the new gcc is not finished yet", it
doesn't make sense to talk about "the new ext4 is not finished yet".
Various ext4 features are enabled using feature flags when you create
the file system using mke2fs, and some/most features can be
manipulated using the tune2fs command. Very often features can only
be used when you have upgraded a newer version of e2fsprogs. So for
example, the metadata checksum feature and the encryption feature
can't be used unless you fetch the development branch of e2fsprogs and
build it yourself. (Well, there is e2fsprogs 1.43~WIP-2015-05-18-1 as
a Debian experimental package, but you use that at your own risk.)
If you restrict yourself to the file system features in the e2fsprogs
1.42.x branch, you should be fine.
> Can I safely install the "stable 4.0.4" kernel from http://www.kernel.org?
You can, but the 4.0 kernel is kernel version that is going to be
getting long-term backports of bug fixes, security fixes, etc. Some
people will regularly track the new kernels, and but if you're someone
who doesn't understand the details of manging kernel upgrades (and
with all due respect, someone who thinks that it's possible to protect
users from root is probably someone who doesn't have the knowledge,
skills, and experience to maintain their own kernel), it might be
better to stick with a distribution supported and maintained kernel.
If you are more adventurous, you could try using one of the long-term
supported kernel (i.e., such as 3.18). See:
https://www.kernel.org/category/releases.html
But remember, now you have to properly configure the kernel, and you
are responsible for checking for new releases of the a long-term
supported kernel. If you stick with a specific kernel version and
don't upgrade it, then you might be prone to security bugs that would
have been fixed by a newer kernel.
Regards,
- Ted
Theodore Ts'o wrote on 06/04/2015 04:08 AM:
> If you are more adventurous, you could try using one of the long-term
> supported kernel (i.e., such as 3.18). See:
>
> https://www.kernel.org/category/releases.html
>
> But remember, now you have to properly configure the kernel, and you
> are responsible for checking for new releases of the a long-term
> supported kernel. If you stick with a specific kernel version and
> don't upgrade it, then you might be prone to security bugs that would
> have been fixed by a newer kernel.
Thanks for the info,
I have many times compiled a kernel and used it successfully,
but when I dist-upgraded from Debian 7 to Debian 8 it installed
it's own stock kernel maintained by Debian. No problem to switch
to a newer kernel from kernel.org, but for me it was unclear
if and how the ongoing ext4-developments will have an impact on
existing ext4-partitions. Now I think everything is clear, I'll
take a newer kernel from kernel.org.
--
cu
Uenal
On Thu, Jun 04, 2015 at 03:59:16PM +0200, U.Mutlu wrote:
> I have many times compiled a kernel and used it successfully,
> but when I dist-upgraded from Debian 7 to Debian 8 it installed
> it's own stock kernel maintained by Debian. No problem to switch
> to a newer kernel from kernel.org, but for me it was unclear
> if and how the ongoing ext4-developments will have an impact on
> existing ext4-partitions. Now I think everything is clear, I'll
> take a newer kernel from kernel.org.
Many Linux kernel developers use at least one or more ext4 file
systems, and they would be very cranky if things became unstable. As
a result, we are regularly running regression tests to make sure we
don't break ext4 users.
This principle holds true for all open source projects, at those with
responsible developers. Emacs is constantly adding features --- would
that lead you to be concerned after upgrading to Debian 8 that you
shouldn't use a new release of emacs because it might corrupt your
source files in the course of using it in normal operations, and send
e-mail to the emacs developer's list asking if it's safe to use "the
new emacs"?
Regards,
- Ted
P.S. There was a typo in my previous message. To be clear, 4.0 is
**NOT** is not a long-term supported kernel. (My previous e-mail
omitted the "not".)