> Going back through the logs though it looks like the main reason we do a > 4MiB block size is so that we have a chance of reporting actual cluster > sizes to 32-bit systems, I believe you're talking about a different block size (there are so many of them). The 'statvfs' system call (the essence of a 'df' command) can return its space sizes in any units it wants, and tells you that unit. The unit has variously been called block size and fragment size. In Cephfs, it is hardcoded as 4 MiB so that 32 bit fields can represent large storage sizes. I'm not aware that anyone attempts to use that value for anything but interpreting statvfs results. Not saying they don't, though. What I'm looking at, in contrast, is the block size returned by a 'stat' system call on a particular file. In Cephfs, it's the stripe unit size for the file, which is an aspect of the file's layout. In the default layout, stripe unit size is 4 MiB. -- Bryan Henderson San Jose, California _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |