From: Dave Chinner <david@fromorbit.com>
To: Dave Hall <kdhall@binghamton.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Slightly Urgent: XFS No Space Left On Device
Date: Tue, 31 Mar 2015 06:45:10 +1100 [thread overview]
Message-ID: <20150330194510.GD28621@dastard> (raw)
In-Reply-To: <551993CF.4060908@binghamton.edu>
On Mon, Mar 30, 2015 at 02:19:59PM -0400, Dave Hall wrote:
> Hello,
>
> I have an XFS file system that's getting 'No space left on device'
> errors. xfs_fsr also complains of 'No space left'. The XFS Info
> is:
>
> # xfs_info /data
> meta-data=/dev/sdb1 isize=256 agcount=19,
> agsize=268435440 blks
> = sectsz=512 attr=2
> data = bsize=4096 blocks=4882431488, imaxpct=5
> = sunit=16 swidth=160 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =internal bsize=4096 blocks=521728, version=2
> = sectsz=512 sunit=16 blks,
> lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
> # df -h .
> Filesystem Size Used Avail Use% Mounted on
> /dev/sdb1 19T 12T 7.0T 62% /data
> # df -ih .
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /dev/sdb1 3.7G 4.7M 3.7G 1% /data
>
>
> xfs_db freesp shows that AG 0 seems to be full. I've included the
> freesp for the first few AGs, but the rest seem pretty consistent
> with AGs 1 - 4 that I've included below.
>
> xfs_db> freesp -s -e 1000000000 -a 0
Can you please drop the "-e 1000000" from these commands and post it
again? The histogram of differing free space sizes is information
we actually need to diagnose the problem...
Also, kernel version, mount options and machine details are
necessary to determine why AG0 might be full (e.g. allocation policy
in use).
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:[~2015-03-30 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 18:19 Slightly Urgent: XFS No Space Left On Device Dave Hall
2015-03-30 19:45 ` Dave Chinner [this message]
2015-04-01 19:53 ` Dave Hall
2015-04-02 0:12 ` Dave Chinner
2015-04-02 14:32 ` Dave Hall
2015-04-02 14:36 ` Grozdan
2015-04-02 14:41 ` Grozdan
2015-04-02 22:36 ` Dave Chinner
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=20150330194510.GD28621@dastard \
--to=david@fromorbit.com \
--cc=kdhall@binghamton.edu \
--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