Inode numbers of files/dirs can get bigger than 2^32 after we grew an xfs file system(<2TB) by xfs_growfs

Issue

After grew a XFS by using xfs_growfs tool, newly created files/directories inode numbers are bigger than 2³²

• Steps to Reproduce:

# lvcreate -L 1100G -n lv_clk sysdataVG00
# mkfs.xfs /dev/sysdataVG00/lv_clk
# mount /dev/mapper/sysdataVG00-lv_clk /CLK
# lvextend -L+1G /dev/sysdataVG00/lv_clk
# xfs_growfs /CLK -D 288620544
# mkdir /CLK/dir{1..10}

• Actual results:
  • On grown file systems(<2TB), inode number of files/dirs gets bigger than than 2³²
  • These large inode numbers caused 32-bit stat calls to fail with EOVERFLOW

# ls -li /CLK
total 0
                 67 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test1
4294967361 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test10 <-- inode number > 2³²
  1073741888 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test2
   2148610112 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test3
3221225536 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test4
4294967360 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test5 <-- inode number > 2³² 
                  68 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test6
   1073741889 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test7
    2148610113 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test8
 3221225537 drwxr-xr-x. 2 root root 6 Feb 16 13:55 test9

• Expected results:
  • As per Storage Administration Guide on grown file systems(<2TB), using 512 bytes inodes the inode number is expected to be smaller than 2³²;