Premature "No Space left on device" on XFS
Dave Chinner
david at fromorbit.com
Fri Oct 7 18:20:12 CDT 2011
On Fri, Oct 07, 2011 at 04:40:13PM +0800, Gim Leong Chin wrote:
> Hi Dave,
>
>
> >
> > As it is, your problem is most likely fragmented free space
> > (an
> > aging problem). Inodes are allocated in chunks of 64, so
> > require an
> > -aligned- contiguous 16k extent for the default 256 byte
> > inode size.
> > If you have no aligned contiguous 16k extents free then
> > inode
> > allocation will fail.
> >
>
> I understand from the mkfs.xfs man page "The XFS inode contains a fixed-size part and a variable-size part."
>
> 1) Do you mean inodes are allocated in units of 64 at one go?
http://xfs.org/docs/xfsdocs-xml-dev/XFS_Filesystem_Structure//tmp/en-US/html/AG_Inode_Management.html
http://xfs.org/docs/xfsdocs-xml-dev/XFS_Filesystem_Structure//tmp/en-US/html/Inode_Btrees.html
> 2) What is the size of the fixed-size part?
> 3) Are the fixed-size parts of inodes also allocated in units of 64 at one go?
> 4) Where are the fixed-size parts located? On special extents just like the variable-size part?
> 5) What about the locality of the variable and fixed size parts of the inodes? Can they be any distance apart?
http://xfs.org/docs/xfsdocs-xml-dev/XFS_Filesystem_Structure//tmp/en-US/html/On-disk_Inode.html
Cheers,
Dave.
--
Dave Chinner
david at fromorbit.com
More information about the xfs
mailing list