From: Dave Chinner <david@fromorbit.com>
To: Gim Leong Chin <chingimleong@yahoo.com.sg>
Cc: Bernhard Schmidt <berni@birkenwald.de>, xfs@oss.sgi.com
Subject: Re: Premature "No Space left on device" on XFS
Date: Sat, 8 Oct 2011 10:20:12 +1100 [thread overview]
Message-ID: <20111007232012.GI3159@dastard> (raw)
In-Reply-To: <1317976813.82044.YahooMailClassic@web77716.mail.sg1.yahoo.com>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-10-07 23:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 19:55 Premature "No Space left on device" on XFS Bernhard Schmidt
2011-10-07 0:22 ` Stan Hoeppner
2011-10-07 0:47 ` Bernhard Schmidt
2011-10-07 1:37 ` Dave Chinner
2011-10-07 8:40 ` Gim Leong Chin
2011-10-07 23:20 ` Dave Chinner [this message]
2011-10-07 11:40 ` Michael Monnerie
2011-10-07 23:17 ` Dave Chinner
2011-10-07 13:49 ` Bernhard Schmidt
2011-10-07 23:14 ` Dave Chinner
2011-10-08 12:29 ` Bernhard Schmidt
2011-10-08 13:18 ` Christoph Hellwig
2011-10-08 22:34 ` Dave Chinner
2011-10-09 14:46 ` Christoph Hellwig
2011-10-08 22:30 ` Dave Chinner
2011-10-07 13:58 ` Bryan J Smith
2011-10-07 23:31 ` Dave Chinner
2011-10-08 6:30 ` Bryan J Smith
2011-10-08 13:16 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111007232012.GI3159@dastard \
--to=david@fromorbit.com \
--cc=berni@birkenwald.de \
--cc=chingimleong@yahoo.com.sg \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox