Re: [Ocfs2-users] Versions and features
-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- ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Versions and features
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sunil Mushran [01.03.2011 01:59]: On 02/28/2011 09:10 AM, Joel Becker wrote: On Mon, Feb 28, 2011 at 02:07:16PM +0100, Werner Flamme wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, last Friday my colleague (using Oracle's Linux 5) und me tried to get access to a shared OCFS2 volume. Since he claimed that he now has OCFS2 1.6, and I only have 1.4.3 (list below), we decided that I create the filesystem with --fs-feature-level=max-features. If you want to share among differing versions, you want --fs-feature-level=max-compat. max-features means select the newest features, which will be incompatible with ocfs2 1.4. mkfs.ocfs2 manpage includes two sections titled feature compatibility and feature values. The former lists the features and when they were made available. You can use the feature values section to determine the feature the fs is missing in your distro version. As Joel mentioned, that max-features is mostly meant for mainline. Distros are always a step or two behind. Sunil, I see the compatibility list on the mkfs.ocfs2 manpage. But I still do not see what features are available for any of us. I this list, the kernel my colleague uses (2.6.18) is not mentioned, the list starts with 2.6.20. So he has no OCFS2 at all? Nonsense, he has. He uses OCFS2 1.4.8 as a kernel module, and the tools show version 1.6. So he can use what features? Because of his kernel module it was local, sparse, unwritten, and inline-data. But from the tools version he should be able to use block64, xattr, and refcount also. 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. What might this attribute have been? How will we ever find out? Only trial and error? What about a %F in the query string of tunefs.ocfs2 telleing all possible features for the installed combination of OCFS2 kernel module and tools? %H and %M are nice, but they only show the flags that are already applied. %F might show the features that are possible to handle. Werner -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk1s9h8ACgkQk33Krq8b42PiJQCeL6kTzhov5N3RBi4pFkDIl8bF FKYAoIDq/6APdxdhoXL7xk+R0FOcp0rI =2QsX -END PGP SIGNATURE- ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
Re: [Ocfs2-users] Versions and features
On Mon, Feb 28, 2011 at 02:07:16PM +0100, Werner Flamme wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, last Friday my colleague (using Oracle's Linux 5) und me tried to get access to a shared OCFS2 volume. Since he claimed that he now has OCFS2 1.6, and I only have 1.4.3 (list below), we decided that I create the filesystem with --fs-feature-level=max-features. If you want to share among differing versions, you want --fs-feature-level=max-compat. max-features means select the newest features, which will be incompatible with ocfs2 1.4. Joel -- Life's Little Instruction Book #407 Every once in a while, take the scenic route. http://www.jlbec.org/ jl...@evilplan.org ___ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
