Products > Computers

[solved] Linux:: xfs odds!!!

<< < (2/2)

0db:

--- Quote from: greenpossum on April 05, 2020, 10:26:00 am ---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.

--- End quote ---

I 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/sda3
xfs_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] =

--- End code ---

xfs_db is part of xfsprogs

CentOS/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.

0db:
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

greenpossum:
It's not just the userland progs, the kernel filesystem module also has to be the updated version, as I have already said.

RoGeorge:
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!   :-+

0db:
tested xfsprogs v3.2.0 -> problem appeared
updated xfsprogs to v3.2.4 -> problem solved
updated xfsprogs to v5 -> still working


--- Code: ---v2.6.25    2005-02
v2.8.18-1  2007-01
v2.9.7-1   2008-03
v3.1.7     2012-01
v3.1.8     2012-09
v3.1.10    2013-01
v3.1.11    2013-07
v3.2.0     2014-05 <-------------- Xfs v5 early support
v3.2.1     2014-07
v3.2.2     2014-12
v3.2.3     2015-06
v3.2.4     2015-07 <-------------- Xfs v5 full support
v4.2.0     2015-09
v4.3.0     2015-11
v4.5.0     2016-03
v4.7.0     2016-08
v4.8.0     2016-10
v4.9.0     2017-01
v4.10.0    2017-02
v4.11.0    2017-05
v4.12.0    2017-07
v4.13.1    2017-09
v4.14.0    2017-11
v4.15.0    2018-02
v4.15.1    2018-02
v4.16.1    2018-05
v4.17.0    2018-06
v4.18.0    2018-08
v4.19.0    2018-11
v4.20.0    2019-02
v5.0.0     2019-05
v5.1.0     2019-07
v5.2.0     2019-08
v5.2.1     2019-08
v5.3.0     2019-11

--- End code ---

Digging deeper
before v3.2.0, there was support for xfs-v4
after v3.2.4 there was support for xfs-v5
between v3.2.0 and v3.2.4 it was stabilization

Navigation

[0] Message Index

[*] Previous page