On 01/29/2018 11:56 PM, Dave Chinner wrote:
On Mon, Jan 29, 2018 at 01:44:14PM +0200, Avi Kivity wrote:
On 01/29/2018 01:35 PM, Dave Chinner wrote:
On Mon, Jan 29, 2018 at 11:40:27AM +0200, Avi Kivity wrote:
On 01/25/2018 03:08 PM, Brian Foster wrote:
On Thu, Jan 25, 2018 at 10:50:40AM +0200, Avi Kivity wrote:
On 01/23/2018 07:39 PM, Brian Foster wrote:
Yeah, could be.. perhaps the issue is that despite the large amount of
total free space, the free space is too fragmented to satisfy a
particular allocation request..?
from to extents blocks pct
1 1 2702 2702 0.00
2 3 690 1547 0.00
4 7 115 568 0.00
8 15 60 634 0.00
16 31 63 1457 0.00
32 63 102 4751 0.00
64 127 7940 895365 0.19
128 255 49680 12422100 2.67
256 511 1025 417078 0.09
512 1023 4170 3660771 0.79
1024 2047 2168 3503054 0.75
2048 4095 2567 7729442 1.66
4096 8191 8688 59394413 12.76
8192 16383 310 3100186 0.67
16384 32767 112 2339935 0.50
32768 65535 35 1381122 0.30
65536 131071 8 651391 0.14
131072 262143 2 344196 0.07
524288 1048575 4 2909925 0.62
1048576 2097151 3 3550680 0.76
4194304 8388607 10 82497658 17.72
8388608 16777215 10 158022653 33.94
16777216 24567552 5 122778062 26.37
total free extents 80469
total free blocks 465609690
average free extent size 5786.2
Looks like plenty of free large extents, with most of the free space
completely, unfragmented.
Indeed..
You need to look at each AG, not the overall summary. You could have
a suboptimal AG hidden in amongst that (e.g. near ENOSPC) and it's
that one AG that is causing all your problems.
There's many reasons this can happen, but the most common is the
working files in a directory (or subset of directories in the same
AG) have a combined space usage of larger than an AG ....
That's certainly possible, even likely (one huge directory with all of the
files).
This layout is imposed on us by the compatibility gods. Is there a way to
tell XFS to change its policy of on-ag-per-directory?
mount with inode32. That rotors files around all AGs in a round
robin fashion instead of trying to keep directory locality for a
working set. i.e. it distributes the files evenly across the
filesystem.
http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide/tmp/en-US/html/ch06s09.html
says:
"When 32 bit inode numbers are used on a volume larger than 1TB in size,
several changes occur.
A 100TB volume using 256 byte inodes mounted in the default inode32 mode
has just one percent of its space available for allocating inodes.
XFS will reserve the first 1TB of disk space exclusively for inodes to
ensure that the imbalance is no worse than this due to file data
allocations."
Does this mean that a 1.1TB disk has 1TB reserved for inodes and 0.1TB
left over for data? Or is it driven by the "one percent" which is
mentioned above, so it would be 0.011TB?
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
