Zach Brown cf512c5fcf Use inode_count field for statfs file counts ...

Our statfs implementation had clients reading the super block and using
the next free inode number to guess how many inodes there might be.  We
are very aggressive with giving directories private pools of inode
numbers to allocate from.   They're often not used at all, creating huge
gaps in allocated inode numbers.   The ratio of the average number of
allocations per directory to the batch size given to each directory is
the factor that the used inode count can be off by.

Now that we have a precise count of active inodes we can use that to
return accurate counts of inodes in the files fields in the statfs
struct.  We still don't have static inode allocation so the fields don't
make a ton of sense.  We fake the total and free count to give a
reasonable estimate of the total files that doesn't change while the
free count is calculated from the correct count of used inodes.

While we're at it we add a request to get the summed fields that the
server can cheaply discover in cache rather than having the client
always perform read IOs.

Signed-off-by: Zach Brown <zab@versity.com>

2021-10-28 12:30:47 -07:00

..

src

Use inode_count field for statfs file counts

2021-10-28 12:30:47 -07:00

.gitignore

scoutfs: update rpm building infrastructure

2018-09-14 15:07:10 -07:00

Makefile

Filesystem version instead of format hash check

2021-01-15 10:53:00 -08:00

scoutfs-kmod.spec.in

scoutfs: update rpm building infrastructure

2018-09-14 15:07:10 -07:00