[Ocfs2-users] Versions and features

[Werner Flamme]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sunil Mushran [01.03.2011 17:48]:

> Note that EL5 is _not_ 2.6.18. That version was merely the starting
> point. The kernel versions listed in mkfs manpage refer to pure
> unadulterated mainline kernel versions.

My colleage had a complete run of up2date last Friday and now has a
kernel 2.6.18-3xx. Before, he had 2.6.18-1xx. He's running a RAC on his
nodes.

> If the kernel module is 1.4, then the user will be limited to the feature
> set listed in the 1.4 docs. That the tools are 1.6 is incidental. To get
> all the latest features, both the tools and the fs need to be the latest
> version.

OK, thanks (and for the rest of the info, too). So, when the new JBODs
arrive, he will create a fs and query the features with tunefs.ocfs2, so
that we know which features are really supported.

>> My kernel (2.6.32) does show up, but the version of my kernel module
>> (1.5) does not. My tools are version 1.4. So I should not be able to use
>> any feature that he can't. But this is not the case, some attribute that
>> my mkfs.ocfs2 introduced to the filesystem was the reason that he could
>> not mount it.
> 
> In mainline, the fs version does not matter. It is the version of the
> kernel that dictates the version of the fs. We have not figured out
> how to automatically populate the fs version with the kernel version.

> modinfo maybe a better place to provide this info. But the reality is
> that this is just an interim problem. If we add the list of supported
> features in modinfo, the new module will be in users hands around
> the same time that all users will be on the new version. Still something
> for us to chew on.

Oh, my. My modinfo identifies OCFS2 as Version 1.5, and I do not see
this version on any manpage... I love it.

Again, thanks for the info!

Regards
Werner
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk1uN/4ACgkQk33Krq8b42OVBgCfcTgoUjut3Sd5ltaqex3zYqmL
MTkAn2WD/oUDMBRv07TBdsEf9koLIqiH
=dmzB
-----END PGP SIGNATURE-----