> [ ... ] couldn't mount on a RedHat 5.3 (antediluvian kernel > 2.6.18-128.el5 ). > running xfs_db version gave this: > versionnum [0xb4a4+0xa] = > V4,NLINK,ALIGN,DALIGN,DIRV2,LOGV2,EXTFLG,MOREBITS,ATTR2,LAZYSBCOUNT Interesting issue. But on my SL57 64 bits I get: ---------------------------------------------------------------- versionnum [0xbd84+0x8] = V4,ALIGN,DALIGN,DIRV2,LOGV2,EXTFLG,SECTOR,MOREBITS,ATTR2 ---------------------------------------------------------------- and that's with kernel 2-6.18-274.12.1.el5 which is nearly the latest. The only difference is 'LAZYSBCOUNT'. I suspect that you have omitted to mention whether the two systems are 64b or 32b or a mix, because IIRC there are some limitations with 32b XFS. Anyhow I did a search for some of those flags and there is a potentially relevant but old reply here: http://uk.centos.org/modules/newbb/viewtopic.php?topic_id=25247&forum=45 and it seems to be a 32b/64 issue, but not one that I espected: «Mandriva LINUX uses 64-bit extents in its 32-bit kernel -- so an XFS volume created on that platform could be up to 16TB this doesn't seem to fly on a 32-bit CentOS host The 64-bit build of CentOS can mount Mandriva's XFS volumes fine» «When I saw you had kmod-xfs, I realized yours was 32-bit, therefore, running older version of xfs. The upstream vendor added the xfs support to the kernel as of 5.4 but it was only for x86_64. If you are running the 32-bit OS, then you are limited to the old code. I believe there is a plan to provide the xfs support (new code) for i686 and CentOS dev Tru is the lead.» That's interesting: the RedHat backports of newer XFS features were only done for the 64b build. However the reply is dated 2006, and a 2.6.18-128 kernel may well be more ancient than that, and since it is from 5.3, it is so old it does not have the backports in the 64b version either as that was done in 5.4. _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
