[solved] Linux:: xfs odds!!! - Page 1
Forum section: electronics / general

author: 0db
author_rank: Frequent Contributor
timestamp: April 05, 2020, 04:08:27 am
content: QuoteThis is really a point to know.Quotewhich version did make the difference? xfsprogs >= v4.5?

author: I wanted a rude username
author_rank: Frequent Contributor
timestamp: April 05, 2020, 04:21:56 am
content: Quote from: 0db on April 05, 2020, 04:08:27 amWhichever version it was, note that Red Hat don't support XFS on RHEL 6 unless you pay extra (Scalable File System entitlement). And that regular support will end in November regardless. So best not to invest too much effort into this release with its decade old kernel unless you have some really good reason.

author: greenpossum
author_rank: Frequent Contributor
timestamp: April 05, 2020, 04:40:38 am
content: Learnt this the hard way.https://green-possum-today.blogspot.com/2018/04/xfs-partition-created-under-centos-7.htmlUsers wanted to go back to CentOS 6 because applications were not qualified for CentOS/RHEL 7.If you don't have a need for CentOS/RHEL 6, go to 7 or even 8.

author: 0db
author_rank: Frequent Contributor
timestamp: April 05, 2020, 10:16:53 am
content: It doesn't care about Red-Hat certifications, except they document the problem. Assuming you are using the same kernel version (both my machines are v4.9) , just talking about the userland, I have just personally verified that if you use a 2020-updated machine to format an XFS partition then a 2011-updated machine cannot check the partition.I haven't understood it yet, but it seems it's 100% related to xfsprogs and (maybe also) e2fsprogs.

author: greenpossum
author_rank: Frequent Contributor
timestamp: April 05, 2020, 10:26:00 am
content: There was a version update to the xfs partition format which affects the kernel driver and the userland tools in between 6 and 7, that's all. Nothing to do with e2fsprogs, different filesystem type.

author: 0db
author_rank: Frequent Contributor
timestamp: April 05, 2020, 10:37:50 am
content: Quote from: greenpossum on April 05, 2020, 10:26:00 amI have experimented it personally, it shows the same errors reported in the Red-Hat's note. In my case, with the same kernel version, two different versions of xfsprogs offer two different behaviors.Code:# xfs_db -c version /dev/sda3xfs_db: WARNING - filesystem uses v1 dirs,limited functionality provided.cache_node_purge: refcount was 1, not zero (node=0x1308210)xfs_db: cannot read root inode (117)cache_node_purge: refcount was 1, not zero (node=0x1308810)xfs_db: cannot read realtime bitmap inode (117)xfs_db: WARNING - filesystem uses v1 dirs,limited functionality provided.versionnum [0xb4a5+0x18a] =xfs_db is part of xfsprogsCentOS/RHEL 7 uses a modern version of xfsprogs than the one on CentOS/RHEL 6, exactly like my 2020-updated computer uses a modern version of xfsprogs than the one on my 2015-updated computer.I still have to understand from which version of xfsprogs there is the problem.

author: 0db
author_rank: Frequent Contributor
timestamp: April 05, 2020, 11:08:31 am
content: Now, the XFS usb-stick made on my workstation has been tried on 4 computers:(workstation) kernel v5, rootfs 2020:able to mount,able to run xfs_tools(server) kernel v4.9.16, rootfs 2020:able to mount,able to run xfs_tools(server) kernel v4.9.16, rootfs 2015:able to mount,unable to run xfs_tools(server) kernel v4.4.197, rootfs 2011:able to mount,unable to run xfs_tools

author: greenpossum
author_rank: Frequent Contributor
timestamp: April 05, 2020, 11:09:08 am
content: It's not just the userland progs, the kernel filesystem module also has to be the updated version, as I have already said.

author: RoGeorge
author_rank: Super Contributor
timestamp: April 05, 2020, 11:23:18 am
content: I'm using ZFS for more than a year now. Always worked perfectly, very easy to administer, and I think it can do more than XFS can. Maybe you want to try ZFS instead.So far, to me ZFS was a zero maintenance filesystem, indeed!

author: 0db
author_rank: Frequent Contributor
timestamp: April 05, 2020, 03:15:41 pm
content: tested xfsprogs v3.2.0 -> problem appearedupdated xfsprogs to v3.2.4 -> problem solvedupdated xfsprogs to v5 -> still workingCode:v2.6.25 2005-02v2.8.18-1 2007-01v2.9.7-1 2008-03v3.1.7 2012-01v3.1.8 2012-09v3.1.10 2013-01v3.1.11 2013-07v3.2.0 2014-05 <-------------- Xfs v5 early supportv3.2.1 2014-07v3.2.2 2014-12v3.2.3 2015-06v3.2.4 2015-07 <-------------- Xfs v5 full supportv4.2.0 2015-09v4.3.0 2015-11v4.5.0 2016-03v4.7.0 2016-08v4.8.0 2016-10v4.9.0 2017-01v4.10.0 2017-02v4.11.0 2017-05v4.12.0 2017-07v4.13.1 2017-09v4.14.0 2017-11v4.15.0 2018-02v4.15.1 2018-02v4.16.1 2018-05v4.17.0 2018-06v4.18.0 2018-08v4.19.0 2018-11v4.20.0 2019-02v5.0.0 2019-05v5.1.0 2019-07v5.2.0 2019-08v5.2.1 2019-08v5.3.0 2019-11Digging deeperbefore v3.2.0, there was support for xfs-v4after v3.2.4 there was support for xfs-v5between v3.2.0 and v3.2.4 it was stabilization