From: Dave Chinner <david@fromorbit.com>
To: "aluno3@poczta.onet.pl" <aluno3@poczta.onet.pl>
Cc: xfs@oss.sgi.com
Subject: Re: Which xfsprogs version to which kernel version
Date: Tue, 1 Dec 2015 08:41:04 +1100 [thread overview]
Message-ID: <20151130214104.GL26718@dastard> (raw)
In-Reply-To: <5656DD39.8060403@poczta.onet.pl>
On Thu, Nov 26, 2015 at 11:21:45AM +0100, aluno3@poczta.onet.pl wrote:
> Hello,
>
> I am using kernel 3.10 and would like to update xfsprogs (currently I
> have 3.1.5).
>
> When I tried to use the newest version of xfsprogs 4.3.0 I get the call
> trace about detected version 5 of superblock when mounting volume which
> was formatted using mkfs.xfs from 4.3.0.
More recent xfsprogs versions enable features that are only
supported by recent kernels. We tend to wait at least a year before
enabling new features by default in xfsprogs so that kernel support
is usually picke dup by distros before they update xfsprogs....
If you have an old kernel, then you need to turn off the newer
features that your kernel does not support. This has always been the
case - if you update the xfsprogs yourself, then you need to use the
correct options for your kernel. In general, this:
# mkfs.xfs -f -m crc=0 -n ftype=0 <dev>
will make a filesystem that can be mounted on old kernels. If
distros are shipping old kernels with new xfsprogs and are not
changing the default behaviour to suit their kernel, then that is a
distro problem.
As it is, in future the version of xfsprogs will tell you what
kernel has the same feature support. i.e. xfsprogs 4.2.0 has exactly
the same code/feature support as kernel 4.2.0. Similarly for
xfsprogs/kernel 4.3.0. However, this won't prevent the fact that
xfsprogs 4.8.0 might enable features that kernel 4.3.0 does not know
about - the only way to prevent that sort of problem is to never
enable new features in mkfs.xfs, and that's not a viable solution.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-11-30 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 10:21 Which xfsprogs version to which kernel version aluno3
2015-11-26 12:26 ` Emmanuel Florac
2015-11-26 13:18 ` aluno3
2015-11-26 13:50 ` Brian Foster
2015-11-26 14:36 ` aluno3
2015-11-27 15:22 ` Brian Foster
2015-11-30 8:37 ` aluno3
2015-11-30 9:51 ` Carlos Maiolino
2015-11-30 21:41 ` Dave Chinner [this message]
2015-12-01 8:30 ` Martin Steigerwald
2015-12-01 20:26 ` Dave Chinner
2015-12-02 5:32 ` Eric Sandeen
2015-12-02 17:07 ` Arkadiusz Miśkiewicz
2015-12-02 21:14 ` Dave Chinner
2015-12-03 16:29 ` Eric Sandeen
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=20151130214104.GL26718@dastard \
--to=david@fromorbit.com \
--cc=aluno3@poczta.onet.pl \
--cc=xfs@oss.sgi.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