On Mon, Feb 22, 2016 at 10:16:43AM -0600, Eric Sandeen wrote: > On 2/22/16 10:12 AM, David Casier wrote: > > I have carried out tests very quickly and I have not had time to > > concentrate fully on XFS. > > maxpct =0.2 => 0.2% of 4To = 8Go > > Because my existing ssd partitions are small > > > > If i'm not mistaken, and with what Dave says : > > By default, data is written to 2^32 inodes of 256 bytes (= 1TiB). > > With maxpct, you set the maximum size used by inodes, depending on the > > percentage of disk maxpct doesn't work like that. It's a limit on the count of inodes, not a limit on their physical location. And, FWIW, mkfs does not take floating point numbers, so that mkfs.xfs command line is not doing what you think it's doing. In fact, it's probably setting maxpct to zero, and the kernel is then ignoring it because it's invalid. Cheers, Dave. -- Dave Chinner dchinner@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
