public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Isaacson <adi@hexapodia.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: ENOSPC but df and df -i show free space
Date: Sun, 19 Jun 2011 15:58:34 -0700	[thread overview]
Message-ID: <20110619225834.GY21778@hexapodia.org> (raw)
In-Reply-To: <20110619221852.GH561@dastard>

On Mon, Jun 20, 2011 at 08:18:52AM +1000, Dave Chinner wrote:
> > % touch /d1/tmp/foo
> > touch: cannot touch `/d1/tmp/foo': No space left on device
> > % df /d1
> > Filesystem           1K-blocks      Used Available Use% Mounted on
> > /dev/mapper/vg0-d1   943616000 904690332  38925668  96% /d1
> 
> Problems like this will occur if you run your filesystem at > 85-90%
> full for extented periods....

Ah, yes, that's definitely been the case.  I grow the filesystem when it
hits 95% utilization or thereabouts.  Hadn't realized that's such an
awful use case for xfs.

> > % df -i /d1
> > Filesystem            Inodes   IUsed   IFree IUse% Mounted on
> > /dev/mapper/vg0-d1   167509008 11806336 155702672    8% /d1
> > % sudo xfs_growfs -n /d1
> > meta-data=/dev/mapper/vg0-d1     isize=256    agcount=18, agsize=13107200 blks
> >          =                       sectsz=512   attr=2
> > data     =                       bsize=4096   blocks=235929600, imaxpct=25
> >          =                       sunit=0      swidth=0 blks
> > naming   =version 2              bsize=4096   ascii-ci=0
> > log      =internal               bsize=4096   blocks=25600, version=2
> >          =                       sectsz=512   sunit=0 blks, lazy-count=1
> > realtime =none                   extsz=4096   blocks=0, rtextents=0
> > % grep d1 /proc/mounts
> > /dev/mapper/vg0-d1 /d1 xfs rw,relatime,attr2,noquota 0 0
> > 
> > Obviously I'm missing something, but what?
> 
> Most likely is that you have no contiguous free space large enough
> to create a new inode chunk.  using xfs_db to dump the freespace
> size histogram will tell you if this is the case or not.

% sudo xfs_db -c freesp /dev/vg0/d1
   from      to extents  blocks    pct
      1       1  168504  168504   1.71
      2       3     446    1135   0.01
      4       7    5550   37145   0.38
      8      15   49159  524342   5.33
     16      31    1383   29223   0.30
2097152 4194303       1 2931455  29.78
4194304 8388607       1 6150953  62.49

I don't really grok that output.

-andy

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-06-19 22:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-19 21:50 ENOSPC but df and df -i show free space Andy Isaacson
2011-06-19 22:18 ` Dave Chinner
2011-06-19 22:58   ` Andy Isaacson [this message]
2011-06-19 23:23     ` Dave Chinner
2011-06-19 23:55       ` Andy Isaacson

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=20110619225834.GY21778@hexapodia.org \
    --to=adi@hexapodia.org \
    --cc=david@fromorbit.com \
    --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