xfs_io shows "extsize" as 0. The data bsize is always 4096. What's the implication of a 0 extsize? $ sudo xfs_io -c 'stat' /mnt/S48BNW0K700192T/ fd.path = "/mnt/S48BNW0K700192T/" fd.flags = non-sync,non-direct,read-write stat.ino = 64 stat.type = directory stat.size = 81 stat.blocks = 0 fsxattr.xflags = 0x0 [--------------] fsxattr.projid = 0 fsxattr.extsize = 0 <==== 0 fsxattr.nextents = 0 fsxattr.naextents = 0 dioattr.mem = 0x200 dioattr.miniosz = 512 dioattr.maxiosz = 2147483136 On Fri, Aug 25, 2023 at 8:48 PM Dave Chinner <david@xxxxxxxxxxxxx> wrote: > > On Mon, Aug 21, 2023 at 12:01:27PM -0700, Shawn wrote: > > Hello Dave, > > Thank you for your detailed reply. That fallocate() thing makes a lot of sense. > > > > I want to figure out the default extent size in my evn. But > > "xfs_info" doesn't seem to output it? (See below output) > > extent size hints are an inode property, not a filesystem geometry > property. xfs_info only queries the later, it knows nothing about > the former. > > # xfs_io -c 'stat' </path/to/mnt> > > will tell you what the default extent size hint that will be > inherited by newly created sub-directories and files > (fsxattr.extsize). > > > > > Also, I want to use this cmd to set the default extent size hint, is > > this correct? > > $ sudo mkfs.xfs -d extszinherit=256 <== the data block is 4KB, so > > 256 is 1MB. > > Yes. > > -Dave. > -- > Dave Chinner > david@xxxxxxxxxxxxx
